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 81

SANDBOX RELEASE DATE: 13/5/2024
PRODUCTION RELEASE DATE: 22/5/2024

API Enhancements:

  • Enhanced the Single Sign-On functionality and extended the functionality to other levels

The existing Single Sign-On functionality that was previously available only for the “Merchant“ (Company level) has been enhanced and extended to other levels. Merchants can set up the Single Sign-On functionality. For example on the “Brand” level brand users can sign-on using this functionality.

The Single Sign-On only impacts the scope (level) where it was initially configured.

Merchants can update the Single Sign-On setup through either the Dashboard or contacting the support team.

Impacted Functionality: Single Sign-On functionality, Sign in Open

image 5
  • Introduced the reference field at the transaction level for refunds for Flypay v2

Introduced the reference field at the transaction level for refunds for Flypay v2. This ensures that the reference provided for the merchant’s refund requests are saved in this field instead of in the transaction.external_reference field at the transaction level.

Impacted Functionality: Flypay v2 and all other gateways

  • Stopped the triggering of the ‘transaction_sync’ process for charges with 3DS

Stopped the triggering of the ‘transaction_sync’ process for charges with 3DS and active fraud without payments.

Impacted Functionality: Backend Charges

  • Updated the error message for ‘invalid format of ID’ for charges and gateways

Enhanced the error messages for ‘Invalid Format ID’ to avoid showing underlying technology.

Impacted Functionality: Backend Charges

  • Restricted the refund for charges in the ‘refund_requested’ status

Restricted refunds for charges in the status ‘refund_requested’.

Impacted Functionality: Refunds

  • Enhanced the error message for check-balance when using incorrect gateways

Enhanced the error message for check-balance when using incorrect gateways where before there was only a 500 error.

Impacted Functionality: Check Balance

  • Enhanced the validations to prevent capture for cancelled pre-authorisations

Enhanced the validations to prevent capture for cancelled pre-authorisations for gateways without Auto-void.

Impacted Functionality: Charges

  • Fixed the behaviour for the remediation endpoint for the customer payment source expiration warning

Fixed the remediation endpoint for the expiration warnings.

Impacted Functionality: Notifications

  • Changed the FatZebra reference field mapping

Changed the FatZebra reference field mapping.

Impacted Functionality: Charges

  • Fixed the mapping for the rejected responses for FatZebra

Fixed the mapping for the rejected responses for the FatZebra Bank Direct Debit integration. Previously Paydock was not mapping the rejected responses from FatZebra correctly, which resulted in the Paydock status displaying as ‘completed’ but the gateway status displaying as ‘rejected’.

Impacted Functionality: Charges

  • Introduced the Cancel transaction by ID endpoint for the Stripe service

Created the Cancel transaction by ID endpoint for the Stripe integration to enable the successful cancellation of a Capture transaction action when it is marked as “Failed” or “Pending”.

Impacted Functionality: Stripe Cancel Charge logic

Widget Enhancements:

  • Removed the old Zip logo from the Zip widget

Removed the old Zip logo from the Zip widget to ensure compliance with Zip branding guidelines.

Impacted Functionality: ZipMoney

UI Enhancements:

  • Upgraded the currencies library in the UI to the latest version to ensure only valid currencies are used

Upgraded the currencies library in the UI to the latest version to ensure only valid currencies are used. Previously there was a discrepancy in the currency list on the front end and this has been resolved.

Impacted Functionality: Front-End Charges

  • Amended the wording of the Rules toggle

Amended the wording for the Rules Toggle to clarify when the Rules are enabled or disabled.

Impacted Functionality: Rules Engine

  • Fixed the navigation between the charges and transaction level templates

Fixed the issue that occurred while navigating between the charges and transaction templates in Brand level reporting so merchants do not need to refresh the page.

Impacted Functionality: Transactions

  • Resolved the incorrect spelling of the In-Progress status

Fixed misspelling of ‘In-Progress’ status, which was previously ‘In-Progres’.

Impacted Functionality: Transactions

  • Enabled both the Transaction and Charge level fields to be displayed in the UI simultaneously

Enabled both the transaction and charges fields to be displayed in the UI at the same time.

Impacted Functionality: Transactions

  • Improved the validation errors for ‘Custom Fields‘

Improved the validation errors for ‘Custom Fields’ when creating charges.

Impacted Functionality: Transactions

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}