paydock logo on transparent background
  • Solutions

    Solutions

    For Banks

    For Merchants

    Generic selectors
    Exact matches only
    Search in title
    Search in content
    Post Type Selectors
    post
    page
    • Expand Market Share
    • Elevate Merchant Experience
    • Offer the Latest Payment Technology
    • Rocket Launch New Merchant Services
    • Minimising Payment Tech Risk
    • Ever Fresh Payment Experiences
    • Deep Security and Stability Uplift
    • Reporting and Reconciliation Fixes
  • Our Platform

    Our Platform​

    Paydock

    Quick Contact

    Generic selectors
    Exact matches only
    Search in title
    Search in content
    Post Type Selectors
    post
    page
    • Our Platform
    • Features
    • For Banks
    • For Merchants
    • Our Platform
    • Features
    • Contact Support
    • Our Helpdesk
    • Contact Us
  • Developers

    Developers

    Paydock

    Resources

    Generic selectors
    Exact matches only
    Search in title
    Search in content
    Post Type Selectors
    post
    page
    • Status Page
    • Documentation
    • Support
    • Our Helpdesk
    • Release Notes
    • Changelog
    • GitHub
    • Boilerplates
    • NPM
    • Responsible Disclosure
  • About

    About

    Paydock

    Newsroom

    Generic selectors
    Exact matches only
    Search in title
    Search in content
    Post Type Selectors
    post
    page
    • Values
    • Careers at Paydock
    • Our Team
    • About Us - Our History
    • Newsroom
    • Contact Us
    • Blogs
    • Press Releases
    • Podcasts
  • Search

    Generic selectors
    Exact matches only
    Search in title
    Search in content
    Post Type Selectors
    post
    page

    Most Searched

    • Features
    • Contact Us
    • Banks
    • Merchants
Get Started
Log In

Home > Changelog

Changelog

Keep up to date with all the latest changes to our code base.

Make sure to follow our Status Page for more information on product performance. We highly recommend clearing the cache in your browser after every release and keeping your Client SDK version up to date. 

 

Release Notes
Client SDK

Changelog – Release 113

  • PRODUCTION RELEASE DATE: 03/03/2026
  • SANDBOX RELEASE DATE: 18/02/2026

API Enhancements:

  • Moved Click To Pay from using Postgres to using Mongo for Tokens

As part of a wider move away from PostgreSQL, we are moving Token-based Click To Pay checkouts datastore. This change has no change from a merchant perspective.

Impacted Functionality: Click To Pay

  • Enabled reference3 to be passed to the /intent endpoint

Introduced reference3 parameter to the /intent creation endpoint and pass/store reference3 for all subsequent charges done using this intent. The main purpose is to use this field to pass information from eComm plugins and store it against charges.

Impacted Functionality: Checkout

UI Enhancements:

  • Enabled reject rules check for charges created from UI

Set enable_rejection_rules to true to fix front-end charge creation.

Impacted Functionality: Charges UI

  • Fixed pagination on Vault and Notification pages

Fixed pagination logic that incorrectly showed all items even when the selected item size is 10.

Impacted Functionality: Charges UI

  • Fixed $0 Verify charge from Dashboard UI

Fixed the amount input on verify charges that prevented customers from submitting it.

Impacted Functionality: Create Verification Charge UI

  • Fixed empty fields issue on charge creation from Dashboard UI

Fixed issue when submitting empty fields from the UI Dashboard Charge creation screen.

Impacted Functionality: Create Charge UI

  • Fix incorrect customer.payment_source.type field for wallets from Dashboard UI

Fix incorrect customer.payment_source.type for wallets being set to ‘card' instead of ’wallet' from the UI Dashboard.

Impacted Functionality: Create Wallet Charge UI

Widget Enhancements:

  • Improved PaypalDeviceDataCollector on collectDeviceData method

Improved Promise rejection handling for better merchant developer experience while integrating with the PaypalDeviceDataCollector widget.

Impacted Functionality: PayPal

  • Improved mechanism to identify the scheme when entering card details

Rebuilt the mechanism to identify a card scheme based on the real BIN list used to identify the card scheme and other card attributes in the API.

Impacted Functionality: Card widget

  • Updated AMEX logo in card input when entering card details

Updated the logo of AMEX-type cards in the card input field.

Impacted Functionality: Card widget

  • Improved validation error for minimum provided amount during intent creation

Improved validation error enhancement for POST /intent api endpoint.

Impacted Functionality: API

Changelog – Release 112

  • PRODUCTION RELEASE DATE: 11/02/2026
  • SANDBOX RELEASE DATE: 02/02/2026

API Enhancements:

  • MPGS - upgraded integration from v75 to v100

Upgraded MPGS payments API integration version to latest v100.

Impacted Functionality: MPGS integration, all flows.

  • Reject Rules evaluation enhancement for Charges processing

To prevent double evaluation, Rejection Rules are now disabled by default during standard Charge processing. Since our Analysis API is the recommended path for merchants—and already includes this logic—this change ensures a leaner, faster execution for every transaction. If needed, merchants can still explicitly trigger these rules within the Charge API by setting the "enable_rejection_rules": true flag.

Impacted Functionality: Charges

  • Implemented performance enhancements for Charges Page

We’ve boosted the speed of Charges Search, making it much faster for merchants to find exactly what they need. You can now combine multiple filters and get results faster, creating a much smoother experience. This upgrade also speeds up reporting, making data generation quicker.

Impacted Functionality: Charges, Reporting.

  • Implemented synchronisation with Wallet Charge Status prior to Checkout expiration

A synchronisation mechanism was introduced to the Checkout flow to prevent the automatic compensation (voiding or refunding) of completed wallet payments. The updated logic ensures the system waits for a final wallet status (Completed or Failed) before concluding the flow. Automatic voiding and refunding have been excluded from the expiration logic and manual cancellations will now only succeed if financial processing has not yet started.

Impacted Functionality: Checkout

  • Analysis Endpoint response enhancement

Add match_value to the analysis endpoint response when a reject rule is triggered, with the value that match the condition. (e.g. if IP is bloqued, the IP value should be the match_value).

Impacted Functionality: Analysis Endpoint.

  • Wallet Initialization custom_fields PAN validation uplift

Fix so that valid UUID values, that used to also be considered PANs by our PAN detector logic, are no longer identified as such and therefore no more validation error raised.

Impacted Functionality: Wallet Initialization with custom_fields

UI Enhancements:

  • Introduce an input popup for the Zip refund for reference field

Added a popup to input the reference for ZipMoney reference on the UI.

Impacted Functionality: ZipMoney refund flow from UI.

  • Align initialization_source for MPGS & EFTPOS

Change in the default initialization_source field passed to MPGS by default during the charge creation from UI, from INTERNET to MOTO.

Impacted Functionality: Charge creation from Dashboard.

  • Resolved validation constraint for Customer First Name in Dashboard

Updated the First Name field validation to allow a minimum of one character, ensuring users can successfully create profiles for customers with shorter names without encountering unnecessary validation errors.

Impacted Functionality: Customers

Widget Enhancements:

  • ApplePay SDK: Fix error on parsing of billing address

Fix a bug that under some SDK Meta configurations for ApplePay threw an error when parsing and processing the ApplePay Payment callback.

Impacted Functionality: ApplePayWallet and ApplePayWalletExpress

Changelog – Release 111

  • PRODUCTION RELEASE DATE: 26/01/2026
  • SANDBOX RELEASE DATE: 12/01/2026
Go to Release notes 111

API Enhancements

  • MPGS - upgraded integration from v75 to v100

Upgraded MPGS integration version to latest v100.

Impacted Functionality: MPGS integration, all flows.

  • Click to Pay – Registration Mapping Fix.

In Click To Pay registrations, the threeDSDefaultdata.defaultAcquirerBin was incorrectly mapped. This is now fixed.

Impacted Functionality: Click To Pay Registrations

.

UI Enhancements:

  • No results caused by timeout on transactions

Improved User Experience in the dashboard when certain transaction queries time out on the API.

Impacted Functionality: Dashboard Charges/Transactions list

.

Widget Enhancements:

There are no widget enhancements in this release.

Changelog – Release 110

  • 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.

Changelog – Release 109

  • 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

Contacts

Orchestrate without clutter, confusion or code. Connect a world of payments and
commerce services to your business.

Contacts

Orchestrate without clutter, confusion or code. Connect a world of payments and commerce services to your business.

Sales

[email protected]

Support

[email protected]

Partnerships

[email protected]

Talent & Careers

[email protected]

Phone: 02035144739

Media, General

[email protected]

Accounts

[email protected]

white paydock logo on transparent background

Solutions

  • For Banks
  • For Merchants

Our Platform

  • Our Platform
  • Features

Developers

  • Status Page
  • Documentation
  • Support
  • Helpdesk
  • Release Notes
  • Changelog

About

  • Values
  • Careers at Paydock
  • Team
  • About Us - Our History
  • Newsroom
  • Contact Us

Paydock Holdings Pty Limited
L40,
2 Park Street,
Sydney,
NSW 2000,
Australia

Paydock Ltd
3rd Floor,
1 Ashley Road
Altrincham,
Cheshire,
England,
WA14 2DT

  • Solutions
    • For Banks
      • Expand Market Share
      • Elevate Merchant Experience
      • Offer the Latest Payment Technology
      • Rocket Launch New Merchant Services
    • For Merchants
      • Eliminating Payment Tech Risk
      • Ever Fresh Payment Experiences
      • Deep Security and Stability Uplift
      • Reporting and Reconciliation Fixes
      • Be A Master Merchant
  • Our Platform
    • Features
  • Developers
    • Status page
    • Paydock Documentation
    • Paydock Support
    • Our Helpdesk
  • About
    • Our Values
    • Careers
    • Our Team
    • About Us
    • Newsroom
    • Contact Us
Black Linkedin Logo On Transparent Background Black Youtube Logo On Transparent Background Black Instagram Logo On Transparent Background

Copyright © Paydock 2023. All Rights Reserved | Privacy Policy | Website Terms of Use 

Manage Cookie Consent
We collect cookies to analyse our website traffic and performance.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}