Consent link for Open Finance

Hi everyone 👋🏼

We’ve reached the end of another cycle, and I’m super excited to share all the news with you. Special thanks to our customers who shared feedback and reported issues, which definitely made a big contribution to this result.

🆕 No-code Open Finance integration

If you’ve heard of payment links, you know how much they’ve made it easier (and possible) for many companies to go digital.

With the challenge of bringing Open Finance access to more companies in mind, we’ve launched the Consent Link. That’s right: from now on, you no longer need to spend hours, weeks or months building an integration to include Open Finance in your process. You can generate a unique link and send it to your user so they can consent to sharing their financial data securely and quickly.

The financial data is available in our dashboard in OFX format, with other formats coming soon. Remember that each Consent Link is unique and can be shared by email, WhatsApp, SMS or whatever tool you prefer.

Want to see how the Consent Link works? Just sign up and use it: we offer 30 connected accounts for free.

🆕 Real-time balance calculation

From now on, Trio calculates the balance in real time for every transaction. We’ve added the balance property to the transaction object, which holds the balance after the transaction.

The details are already available in our documentation.

🆕 Credit card data - Santander Business

We’ve rolled out credit card data fetching (statements and card information) to all customers for the Santander - Business institution. Access covers the available past card statements (24 months) and the current one.

🧠 Improvements

• We’ve improved our error handling and management to give more context when an exception happens in our API. A complete table is available in our documentation to help you build your integration.

🐛 Bugs

• Removed the company_id field from the webhook creation endpoints. It’s no longer needed, since we can identify the company from the credentials;
• Fixed an issue affecting Bridge availability for applications with restrictions. We moved responsibility for sizing, overlay, alignment and spacing to Trio;
• Improved Bridge responsiveness for mobile apps.

Until next time :)