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

Changelog – Release 112

SANDBOX RELEASE DATE: 02/02/2026
PRODUCTION RELEASE DATE: 11/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

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}