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 99

SANDBOX RELEASE DATE: 27/05/2025
PRODUCTION RELEASE DATE: 10/06/2025

API Enhancements:

  • Implemented an ability to perform a standalone refund with the Fat Zebra gateway

Implemented an ability to support standalone refunds with the FatZebra Gateway for Card Payments

Impacted Functionality: Charges

  • Introduced support for ECM values to align with the COF framework (API)

Introduced support for the stored credential indicator, which is used to indicate if this is the initial recurring / instalment transaction, or the subsequent transaction, and the ECM (eCommerce Indicator) that describes the card transaction type.

Impacted Functionality: Charges

  • Implemented enhancements for the Subscription Pass Through feature for MPGS

Implemented enhancements for the Subscription Pass Through feature, including:

  • Support for in-built 3DS flow
  • Support for the agreement object and stored_on_file fields in webhook notifications
    • Transaction Success
    • Transaction Failed
    • Verification Success
    • verification Failed
  • Minor bug fixes

Impacted Functionality: Charges

  • Implemented refund response mechanism for Forter in the transaction service

Enabled sending of successful full and partial refund results to Forter for all charges with attached fraud checks, improving fraud model accuracy. No response is sent for failed refunds.

Impacted Functionality: Forter

  • Implemented a fix to ensure charge status is sent to Accertify for wallet payments

Fixed the non-receipt of status of payment on the Accertify side for Apple, Google, and Paypal charges.

Impacted Functionality: Charge, Apple, Google, Paypal, and Accertify

UI Enhancements:

  • Implemented displaying Forwarding Institution ID as a disabled field in EFTPOS connectivity

Implemented displaying the Forwarding Institution ID field as disabled with value provided by EFTPOS to Paydock in the Create/Edit EFTPOS service UI

Impacted Functionality: EFTPOS

  • Enabled multi-selecting of ‘Merchants’ in “Apply Filter” capability for charges at the Brand level

Enhanced the “Apply Filter” capability for charges to enable brands to select and filter charges for multiple merchants to aid their reporting and reconciliatory needs

Impacted Functionality: Charge

  • Implemented update to display new fields created_at and updated_at in notifications

Implemented displaying the created_at and updated_at date/time in notifications

Impacted Functionality: Notifications

white paydock logo on transparent background
👋 we are hiring self-motivated people to join our team

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
  • 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 X Logo On Transparent Background Black Youtube Logo On Transparent Background Black Instagram Logo On Transparent Background

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

 

 

Paydock Ltd
Arquen House,
4-6 Spicer Street,
St. Albans,
Hertfordshire,
England,
AL3 4PQ

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}