Changelog
Back to All
added

Release 25/02/2025

about 1 month ago by Alice Barrow

Version: v2025.02.25.1

Date: 25th February 2025

What's included?

  • Customisable Payment Method Display Order for Hosted Checkout
  • Corrected Card Storage Logic for Expiry Date Updates
  • Bug Fixes
    • Validation Error for Negative Offset in API Endpoints
    • Lloyds Void Issue
    • Shift4 Recon Report

Customisable Payment Method Display Order for Hosted Checkout

We have introduced a new feature that allows merchants to define the display order of payment methods on the Hosted Checkout page, improving flexibility and enhancing the end-user experience. Merchants can now configure the display order using the payment_methods array within the Hosted Checkout configuration page in the Hub. When enabled, the specified order will dictate how payment methods appear on the Hosted Checkout page. If no order is specified or the feature is disabled, payment methods will continue to display in the default order as per the current system behaviour. The feature dynamically adapts to exclude payment methods that are unsupported on the user’s device or unavailable due to currency constraints, while maintaining the sequence defined in the array. This update provides merchants with greater control over payment method prioritisation, aligning the display with their business strategies and user preferences.

Corrected Card Storage Logic for Expiry Date Updates

We have updated how card IDs are generated when merchants store new cards for customers. Previously, card IDs were only determined based on the customer ID, card number, and cardholder name, without considering the expiry date. This caused issues where a card with an updated expiry date would return the same card ID instead of generating a new one.

With this fix, the /payments endpoint now assigns a new card ID whenever any of the following change: cardholder name, card number, or expiry date. If network tokens are enabled, a new network token will also be provisioned. This ensures that merchants receive the correct card details and prevents issues with expired network tokens.

Bug Fixes

  1. Validation Error for Negative Offset in API Endpoints:

Improved validation across /customers, /cards, /reports/reconciliations, and other endpoints. Requests with a negative offset now return an error instead of processing incorrectly.

  1. Lloyds Void Issue:

Void transactions are now correctly blocked for Lloyds when the original transaction type is AUTH_CAPTURE and more than 30 seconds have passed since the initial authorisation. These transactions will now return response code 263 - Error: Original Transaction Already Settled, cannot Void.

  1. Shift4 Recon Report:

There was an issue whereby Account Funding Transactions were being missed, but these are now being treated as Purchase entries.