April-June 2024

๐Ÿšจ Development Environment Deprecation

๐Ÿšง

Please note that the Development Environment will be deprecated in June 2024.

To improve your integration experience, we will be deprecating our development environment at the end of June 2024 and substituting it with direct access to production with an activity limit that you can use for free.

Why the change?

Maintaining a separate development environment can pose challenges in ensuring feature parity with production, particularly in terms of performance and response times. By providing direct access to production, we aim to give you a more consistent and reliable experience.

What will happen with my existing data in development?

Data from links created in development will be deleted. Recurrent activity will stop and credentials of links will be deleted.

If you are currently using our development environment, our support team will reach out to you with additional details on the process. And of course, if you have any questions, do not hesitate to contact us!


Aggregation

๐ŸŽ‰ New

Employments Colombia

Want to retrieve employment data about your users in Colombia? Well now you can! With our new Employments (Colombia) product, you can retrieve the last two years of your user's employment history. Check out our dedicated article and API reference for the details.

Employment Score (Mexico)

Our employment score for Mexico is an innovative combination of employment data and machine learning that generates a score predicting a user's employability and income in the next 3, 6, and 12 months. Try it now for free by reaching out to our support team! And don't forget to check out our Employment Records API reference for the details.


SAT Payroll Fields

We've updated our SAT Invoices product to now retrieve the following critical details regarding payrolls:

  • periodicity
  • earnings_breakdown
  • tax_deductions
  • other_payments

Check out the details of each new field in our Invoice API reference (scroll down to the responses section).

OFDA App2App Widget Flow

Bring a more native-like experience for your mobile users by utilizing our new App2App flow for the OFDA Widget.

Webhook trigger reason

Need to know if the webhook you received was for a historical update, a recurrent link update, or as a response to an asynchronous POST request? You'll be glad to hear that we've added the process_type parameter in all our webhooks to do just that.

๐Ÿ“˜

Webhook process_type

The process_type parameter indicates why the webhook event was triggered. We return one of the following values:

  • historical_update: The webhook was triggered as we finished a historical update for the data retrieval (for recurrent links and for single links with fetch_resources).
  • recurrent_update: The webhook was triggered due to the recurrent (cyclical) refresh of the data.
  • async_post: The webhook was triggered as the asynchronous retrieval of data from a POST call is complete.

Read up on the details in our Webhooks (Aggregation) article.

๐Ÿ’ช Improved

Employment Records (Mexico) now supports async

You can now use the X-Belvo-Request-Mode: async header parameter in our Retrieve employment record details (Mexico) requests.

Update your links fetch_resources

Accidentally didn't add a resource to the fetch_resources parameter when creating a link? Well, you can now use our Modify a link's data retrieval request to not only update the access_mode, but also the fetch_resources!

Belvo webhook IP addresses

Want to whitelist the IP address that Belvo uses to send webhooks to you? Well, we've added it to our documentation for both Aggregation and Payment webhooks, but here they are just in case you missed them:

  • 3.130.254.46
  • 18.220.61.186
  • 18.223.45.212

๐Ÿ‘

We highly recommend you whitelist these IP addresses so that you can receive webhook events.

Payments

๐ŸŽ‰ New

Schedule one-off and recurring payments

Need to schedule a payment to occur within the next two years? Have no fear - we've got you covered. With our new Single Scheduled Payments feature, you can!

And say you wanted to schedule recurring payments? Then you'll be glad to hear that you can create daily, weekly, monthly, and custom payment schedules ๐Ÿ˜Ž.

If you accidentally scheduled a payment (or a set of payments) that you need to cancel, well, we thought of that too. Check out our Cancel a Payment Intent guide for the details.

๐Ÿ’ช Improved

Add a statement description

Want to have more control over the description that will appear in your user's bank statement? Well, we've added the new statement_description parameter to our Payment Intent and Payment Links requests. With this new parameter, you can use the description parameter as an internal reference of the payment, and have a custom description for your user in the statement_description parameter.