Changelog
Back to All
added

Release 06/05/2025

5 days ago by Alice Barrow

Release: v2025.05.06.1

Date: 6th May 2025

Items:

  • Hosted Checkout - Initial Refresh
  • New REST API Endpoint: /payments/credit (Visa Direct & Mastercard Send via Trust Payments)
  • Bug Fixes:
    • Dispute Reason Codes
    • Webhook error
    • Apple Pay issue

Hosted Checkout – Initial Visual Refresh

We’ve started rolling out visual updates to the Hosted Checkout, with more enhancements planned over the next few releases.

This release includes updated designs for the payment method selection buttons, the card form, and the Pay Now button. These updates apply to both desktop and mobile journeys and are visual only, with no changes to functionality.

New REST API Endpoint: /payments/credit (Visa Direct & Mastercard Send via Trust Payments)

We’ve introduced a new /payments/credit endpoint to support sending funds to Visa and Mastercard cards via Trust Payments, mirroring existing functionality on the Core API. This release allows REST API-integrated merchants to process credit transactions using either a card_id or full card details, with support for all required customer and billing fields. The endpoint handles all required Trust Payments mappings and ensures compatibility with both Visa Direct and Mastercard Send.

Check out the API reference here.

Bug Fixes

  1. Dispute Reason Codes:

Removed an unnecessary trailing dot from Mastercard dispute reason codes.

  1. Webhook error:

Resolved an issue where an unintended third webhook with status error was sent for a successfully settled transaction. This occurred despite the transaction being marked as executed and settled as expected. Logic has been updated to prevent erroneous status updates in similar cases.

  1. Apple Pay issue:

Resolved an issue causing recurring Apple Pay transactions to fail due to an invalid cardholder_name field. Initial Apple Pay sign-ups were successful, but follow-up payments were being declined at the gateway. This was caused by incomplete cardholder data from tokenised transactions and incorrect error mapping within the system. Cardholder details are now handled consistently to support recurring payments.