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 113

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

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}