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 100

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

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

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}