Changelog#
This section lists updates to payment methods that may affect your integration. Check it regularly for changes to request fields, accepted values, and validation rules.We publish changelog entries for changes such as:| Change type | Example |
|---|
| New field | A new field is added to a payment method request |
| Removed field | A field is no longer accepted |
| New accepted value | A new value is supported for a field |
| Removed accepted value | A value is no longer supported |
| Validation change | A field gets new format, length, or content rules |
| Required field change | A field changes from optional to required, or the reverse |
Breaking vs non-breaking changes#
Changes may require updates to your integration.Breaking changes usually include:| Breaking changes |
|---|
| A field becomes required |
| A previously accepted value is no longer supported |
| Validation becomes stricter |
| A field is removed or renamed |
Non-breaking changes usually include:| Non-breaking changes |
|---|
| A new optional field is added |
| A new accepted value is added |
| Validation is relaxed |
| Date | Payment flow | Country / Currency | Payment method | Change | Merchant impact |
|---|
| YYYY-MM-DD | Pay-In | CO / COP | PSE | Added required field document_type | Update your request payload to include document_type |
| YYYY-MM-DD | Pay-Out | MX / MXN | SPEI | account_number must now contain exactly 18 digits | Validate account number format before sending requests |
| YYYY-MM-DD | Pay-Out | EC / USD | Bank Transfer | Added a new supported bank_code value | No action required unless you want to use the new bank |
Recommendation#
Before going live with a payment method, make sure your integration:1.
Sends all required fields.
2.
Uses only supported field values.
3.
Validates field formats and lengths before submitting requests.
4.
Reviews this changelog for recent updates that may affect production traffic.
Modified at 2026-04-28 08:36:34