Release 12/03/2025

Version: v2025.03.12.1

Date: 12th March 2025

What's included?

• Reversal Endpoint
• Bug fixes:
  • Updated Card Details Display After Network Token Update
  • Apple Pay Transactions Now Return Full Customer Data
  • Hosted Check Decimal Place Bug

Reversal Endpoint (/transactions/{transaction_id}/reversal)

We've introduced a new POST /transactions/{transaction_id}/reversal endpoint to streamline the handling of voids and refunds. This endpoint automatically determines whether a transaction should be voided or refunded based on the payment's settlement status and acquiring bank rules, eliminating the need for merchants to manage separate logic. It supports both full and partial reversals, allowing flexibility in refund handling. If the transaction is still unsettled and within the acquiring bank’s same-day void window, the system will attempt a void; otherwise, it will process a refund instead. If no amount is specified, the system assumes a full reversal. Built-in validation ensures that the requested amount does not exceed the original or remaining refundable balance. This update simplifies API integrations, reducing development effort while ensuring compliance with acquiring bank policies.

Bug Fixes

1. Updated Card Details Display After Network Token Update

We have resolved an issue where the card display in the UI continued to show the old PAN and expiry date after being updated via Network Token. Now, the card details will correctly reflect the updated expiry date to prevent confusion for merchants.

2. Apple Pay Transactions Now Return Full Customer Data

We have updated the Transactions API to ensure that Apple Pay transactions now return the same customer details as Google Pay transactions when querying the /transactions endpoint. Previously, only the customer_id was provided for Apple Pay, while Google Pay included full customer details. This fix aligns the behaviour across both payment methods, making it easier for merchants to retrieve complete customer information consistently.

3. Hosted Check Decimal Place Bug

We have fixed an issue where the Acquired outcome page was incorrectly displaying amounts with one decimal place instead of two, even when two decimal places were passed in the request. Now, amounts will always be shown in the correct currency format (e.g., £1.50 instead of £1.5) for improved clarity and consistency.