Hop on over to our latest changelog, it's Easter-rific! 🐇

Aggregation

🎉 New

New product in the house: Employment Aggregation!

Now you can access employment data, such as work history and salaries, in 🇲🇽 Mexico (IMSS)! With Belvo's employment records resource, you can access information about your user's current social security contributions and employment history. For each user, we return:

• personal data
• work history
• historical and current daily base salary
• and more!

For more information, check out our DevPortal article and API reference.

Added fetch_historical and credentials_storage

To give more flexibility on data retention, we’ve added two new request parameters for when you’re registering a Link:

• fetch_historical - setting this to false for a single link creates a one-off link that won’t trigger historical updates.
• credentials_storage - lets you choose if you want Belvo to store credentials. If set to store, you can also specify the duration for which they should be stored.

For more information, check out our API reference.

💪 Improved

Expanded institution support

We’ve expanded our 🇨🇴 Colombia coverage to include Bancolombia a la Mano. Now you can fetch data from the savings account of Bancolombia Wallet users.
Check our Institutions article for more info.

Enrichment

🎉 New

Income Verification: reloaded!

You wrote. We listened! We've improved our Incomes resource to give you:

• detailed insights into your customers' income sources to verify their earnings.
• stability and regularity scores that reflect the consistency of their income history.
• a confidence level score that forecasts your customers' future income potential, allowing you to make well-informed lending decisions.

But that's not all! You can now use Income Verification to Enrich Your Own Data. Just plug your own raw data into our enrichment engine, whether you have an existing dataset or currently access open finance data, and we will return enriched income information.

For more information, check out our DevPortal article and API reference.

💪 Improved

Transaction categorization taxonomy: introducing more (a lot more) subcategories!

• For those using our Transaction categorization feature, you can now access 15 primary and 94 subcategories, providing you with the granularity needed to make data-driven decisions. This granularity also comes with higher-quality category predictions. For more information, check out our Subcategorization DevPortal article.
• Expanded geo-support! We used to support subcategories only in Brazil, well… now we also support 🇨🇴 Colombia and 🇲🇽 Mexico as well!
• Enrich Your Own Data! Our newly improved taxonomy is also available for our Categorization resource.

Payment Initiation

🎉 New

Set the expiration time of your Payment Links

By using the expires_in parameter, you can now customize the expiration time of a Payment Link (available for 🇨🇴 Colombia PSE and 🇧🇷 Brazil OFPI). The minimum time limit for a payment link to expire is one minute, while the maximum time limit is 90 days. Check out our API reference for more info.

Added regular expressions to the amount parameter in Payment Initiation.

Since we know 🇨🇴 Colombia and 🇧🇷 Brazil handles currency differently, we wanted to help you avoid unnecessary errors when creating payment links in each country. That’s why we’ve added country-specific validations to the amount request parameter for Payment Links. You can check this out in our API Reference.

Added belvo-flow parameter in Payment Links - 🇨🇴 Colombia (PSE)

You can now choose whether you want to use our Belvo flow when you create payment links with Belvo-integrated institutions. Setting this parameter to false will create the payment link using the non-Belvo flow. Check out our API Reference for more info.

💪 Improved

API and Widget Errors article updated with Payment errors.

We improved our page so you can now see what listed errors have an impact on the Payment Initiation API and added a new section for payment-specific errors.

callback_urls are now optional in Payment Links

The callback_urls object is now optional when creating a payment link, which means that you don't have to send URLs that redirect your customer after the payment is completed. This is particularly useful when sharing a payment link with your customer via email and you don't want to redirect them after payment. You can check this out in our API Reference.

🐞 Fixed

wrong date format

We noticed that the created_at field in our Payment Initiation API was returning the wrong format. This is fixed now and we return the value in ISO 8601 format - sorry about that.

⚠️ Deprecated

Removed provider_error_message from payment intents

We want to simplify things for you - that's why we've removed this information from the response since it didn't add value to our clients.

API and documentation

🎉 New

Added fields and omit parameters in our API Reference

To improve our Open API specification, we’ve added the fields and omit parameters to all the endpoints in our Public API.

Dashboard

🎉 New

• You’re now just one click away from every Help resource and contact us link if you ever need our help. Clean, functional, accessible, and intuitive 🤗.
• You’ll see some new pop-ups “pop up” in our Dashboard to let you know about our new Payment Initiation product in Brazil and Colombia - Check them out to start collecting payments from your customer!

⚠️ Deprecated

• We removed the "Back to table" button from Link and Event details to improve your experience with the product.

With ❤️, the chocolate-filled Belvo development team.