Changelog

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

Go to Release notes 99

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

• PRODUCTION RELEASE DATE: 21/05/2025
• SANDBOX RELEASE DATE: 07/05/2025

Go to Release notes 98

API Enhancements:

• Implemented ability to attach a standalone 3DS charge with fraud to a Direct Charge

Implemented support for attaching Fraud Charge to Standalone 3DS and then performing the Charge by providing only the 3DS Charge ID.

Impacted Functionality: Charges

• Updated Zip URL endpoints and introduced the “reference” field for refund

Updated the Zip URL endpoints for sandbox and production to ensure that we are pointing to the correct URL advised by Zip, and also introduced & mapped the reference field as mandatory for the POST /refunds request body.

Impacted Functionality: ZipPay

• Renewed Click to Pay Sandbox and Preproduction environment encryption keys

Renewed Click to Pay Sandbox and Preproduction environment encryption keys to avoid service disruption when the encryption keys expire.

Impacted Functionality: Click to Pay

• Resolved misalignment between card expiry and token expiry dates in payment source object for standalone 3DS

Addressed the misalignment between the card expiry and token expiry dates in the payment source object for standalone 3DS and ensured that the card expiry date is the information displayed.

Impacted Functionality: Gpayment (Standalone 3DS)

• Introduced a flag in the SDK for the 3DS canvas widget to control the display of the messaging

The remote-app message was updated with an optional third parameter: when set to true, the "payment confirmed" message will be visible; when set to false, it will be hidden; and if the parameter is not provided, the message will default to visible.

Impacted Functionality: Gpayment (Standalone 3DS), Remote-app

• Addressed the incorrect “Stored_On_File” value passed for Charge refunds

Implemented a fix to ensure that the correct "stored on file" value is passed for charge refunds and aligns with the expectation from MPGS when a vault token linked with NT is used as the payment source.

• 1st Direct/Authorize Charge: to_be_stored
• 1st Charge Refund: to_be_stored
• Subsequent Direct/Authorize Charge: stored
• Subsequent Charge refund: stored

Impacted Functionality: MPGS gateway

UI Enhancements:

• Removed Forwarding Institution ID from EFTPOS configuration (UI + API)

Removed the Forwarding Institution ID from the Create & Edit EFTPOS service to simplify merchant onboarding. Forwarding Institution ID is defined on environment level

Impacted Functionality: EFTPOS

• PRODUCTION RELEASE DATE: 30/04/2025
• SANDBOX RELEASE DATE: 16/04/2025

Go to Release notes 97

API Enhancements:

• Added limit for Customer payment sources

Introduced a maximum cap of 30 payment sources per customer to safeguard platform performance and avoid large-scale operations that could affect Paydock system stability. Existing customers with over 30 active payment sources remain unaffected but can no longer add new ones.

Impacted Functionality: Customers

• Extended Create Vault API response with Network Token status

Enhanced Create Vault API response with network_token_status field, providing merchants with greater visibility into the Network Token status of stored payment methods.

Impacted Functionality: Vaults

UI Enhancements:

• Displayed localised timestamps in the Checkout History tab

Timestamps in the History tab of Checkout now reflect the merchant’s local timezone, reducing confusion from UTC-based displays.

Impacted Functionality: Checkout

• Fixed the downloading All Filtered Items report with default template

Fixed the issue preventing merchants from downloading the “All Filtered Items” report using the default Charge or Transaction template. Previously, they encountered an error stating: “To create a report, you must select fields from a template. Please click the “Settings” button to choose the fields you want to include in the report.”

Impacted Functionality: Reporting

• PRODUCTION RELEASE DATE: 28/04/2025
• SANDBOX RELEASE DATE: 02/04/2025

Go to Release notes 96

API Enhancements:

• Added support for the ‘reference2’ field for Checkout

Enabled passing an optional ‘reference2’ field during the Checkout intent API and ‘Preview’ UI tab request for more granular transaction tracking.

Impacted Functionality: Checkout

• Implemented a fix to ensure CVV is sent for MPGS 3DS Inbuild
  Ensured the card verification value (CVV) is sent to MPGS during the 3DS pre-authorisation and financial charge operations, aligning with MPGS compliance requirements.

Impacted Functionality: MPGS 3DS Inbuild, Charge

• Enabled support for shipping address and options for Apple Pay and PayPal Express checkout
  Introduced support for shipping addresses and shipping options in Apple Pay and PayPal Express Checkout, enabling consumers to update shipping information and allowing merchants to adjust wallet charges accordingly.

Impacted Functionality: ApplePay and Paypal Express checkout

Widget Enhancements:

• Expanded clickable area for payment method selection in the Checkout widget

Increased the clickable area within the payment method accordion, allowing users to select an option by clicking anywhere in the box, improving usability, especially on smaller devices, without impacting responsiveness or layout.

Impacted Functionality: Checkout

• PRODUCTION RELEASE DATE: 26/03/2025
• SANDBOX RELEASE DATE: 12/03/2025

Go to Release notes 95

API Enhancements:

• Fixed incorrect “Stored_On_File” value passed for Charge refunds

Implemented a fix to ensure that the correct "stored_on_file" value is passed for charge refunds and aligns with the expectation from MPGS when a vault token linked Network Token is used as the payment source:

• 1st Direct/Authorize Charge created with session/permanent vault token - stored_on_file: to_be_stored
• 1st Charge Refund: stored_on_file: to_be_stored
• Subsequent Direct/Authorize Charge created with permanent vault tokens: stored_on_file: stored
• Subsequent Charge refund: stored_on_file: stored

Impacted Functionality: MPGS gateway

Widget Enhancements:

• Implemented Network Call Error Callbacks

Introduced an "error" callback when an issue happens during Network Calls (e.g., OTT Generation), allowing merchants to customise error handling according to their needs. This enables them to receive detailed error information and implement tailored error handling strategies.

Impacted Functionality: Widget

• Upgraded Apple Pay JS and introduced the “apple_pay_capabilities”

Upgraded the Apple Pay JS version from 3 to the latest version (14) to support new capabilities across all versions and introduced the "apple_pay_capabilities" flag to the ApplePay SDK, enabling merchants to control the display of Apple Pay buttons across different browsers for greater flexibility in customizing the user experience.

Impacted Functionality: ApplePay via MPGS

• Introduced the checkout_url and popupOriginUrl for Afterpay v2

Added the checkout_url to the wallet callback & also introduced the popupOriginUrl property to enable frontend communication for displaying the Afterpay popup.

Impacted Functionality: Afterpay v2

• Enhanced the Afterpay v2 SDK to use popup mode

Introduced the popup mode for Afterpay v2 to ensure that when a redirect URL is not available, the SDK defaults to the popup mode and passes the checkout_url in the wallet callback.

Impacted Functionality: Afterpay v2

• Fixed Non-Display of OTT in Console for Click to Pay Manual Card Entry Path

Implemented a fix to resolve the issue where the OTT was not displayed in the browser console for the Click to Pay manual card entry path.

Impacted Functionality: Click to Pay