Changelog

• PRODUCTION RELEASE DATE: 14/07/2025
• SANDBOX RELEASE DATE: 16/06/2025

Go to Release notes 100

API Enhancements:

• As an administrator I want to be able to integrate with multiple SSO providers regardless of their IdP Metadata format

Enhance SAML/SSO flow such that integration with identity providers whose IdP metadata contains name-spaced XML tags is possible (e.g., PingID).

Impacted Functionality: Authentication

• Per role permissions are causing the creation of access tokens to fail

Fixed an issue where roles and tfa permissions were missing purpose, occasionally leading to Forbidden Errors in the web-app when accessing the create access tokens page.

Impacted Functionality: Permissions, Permission Policies and Roles

• Search notification-templates: created_at.to filter ignores milliseconds, excluding records at the upper boundary

Allow notification templates to be filtered to the millisecond using the ISO 8601 - yyyy-mm-ddThh:mm:ss.sssZ standard on GET {{url}}/v1/notifications/templates and ensure documents on the upper boundary are included in the response. This change was made to streamline experience with respect to other similar functionalities.

Impacted Functionality: Notification Templates

• Implemented the ability to perform Standalone Fraud Check using Network Tokens with Forter

Enhanced standalone fraud check API to support network tokens with Forter, enabling merchants to leverage the security benefits of network tokenisation. Paydock will prioritise Network Tokens over raw card details when possible.

Impacted Functionality: Standalone Fraud

• Implemented the ability to perform a Standalone Fraud Check with Forter using Customer ID

Enhanced our standalone fraud check API to support passing the Customer ID with Forter. This enhancement will allow merchants to select their preferred way of integration, providing flexibility.

Impacted Functionality: Standalone Fraud

• Implemented the ability to perform Automatic Reversals in partial capture scenarios (MPGS)

Enabled merchants to Automatically Reverse the outstanding authorized amount after capture if the captured amount is less than the originally authorized amount, enabling release of the unused portion of the authorization back to the customer.

Impacted Functionality: Charges

• Fixed the issue of ApplePay transactions stuck in “in progress” status

Implemented a fix to address the issue of ApplePay wallet sale transactions processed via MPGS gateway being stuck in “in progress” to ensure seamless processing

Impacted Functionality: ApplePay via MPGS

• Removed support for the update of acquirer data for Mastercard SCOF NT registrations

Enhanced the Mastercard SCOF Network Token Registration Update by removing support for the update of acquirer data fields (ica, bin, merchant_id) to align with Mastercard's latest changes which blocked the update of the fields

Impacted Functionality: Mastercard SCOF NT registration

• Fixed the Overlap of EFTPOS service label above status and actions

Implemented a fix to address the overlapping of long EFTPOS service names across "status" and "actions" on the Rule page

Impacted Functionality: Rule page

• Enhanced the Paypal Charge log with the addition of the shipping.contact.store_name field

Uplifted the Paypal Charge log with inclusion of the shipping.contact.store_name as an additional field in the Charge log

Impacted Functionality: Paypal, Charges

.

UI Enhancements:

• As a user I want to know how many gateway services are connected on my account

Changed a card title from “Connected Services” to “Connected Gateway Services” to accurately reflect the number displayed on the card body.

Impacted Functionality: Dashboard statistics page

• As a user I want permission policies to be read-only when open in view-mode

Changed the modal used Company Users / View User / Role Permissions (read-only modal) such that it is not possible to move permission policies around, to clearly indicate that this a read-only modal. This change also includes a header message in the modal to explain why changes are not possible.

Impacted Functionality: Role permissions modal

• Merchant name character limit validation does not match API

Changed the maximum character limit to 256 up from 128 on the web-application when giving names to companies (merchants). This change was made to reflect the actual limit on backend servers.

Impacted Functionality: Merchant creation page

• As a User I want the Audit Action dropdown list is be sorted correctly and consistently

Changed Audit log action names (e.g., Create fetch) to have a consistent capitalization strategy (Create Fetch), improving scanning and sorting in “Choose Action” dropdown component within the “Audit” page.

Impacted Functionality: Audit page

• Improved Resilience When Loading Companies to ensure backward compatibility

The web-app now gracefully handles failures from the getAvailableCompanyAttributes endpoint due to missing permissions. Previously, such failures prevented companies from loading. With this enhancement, the app no longer depends on this endpoint to display companies, ensuring continued functionality even if the attribute request fails.

Impacted Functionality: Company permission

.

Widget Enhancements:

• Fixed the inability of Checkout Widget to render card scheme on autofill

Implemented a fix to ensure that the checkout widget can display the card scheme when using the autofill on browsers to populate card information

Impacted Functionality: Checkout Widget

• 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