Changelog
Back to All
improved

Release 25/03/2025

5 days ago by Alice Barrow

Release: v2025.03.25.1

Items:

  • order_id Added to funds_received Webhook for Pay by Bank Transactions
  • AVS/CVV Rule-Based Transaction Blocking Now Supported
  • Bug Fixes
    • /payments/internal-transfer incorrect ledger_id
    • Recurring type bug
    • Missing issuer_response_code and check in Reuse Payment Responses
    • Invalid Amount in Apple Pay Request Returned Server Error Instead of Bad Request
    • Made custom_data Optional in Cancel Collection API
    • Fixed Customer Search by Full Name
    • Card category in the Hub - cardholder name
    • Fixed Incorrect Card Number Display in HPP Callback and Return URLs

order_id Added to funds_received Webhook for Pay by Bank Transactions

The funds_received webhook payload now includes the order_id field to help merchants reconcile incoming payments more accurately. If the payment is linked to a Pay by Bank transaction, the order_id from the original request will be included. For manual bank transfers, the order_id field will still appear but will be set to an empty string (""). This change maintains full backward compatibility with existing integrations and helps reduce duplicate records and confusion in reconciliation processes.

Check out the webhook documentation here.

AVS/CVV Rule-Based Transaction Blocking Now Supported

Merchants can now configure rules in the Hub to automatically reject card transactions based on AVS or CVV outcome data, helping reduce potential fraud. For REST API card payments (excluding Apple Pay and Google Pay), transactions will be automatically voided if configured criteria (e.g., AVS line1 not matched) are met. Merchants will receive a blocked status with a new reason code: avs_rule or cvv_rule. This feature mirrors similar functionality offered by other gateways and reduces the need for merchants to implement this logic themselves.

Check out the documentation here. If you would like this feature enabled on your merchant, please reach out to support.

Bug Fixes

  1. /payments/internal-transfer incorrect ledger_id:

Resolved an issue in /payments/internal-transfer where incorrect verification information was returned when using ledger_id.

  1. Recurring type bug:

Updated recurring type logic for failed transactions in /payments, /payments/applepay, /payments/googlepay. When create_card or credential_on_file is true, the recurring type now correctly shows STORED CARD instead of N/A.

  1. Missing issuer_response_code and check in Reuse Payment Responses:

Fixed an issue where successful transactions made to /payments/reuse and /payments/google-pay did not include issuer_response_code or check in the response. These fields are now correctly returned for successful reuse transactions.

  1. Invalid Amount in Apple Pay Request Returned Server Error Instead of Bad Request:

Fixed an issue where requests to /payments/apple-pay with an invalid transaction.amount value incorrectly returned a server error. The API now correctly responds with a blocked status and invalid_amount reason.

  1. Made custom_data Optional in Cancel Collection API:

Updated the Cancel Collection API to make the custom_data field optional instead of required. Previously, the API incorrectly enforced custom_data, which could cause integration issues for merchants not expecting to supply this field. The endpoint now correctly allows cancellation requests without custom_data, aligning with the intended behaviour.

  1. Fixed Customer Search by Full Name:

Resolved an issue where users were unable to search for customers using their full name. Previously, the search only returned results when using either the first name or surname individually. The search functionality has been updated to support full name queries, making it easier to locate specific customers.

  1. Card category in the Hub - cardholder name:

Fixed an issue in the transaction detail view where the CARD CATEGORY heading incorrectly displayed the cardholder's name. The heading has been corrected to CARDHOLDER NAME to reflect the actual data shown.

  1. Fixed Incorrect Card Number Display in HPP Callback and Return URLs:

Fixed an issue where HPP callback and return URLs returned the network token instead of the actual card number used, causing confusion for merchants. The correct masked card number is now shown, and related views have been updated for consistency.