Changelog from Trio

Hello! 👋

Trio is moving full steam ahead to bring new features and updates to our product. We’re happy to introduce the new Credit Cards feature as part of our continuous evolution. This new feature lets companies issue digital or physical corporate cards to employees or departments, with the option to top up the balance as needed.

See how the new feature fits into our dashboard:

Key benefits:

1. Simplified expense management: Simplify the way companies manage employee expenses, with control and flexibility through a top-up feature that ensures funds are available only when needed.
2. Customizable spending limits: Set specific spending limits for each card, for detailed control over company expenses.
3. Real-time top-ups: Instantly load funds onto the corporate card, so employees have the amounts they need to make transactions when they need them.
4. Comprehensive reporting: Track and manage card usage through detailed reports that integrate seamlessly with your existing financial workflows, providing transparency and reducing administrative overhead.
5. Frictionless integration: This feature is integrated into our existing platform, providing a unified experience for companies to manage finances, payments and employee expenses in one place.

Why have credit cards?

By adding corporate cards with top-up functionality, we’re enabling your company to manage expenses more effectively using your Trio account balance. That way, you keep full control over how, when and where funds are spent. This is in line with our goal of providing flexible, secure financial solutions that increase efficiency and improve financial oversight for companies of all sizes.

Split by cost center or cardholder

Issue cards for each area of the company, or cards for employees’ individual use, always with a preset budget. View transactions in detail.

Get started!

This integration is already available in Trio’s Internet Banking: just select the “Cards” tab.

Questions?

Until next time!

Best, the Product team

As payments technology experts, we know that any direct message between seller and user is an opportunity to build better relationships. This is why the proof of payment can be a very important communication channel. The good news is that all Trio customers can now use personalization to imprint their brand’s tone of voice, or even deliver special offers, through this important receipt.

Better Statements

We’ve added new filters to help you explore and visualize your data.

Better Communications

We have included a feature to improve the end user experience. Our customers now receive a notification (webhook) whenever an automatic refund is made.

This change allows our clients to tell their users why their deposit was returned. This minimizes the risk of an accounting error on our client’s side while also reducing the load on their support service.

General features and bug fixes

🧠 Features:

• Trio API: change qrcode documentation;
• Trio Console: add virtual account id into filter component, in document screens;
• Trio Checkout: improving checkout experience outside SDK;
• Feature: send a summary of the operation when a deposit is refunded due to compliance validation;
• Feature: changing the create_and_notify to send webhooks list and the new event.

Create Sandbox Account

🐛 Fixes:

• fix(ledger): validate counterparty tax number
• fix(ledger): prevent error when generate statement csv
• fix(console): documents screens, when there is no counterparty associated with a reference
• fix(console): improve tax number validation for qrcode page
• fix(ledger): refresh ledger transaction minute aggregation before bef…
• fix(ledger): TPV value calculated with duplicated fee’s amount
• fix(admin): (Big amount) check if counterparty maximum_amount is nil, in search document screen
• fix(cashout): update counterparty legal name for transactions initiated to bank accounts
• fix(console): display an empty state in show documents screens, when counterparty is nil
• fix(cash_out): search protocol in payment batches
• fix(ledger): fix bank account branch validation
• fix(ledger): validate ISPB number when creating a counterparty bank account
• fix(console): simulate payment for pix keys when it is not a cpf or cnpj
• fix(cashin): consider failure status of refund documents
• fix(cashout): send pix message
• fix(cashout): use cashout v2 for all types of pix keys in sandbox
• fix(console): display counterparty infos in show initiation document screen
• fix(admin): update company in redis, when insert default sandbox runtime is called
• fix(ledger): prevent error when calculate fee and tax in sandbox environment
• fix(cash_in): counterparty tax number validate method
• fix(admin): synchronize fitbank statement
• fix(admin): cron job for fitbank statement sync
• fix(console): convert map keys to map atoms in stage timeline component
• fix(sandbox): refund cash out flow
• Fix(trio_checkout) - Fix checkout callback issues
• fix(ledger): synchronize fitbank statement for intermediation bank accounts

Questions? The choice is yours, and both our Merchant Services and Technical Support teams will assist:

On the Trio website or Console: click the Help Desk icon in the bottom right corner of the screen;

Via instant messaging: Reach out to us on WhatsApp (+55 41 99626-1785) or Telegram (TrioSupport_Bot) for urgent individual requests;

Via email: suporte@trio.com.br

We’ve got fresh news, right out of the UX oven!

Maybe you’re new to this, but our Product team is always keen on delivering Open Finance usability without making it about the Open Finance environment. The time has come to deliver our newest ready-to-use SDK, which reduces time and friction in QR code payments.

Trio Checkout is a tool that allows your users to implement Trio’s payment system in a straightforward manner. By using an SDK embedded in your website, you will be able to offer your clients both Payment Initiation (Open Banking / Open Finance) and the whole PayIn/PayOut processes you already hired from Trio, always handling it with isolated end-to-end security when linking to banks and financial institutions.

The benefits are numerous. Without much coding needed, all stages of the consent and payment process are managed through Trio Checkout, from credential validation and authentication to error handling and notifications for each payment flow.

So, Developers: if you’re interested in adding this payment method to your checkout, start by taking a look at our documentation.

Feel like giving it a try? For a better experience, act as if you’re the end user: use a real CPF (individual tax ID) and go through the entire process on a mobile phone.

Trio Checkout Demo

📣 New milestone: 1,500 cashouts in 60 seconds

Especially in the gambling market, payout is a hassle. But only Trio’s cashout management layer keeps fraudsters from attempting multiple withdrawals, which may overload the system and cause temporary interruptions to the cash flow. Developed in early December, V2 of our Cashout has been surpassing every expectation. We are now handling over 6,000 transactions every minute, which is way more than the 30% growth expected by the end of Q2.

Cashout V2 has delivered tremendous value to our clients, who report their cashout SLA rising from 30% to 85% after integrating.

More of our numbers (we’re really proud of them):

General features and bug fixes

🧠 Features:

• Trio Console: create financial user roles and apply new role validations in dashboard settings;

• Trio Console: re-added banking service to Entity Dropdown

• Trio Console: added TED option for Transferring screen;

• Trio Console: open new rate rules screen according to the selected tab, adding net amount and shortcuts in documents screens;

• Trio Console: cash in and cash out simulator for the sandbox environment;

• Reconciliation: Creating materialized views for integration statement entries;

• Cashout: add TED payment method to Payouts.

• Security: Add entity id in events and webhooks, so that the entity can only receive the events allowed for it.

  Create Sandbox Account

🐛 Fixes:

• fix(web): prevent cache error for pix with bank_account reference
• fix(cashin): increase the datetime range for identification of initiation document
• fix(cashin): increase to 12h the datetime range for identification of initiation document
• fix(trio): prevent deadlock when enqueue event creation
• fix(console): changed Sandbox main page from root to /tutorials
• fix(console): added initial usability improvements
• fix(console): corrected Counterparty fallback in PaymentBatch line editing
• fix(adm): create cash out failed event
• fix(cashin): increase cash in queue execution limit
• fix: added legal_name to Counterparty OpenAPI helper schema
• hotfix(sandbox): corrected error message for Settled stage in CashOut
• fix(cashout): fix blocked bank list validation
• fix(cash_out): correction for automatic confirmation of Pix Keys in Sandbox
• fix(cashin): prevent performance issues when generating refunds
• Fix(Reconciliation): removing the crontab entry for synchronize
• fix(webhook): prevent error when receive a cash out refund from Aarin
• fix(console): Transfer screen receive all PubSub payment document events
• fix(ledger): corrected validation for younger than 18
• fix(cashout): prevent error in cache validation for multiple cashouts v1 for bank account
• fix(EFX): improving error treatment when creating new rates based on old ones
• fix(ledger): increase the capacity of monetary fields
• fix(cashin): prevent performance issues when generating refunds
• fix(console): improving the response time of pages displaying documents details
• fix(console): Remove tax number search option in refund screens, and remove join clause in list pipelines
• fix(sandbox): corrected simulation of pix key payments in TrioConsole.TutorialLive
• fix(console): added timeout retry for PixKey simulations in Sandbox
• hot fix(console): corrected Sandbox generate cashout simulation for PixKey case handling
• fix(console): corrected user invitation task in TrioConsole settings
• fix(console): added another fallback to Sandbox Pix Key payment tax number
• fix(sec): update dependencies
• fix(cash_out): corrected ref value not being updated in PaymentBatch.Line
• hotfix(console): corrected InitiationDocument detail page breaking with rejected stage
• fix(console): corrected usability of Home page
• fix(ledger): query virtual account balance on replica
• fix(cash in/out): document stages with same document transaction date

💬 Need help? We’re here for you!

The choice is yours, and both our Merchant Services and Technical Support teams will assist:

Via instant messaging: Reach out to us on WhatsApp (+55 41 99626-1785) or Telegram (TrioSupport_Bot) for urgent individual requests;

On the Trio website or Console: click the Help Desk icon in the bottom right corner of the screen;

Via email: suporte@trio.com.br

---

Thanks for keeping up with us!

See you next time! 👋

Trio Sandbox is a free testing platform for anyone who wants to run simulations before releasing the payment method to customers. It’s mostly used by clients while integrating, but it can also be a game changer when deciding which banking institutions you’re going to rely on for your payments in Brazil. See the main benefits of using it:

• Test integrations: simulate payment operations, transfers and other features without affecting your production account;
• Validate the interaction process: make sure your system works correctly before going live;
• Experiment in a safe environment: use mock data in test mode, without the risk of compromising real or financial data.

The first step to accessing the environment is having a Trio Sandbox account. If you don’t have one yet, click here and open yours, for free.

With the account created, simply access the Sandbox and log in using your email and password. Then you can start by trying these processes:

• Add your teammates to show them what’s most important, and what different types of users can access;
• See how easy it is to create your first Virtual Account and move money to and from it;
• Generate a payout batch and understand how paychecks and bulk payments can leave your organization more efficiently;
• Get a glimpse of the view you can have using Trio for Foreign Exchange;
• Get the full experience of submitting a new merchant for compliance analysis;

If you have any questions, you can also access the available technical documentation.

General features and bug fixes

🧠 Features:

• (reconciliation): new interface and process to fix the entries with document_status_error;
• (admin): create generate report csv screen;
• (cash-in): consolidate intermediation companies into a single SPB bank account;
• (console): remove update limits when entity is intermediation;
• (cashin): ignore cashin from investment entity;
• (admin): created page for event batch renotification;
• (console): added fee visualization for regular virtual accounts.

🐛 Fixes:

• (api): remove qrcode generation cache by tax number;
• (console): improve documents details page performance;
• (console): add convert timezone datetime in home screen test;
• (Reconciliation): refactoring the way to find refund documents;
• (cashin): retry cash in refund with new document for each attempt.

That’s all for now!

Questions and suggestions? Please comment below or send us an email at suporte@trio.com.br

Thanks for reading!
See you soon!

Check out our new features

Hi everyone!

Our product and engineering teams have some news for you. Stay up to date:

🆕 New Console views for operators

Our team developed a new Console view that shows everything the operator needs to provide support and verify the ongoing operation, with no risk of changing a transaction by mistake.

🆕 Transactions Detailed Information

Our clients can now experience several upgrades and fixes in Trio’s Console. One highlight is the view of the accounting transactions for each document.

With these views, customers can see each transaction’s fees and taxes in the finest detail.

General features and bug fixes

🧠 Features:

• (trio_checkout): simplify and prevent errors in qr codes generation by creating a url shortener;
• (statement): generation of asynchronous ledger statements with notifications through emails;
• (console): create moving money for external accounts screen;
• (reconciliation): adding a form to go straight to bank account overview;
• (console): default entity;
• (cash in): automatic refund for invalid tax number;
• (console): create refund list screen;
• (ledger): track origin of transactions;
• add oauth authentication method.

🐛 Fixes:

• (reconciliation): create cashout refund document when the transaction date is between 00:00 and 03:00 GMT;
• (ledger): consider tax refund when validating balance;
• (cashout): process revert back for a payment document in retry;
• (reconciliation): fix for an error when converting to_datetime to iso8601;
• (reconciliation): adding a check for payment_documents with status (failed, reversed or refunded);
• (reconciliation): fix multiple agendas in a batch;
• (reconciliation): decreasing the date range for normal documents to 10 minutes;
• (console): refactor virtual account configuration labels to be easier to understand.

Thanks for reading!
’Til next time :)

Hello everyone, how’ve you been?

It’s been a busy month here, with essential changes to our product that aim to provide a faster and safer payment experience to our customers.

As usual, all improvements are also listed in our Documentation.

New Features

🆕 Open Finance Checkout

Our Open Finance payment interface now runs faster and takes the user through fewer steps, improving the user experience and raising conversion rates.

🆕 Cashout V2

Focusing on a safer money withdrawal system, Trio has developed a better way to manage the buckets of our customers’ bank accounts with an Enhanced Cashout Experience.

Find out more here: Trio Cashout V2

General features and bug fixes

🧠 Features:

• (API) distinct error code and status for duplicate external id #1429
• (ledger/calculate fee): specify when to refund fees #1416
• (cash in): automatic retry for cash in refund failure #1413
• (reconciliation): new enqueue reconciliation process #1415
• (console): moving money into virtual accounts screen #1371
• (console) added end_to_end_id validation in document consultations #1366
• (api): list ledger transactions with account type #1425

🐛 Fixes:

• create qrcode with expiration date/time second precision #1433
• (cashout/payment-batch): prevent errors in the process of copying batch lines when the line has no fees #1421
• docs (api): fix cash out v2 documentation path
• hotfix: added check for duplicate tax number in QRCode controller
• improving the order of bank accounts on the reconciliation and integration download interfaces
• (console/responsive): table row details not overflowing correctly when clicked on mobile devices
• (checkout): errors when initiation document date is not found
• (e-fx): remittance
• hotfix (console): graphs
• (api) search entries
• (api) calculate tax with round half up rule
• (reconciliation): create cashout refund document when transaction date is between 00:00 and 03:00 GMT
• (reconciliation): fix for an error when the payer is null in a CreditPixIn
• (operations): differentiate json log messages by type

Thanks for reading!
’Til next time :)

Hi everyone, how are you doing?

We’ve had a month full of work and fundamental improvements to our product, aimed at delivering better connectivity and more robust integrations to our customers. As usual, all improvements are also consolidated in our Documentation.

We hope you like what we’re presenting in this new Changelog:

🎯 A new way to integrate with Banco do Brasil

• We’ve implemented a new authentication system, based on authorizing access with a code received by SMS when the connection is created;
• We’ve added Banco do Brasil Business to Bridge;
• We’ve updated the user guide on our SUPPORT site.

🧡 Inter Personal and Inter MEI (microentrepreneurs)

• New integration with Banco Inter, easily accessible to users through QR code authentication;
• On the way to Inter Business, which should come out in the next few weeks 🚀

⏭ Improvements

• Structural change to the API: the rate limit (number of calls) is 15 requests per day. If more are requested, an error 429 will be returned with the message “too many requests”;
• The transaction fetching endpoint returns the account balance;
• Faster integration with automatic retry when discovering new accounts (login and data fetching now happen separately through a new webhook);
• Option to share information indefinitely.

🐛 Fixes

• Greater consistency in calculating transaction balances, with significant improvements;
• Several fixes to the user connection Bridge, improving usability.

Start with a 14-day free trial

Hi everyone! We have hot, exclusive news from Trio to make life easier for businesses: we’ve added Bradesco credit card integrations and XP investment positions to our connections

🆕 Banks available: XP Investimentos!

⚫️ XP Investimentos - Business integration:

• Registration data
• Bank account data
• Investments
• Positions

⚠ The XP Investimentos integration runs on the API only. Coming soon to Link!

🔴 Bradesco Business / Credit card:

We now support Bradesco credit cards:

• Credit card data
• Transactions
• Card statements

🧠 Improvements

• Documentation updated to OpenAPI
• More detailed errors when fetching statements

🐞 Fixes

• Bridge usability fixes

  • The button stayed disabled while verifying CPF/CNPJ authentication and showed no error message or any message at all. Behavior fixed.
  • Fixed behavior where institutions appeared duplicated, with no indication of which account type they belonged to, when a list of institutions was sent.

• Statement fetching fixes [Trio Link]:

  • Error fixes for these banks: Caixa Business; Itaú Business; Sicredi Business.

⏭ Changes

No changes this period. All calm and quiet ;)

Create your keys and test as much as you like!