April 2023
April Fool's Day may be over, but our changelog is no joke!
Aggregation
🎉 New
Returning a new type of document_id
for 🇲🇽 Mexico
document_id
for 🇲🇽 MexicoWith our Owners resource, you can retrieve a new type of document_id
: RFC
(Registro Federal de Contribuyentes). This is a type of document in Mexico that owners can provide to their institution to open an account. Here’s the updated list just in case:
Added new institution type to display in the widget
There’s a new institution type you can set to display in the widget: employment
! This new type will let you display employment institutions such as IMMSS.
Check our institution types article to learn how to set it up.
Enrichment
💪 Improved
Enum BIWEEKLY
changed to FORTNIGHTLY
for accuracy
BIWEEKLY
changed to FORTNIGHTLY
for accuracyIn our Incomes response, we return the frequency
with which transactions are received. To be more precise and avoid confusion, we changed the value BIWEEKLY
to FORTNIGHTLY
to describe incomes received every two weeks. Here’s the updated list:
🐞 Fixed
Language input returns an error
We had a bug in Incomes (EYOD) that caused the language
input to return an invalid_choice error. Sorry about that! This is now fixed.
Wrong income type in Incomes
We noticed there was one wrong income_type
listed by mistake in our Incomes resource: the category PENSION
shouldn’t have been there. We fixed it right away and here’s the list:
⚠️ Deprecated
Removed institution
from our Incomes resource response
institution
from our Incomes resource responseWe decided to simplify things and remove institution
from the Incomes response.
Payment Initiation
🎉 New
New resource in the house: Payment intents!
For those using our Payment Initiation solution in 🇨🇴 Colombia (PSE), we’ve got news for you! The Payment Intents resource will walk you through the necessary steps that you need to guide your user through in order to complete the payment flow. You can check this out in our API Reference.
But that’s not all! To help you navigate the different payment intent flows, we created dedicated guides for Payment intents in 🇨🇴 Colombia (PSE) and updated our ur Postman collection so you can test them out!
And another resource: Payment webhooks!
To keep you always in the loop with your payment flows, we added Payment Webhooks to our API Reference. You can use this resource to register a payment webhook that will let you know about relevant updates that occur during the payment process (such as bank account creation, payment status updates, and so on). Of course, we’ve also updated our Payment webhooks article with this info if you want to know more. 😎
Added last_used
and created_at
info to our Secret keys resource.
last_used
and created_at
info to our Secret keys resource.We know that Secret Keys hold sensitive data and we think it’s important to know when secret keys were created and used. That’s why now with every request you make to our Secret keys resource, we return last_used
and created_at
info.
Added legal_entity
to our payment institutions
legal_entity
to our payment institutionsWe take regulatory compliance to heart! So, to be compliant with Brazil’s regulatory authority, we now return the legal_entity
name of payment institutions. Check our API Reference for more info on Payment Institutions.
💪 Improved
Bank number
now required for PSE
number
now required for PSENow the bank account number
is required for when you want to register a beneficiary bank account for PSE in Colombia 🇨🇴.
Improved description for our amount
field in Payment Links and Payment Intents
amount
field in Payment Links and Payment IntentsWhen you’re creating a payment link or a payment intent, you can actually choose to send through the amount
to be paid by your customer as:
- a string or an integer for PSE (🇨🇴 Colombia)
- a string or a float for OFPI (🇧🇷 Brazil)
We’ve added more info on these options in our request parameters to be clearer and to help you collect payments from your customers without hassle.
You can check out our Payment Links and Payment Intents resources for more info.
With ❤️, the Belvo development team.