Versioning
Breaking changes
See Breaking changes in API reference.
Change log
2026-08-20
- Fixed the API documentation rendering the spec incorrectly.
- Some response fields were previously shown as optional in the rendered API documentation page even though they were required in the spec.
- This is a backwards compatible change, as the affected fields are all response fields and only go from optional to required.
2026-04-14
- Relaxed
transaction.payment_method_details.authorization_codevalidation from^[0-9A-Z]{6}$to^[0-9A-Za-z]{6}$.- This was done to support issuer authorization codes that contain lowercase letters.
- Clients with strict response validation should update their validation rule for
transaction.payment_method_details.authorization_codeaccordingly.
2026-03-11
- Added
transaction.dcc.exchange_rate_preciseto expose DCC exchange rate with higher precision thantransaction.dcc.exchange_ratesupports.- Clients should use
transaction.dcc.exchange_rate_preciseovertransaction.dcc.exchange_ratesince it is safer. - The
transaction.dcc.exchange_ratewill be replaced withtransaction.dcc.exchange_rate_precisein the next major version update.
- Clients should use
