Changelog
Filter by:
August of 2025
We have included the "threeds" parameter as one of the fields returned in the GET from the Payments API. This field will provide the status of the 3DS (3D Secure) security protocol, which is used for authenticating online card transactions.
Addition
Checkout API
API Reference
Security
June of 2025
The 403 Forbidden status code was added as a possible response when creating a release report. This error includes the message "operation not allowed" and means that the report cannot be generated from the company's general account. Instead, it must be generated from the account associated with the relevant country—that is, through the account of the country for which the report is to be generated. Check Create report for more information.
Update
Reports
May of 2025
Starting from 05/07/2025, we will implement a change to the preference search endpoint: only those created within the last 90 days will be considered. Older preferences must be accessed using their ID through the corresponding endpoint. This change will be applied progressively and will be completed by 05/19/2025. For more details, visit the news.
Update
API Reference
Regularization of "external_reference" parameter in integrations
To avoid issues with transactions, update the "external_reference" parameter sent through the preferences and payments API before 10/10/2025. This field must be a maximum of 64 characters and may only contain numbers, letters, hyphens (-), and underscores (_). Special characters such as ([ ], (), ", @) are not allowed. See the documentation for more information.
Update
API Reference