Changelog
Back to All
added

Release 23/04/2025

about 1 month ago by Alice Barrow

Release: v2025.04.23.1

Date: 23rd April 2025

Items:

  • Account Updater Now Available for REST API Transactions
  • Bug fixes:
    • Improved Error Handling for Auto-Void Transactions Without 3DS in Hosted Checkout
    • Fix for Reusing Order IDs in Hosted Checkout After Decline

Account Updater Now Available for REST API Transactions

Account Updater functionality has been extended to support REST API merchants. All logic is driven by the card_id (rather than transaction_id) and applies only to cards without an active network token. When a Mastercard transaction is declined for reasons such as closed account, expired card, or lost/stolen, Acquired will trigger a SCHEMEUPDATE request via Trust Payments using the associated card data. Successful updates will result in new card details being applied to the existing card_id. Merchants will be notified of these changes through the existing card_update webhook, which now includes two new fields: update_type (set to account_updater) and update_detail (e.g. card_updated, closed_account, or no_update). Monthly batch runs are also supported where enabled, and updates will be logged in the Core API for consistency.

Check out the documentation here!

Bug fixes

  1. Improved Error Handling for Auto-Void Transactions Without 3DS in Hosted Checkout

Resolved an issue where Hosted Checkout displayed a generic error screen—rather than the expected “Payment Unsuccessful” message—when auto-void transactions were declined due to CVV/AVS rules and 3DS was not used (e.g., MOTO or tds.is_active: false). Transactions were successfully voided in the Hub, but the customer-facing messaging was unclear. This update ensures proper error feedback is shown in non-3DS flows, improving the experience for merchants relying on the auto-void feature.

  1. Fix for Reusing Order IDs in Hosted Checkout After Decline

Resolved an issue in Hosted Checkout where merchants were unable to reuse the same order_id to generate a new payment link after a transaction was declined. This behaviour was inconsistent with the /payments endpoint and impacted integrations such as WooCommerce, which rely on regenerating links without reopening the original one. Hosted Checkout now correctly allows reuse of the order_id following a declined transaction when count_retry = 1.