Changelog

• PRODUCTION RELEASE DATE: 06/01/2026
• SANDBOX RELEASE DATE: 24/12/2025

Go to Release notes 110

API Enhancements

• Click to Pay – Editable Fields Now Documented.

The Postman docs for the Click to Pay registration modify endpoint now clearly list all fields that can be updated.

Impacted Functionality: Api Docs

• Routing rules by Processing networks fix

Fix the logic when routing rules haven’t worked with the processing_networks field as expected during charge creation.

Impacted Functionality: Charge creation with Vault or Raw Card

.

UI Enhancements:

• Resolved the incorrect formatting of the cURL request in the Checkout Preview

An issue was resolved that provided an incorrectly formatted cURL command when creating a Checkout Intent in Preview, which caused execution issues due to unescaped newlines and an unnecessary single quote after the x-access-token field.

Impacted Functionality: Checkout > Preview.

.

Widget Enhancements:

There are no widget enhancements in this release.

• PRODUCTION RELEASE DATE: 06/01/2026
• SANDBOX RELEASE DATE: 10/12/2025

Go to Release notes 108

API Enhancements

• 500 Errors On Wallet Capture Endpoint

Improved error handling on the /v1/charges/wallet/capture endpoint. Timeout errors from the MPGS gateway are now handled more gracefully, ensuring clearer and more accurate error messages are returned to clients. This enhancement helps prevent unexpected 500 Internal Server Errors and improves reliability for our merchants.

Impacted Functionality: Wallets

• Extend Analysis API to Support BIN & IP Reject Rules

The /v1/routing/analysis API now supports BIN and IP-based reject rules. Merchants can block transactions by specifying an IP address or card BIN in the request. If a reject rule is triggered, the transaction is stopped before 3DS or charging. The endpoint remains backward compatible—existing integrations are unaffected if new fields are not used.

Impacted Functionality: Rules

• Incorrect storedOnfile value passed for charges & charge refund

Fixed an issue where the stored payment source flag was incorrectly set for certain charge and refund requests. Now, payments using Network Tokens are correctly marked as stored, and refund requests no longer include unnecessary payment source information. This ensures more accurate processing and compliance with gateway requirements.

Impacted Functionality: Charges

• verificationResults is empty object in Send Result Back to Forter

Updated our fraud check integration to remove empty verification results from requests sent to Forter. This change ensures cleaner data exchange and prevents unnecessary fields from being included in the request payload.

Impacted Functionality: Charges

• Data Validation for the new custom fields in wallets is not validating correctly

Resolved an issue affecting wallet payments for our merchants, where custom fields were not being validated consistently with credit card payments. The validation logic for custom fields in wallet transactions now matches that of credit cards, preventing unnecessary errors and ensuring continued support for existing integrations.

Impacted Functionality: Wallets

• Analysis endpoint enhancement - IP Address

The analysis endpoint now supports extracting the Bank Identification Number (BIN) from card or vault token, and will use the provided IP address or fall back to the source IP if not specified. This improves accuracy for rule creation and fraud analysis.

Impacted Functionality: Rules

.

UI Enhancements:

• There are no UI enhancements in this release

.

Widget Enhancements:

• Click To Pay Return Button Widget Issue

Resolved an issue where the "Return to Merchant" button in the Click to Pay widget did not redirect users as expected and caused the screen to keep spinning. Users can now successfully return to the merchant page after attempting card enrollment.

Impacted Functionality: Click to Pay

• Card widget validation error formatting

Fixed an issue where card widget validation errors (such as incomplete CVV) were displayed with incorrect formatting, showing each letter as a separate bullet point. Error messages now appear as clear, plain text for a better user experience.

Impacted Functionality: Card Widget

• PRODUCTION RELEASE DATE: 03/12/2025
• SANDBOX RELEASE DATE: 20/11/2025

Go to Release notes 108

API Enhancements:

• No API Enhancements in this release

.

UI Enhancements:

• No UI Enhancements in this release

.

Widget Enhancements:

• PayPal Vaulting Button Fix & FundingSource Enhancement

Resolved an issue where using the disableMaxHeight: true setting in the PayPal Vaulting configuration caused an unexpected fundingSource error, preventing the PayPal button from rendering correctly.

Impacted Functionality: Paypal Vaulting

• PayPal Vaulting SDK Response Fix

Fixed a bug in the PayPal Vaulting widget where the returned data structure was inconsistent. The system was incorrectly returning the payment token at the root level (response.token), rather than within the expected data object (response.data.token). The SDK has been updated to correctly return the data structure, ensuring reliability across all three key event responses: onSuccess, onError, and onCancel.

Impacted Functionality: Paypal Vaulting

• PRODUCTION RELEASE DATE: 10/11/2025
• SANDBOX RELEASE DATE: 03/11/2025

Go to Release notes 107

API Enhancements:

• Implemented CIT/MIT indicators for Cybersource gateway

Added support for Customer Initiated Transaction (CIT) and Merchant Initiated Transaction (MIT) indicator fields in Cybersource requests. This ensures accurate transaction classification and aligns with Cybersource’s compliance recommendations.

Impacted Functionality: Cybersource

• BIN Input Validation for Rule Endpoints

Introduced comprehensive validation for BIN inputs on rule creation and update endpoints. Only numeric strings of 6 or 8 digits are accepted, with matching lengths and correct range order enforced.

Impacted Functionality: Rules Engine

• Comprehensive IP Input Validation for Rule Endpoints

Added validation for IP address rules on creation and update. Ensures valid IPv4/IPv6 formats, matching IP versions in ranges, and correct ordering.

Impacted Functionality: Rules Engine

.

UI Enhancements:

• Enhanced Reporting: Timezone Display

Updated reporting functionality to reflect the selected timezone instead of defaulting to UTC, improving accuracy and clarity for users across the merchant and brand level

Impacted Functionality: Reporting

.

Widget Enhancements:

No enhancements in this release.

• PRODUCTION RELEASE DATE: 22/10/2025
• SANDBOX RELEASE DATE: 09/10/2025

Go to Release notes 106

API Enhancements:

• PayPal Authorization Expiry Mapping

Introduced and mapped the PayPal expiration_time to the Paydock authorization_expiry field for PayPal Authorized charges. This field is now visible at the charge level, ensuring merchants are aware of the authorization expiration timeline.

Impacted Functionality: Paypal Vaulting

.

UI Enhancements:

• Card Expiration Year Range Extended

Expanded the card expiration year selection range in the UI to 2039. Merchants can now select expiration years up to 2039 on the charges, subscriptions, and customer pages.

Impacted Functionality: Charges, subscriptions, and customer

• Improved Transaction Search Functionality

Implemented a fix to resolve the issue where transactions could not be retrieved when searching by first name, last name, or email within the Apply New Filter option on the Charge page.

Impacted Functionality: Charges (Apply New Filter - Search input)

• Enhanced Reporting Experience

Improved reporting to provide greater accuracy and flexibility:

• Timezone Dropdown – now includes flexible search using partial/full text or city/region for quicker selection.
• Date Range Fields (From & To) – both are optional, auto-populate from Charge page filters, and can be set during report creation.
• Mandatory Date Type – a new required field (Creation Date, Settlement Date, Update Date, or Processed At) that defines which date type is applied for the report.

These updates ensure reports align seamlessly with filter criteria and deliver more reliable results..

Impacted Functionality: Charge Reporting

• Corrected Services Page Default Behaviour for Click to Pay

Fixed an issue where the Services page defaulted to Gateway services after adding a ClickToPay service from Registration. The page now correctly reflects the selected service, preventing user confusion.

Impacted Functionality: Services page (Click to pay)

.

Widget Enhancements:

• Updated Google Pay Mark for Brand Compliance

Resolved an issue where the Google Pay mark in the checkout widget was missing the required border. The Google Pay logo mark has been updated to align with the latest brand guidelines, ensuring merchants can successfully activate Google Pay in production.

Impacted Functionality: Checkout