Release 02/09/2025

Release: v2025.09.02.1

Date: 2nd September 2025

API & Transaction Response Improvements

We’ve made several updates to our APIs and transaction responses to give you more data, flexibility, and consistency.

Transaction responses now include BIN object and authorisation code for better transparency and reconciliation.
Implemented non-breaking changes for REST API transaction structure updates, allowing a smooth migration to new response formats.
Support for multiple MID headers in /payments requests, giving merchants more control over routing and load balancing.
Fixed breaking changes in the /GET transactions endpoint and API response for merchants using the new BIN Service, ensuring field values are uppercase and commas are removed for consistency.

We’ve tackled bugs and made behind-the-scenes improvements to keep everything running smoothly.

Fixed server error when a card is not enrolled in 3DS, now returning a clear tds_failed response.
Resolved issues with stored card transactions not generating card_id or card_new webhooks (QA).
Handled reversal of successful transactions via Railsr webhook, ensuring accurate balances and clear merchant notifications.
Removed Hub limitations preventing duplicate bank parameters across MIDs, making it easier to configure new acquiring partners.
Updated dispute status logic for Cashflows representment entries, ensuring correct status transitions and merchant outcomes.
Fixed duplicate webhook notifications for certain merchants, reducing confusion and improving reliability.
Fixed bug preventing testing of INSUFFICIENT FUNDS responses for recurring payments. Read more