Changelog
Back to All
improved

Release 30/01/2025

26 days ago by Alice Barrow

Version: v2025.01.29.1

Date: 30th January 2025

What's included?

  • Enhanced Retry Logic for "Do Not Honour" Declines
  • Enhancements to API Access Management

Enhanced Retry Logic for Improved Transaction Processing

We have enhanced the retry logic to provide merchants with greater flexibility and support for additional bank response codes. You can now configure retry settings in the Hub for response codes 05, 25, 26, 31, 51, and 61, based on subscription types (NONE, INIT, REBILL, REUSE) and card schemes (Visa, Mastercard).

This enhancement enables a single retry for auth_only and auth_capture transaction types by duplicating transaction fields, assigning a new transaction ID, identifying an alternative MID, and submitting the retry to the acquiring bank, flagged as a "retry." To maintain control and prevent unnecessary retries, the system ensures that a retry transaction will not trigger another retry, even if it meets the retry criteria.

Enhancements to API Access Management

We have introduced a new feature which allows merchants to manage multiple app_id values more securely and efficiently in the Hub. Using the "CREATE APP ID" button, merchants can generate multiple app_id values under a single profile. New app_id values are inactive by default, with the option to activate them later.

Check out the updated authentication guide here.

Bug Fixes

  1. Error Handling for Unsupported Currency in Payment Links:

Resolved an issue where creating a payment link at the company level using an unsupported currency (e.g., "AUD" when the company lacks an AUD MID) resulted in an error being displayed to the end user during payment in Hosted Checkout. With this fix, an appropriate error will now be returned when attempting to create the payment link for an unsupported currency, preventing the user from navigating to an invalid payment link.

  1. Consistent Display of Last 4 Digits of PAN Across Endpoints:

Fixed an issue where the last4 of the PAN was inconsistent between the GET /cards/{card_id} and GET /transactions/{transaction_id} endpoints. Previously, the transactions endpoint displayed the real card number's last4, while the cards endpoint displayed the visual card number's last4. With this fix, both endpoints now consistently return the same last4 of the real card number. Additionally, the BIN number will only be available in the GET /cards/{card_id} endpoint as expected.

  1. Webhook log filter:

There was an issue whereby filters on the webhook log page were not clearing when a different merchant was selected, this has now been resolved.

  1. Bug Fix for Special Characters in Hashcodes and Passwords:

Resolved an issue where the system generated errors when hashcodes or passwords included special characters such as &, %, <, or >. With this fix, the system now properly handles these characters without generating errors. Additionally, validation has been implemented to prevent hashcodes or passwords from being generated with unsupported characters, ensuring a seamless user experience.