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 77

SANDBOX RELEASE DATE: 8/2/2024
PRODUCTION RELEASE DATE: 21/2/2024

UI Enhancements:

  • Added a mask for the Public and Secret key in the dashboard

Added a mask for the public and secret keys, as well as the last key reset date. This provides an additional layer of security.

 Impacted Functionality: API and Settings section in Dashboard

  • UI users no longer need to manually clear their cache after release

After the release, UI users often need to clear their cache manually to enable the latest changes to be reflected. To ensure that there is no need for manual cache clearing following the release, the deployment process has been improved.

Impacted Functionality: Dashboard caching

  • Hidden disabled “Feature Options” Headers From Lower Scopes

If the header options in the “Feature Options” modal window are disabled/unticked for a specific Brand on the Global scope, these options will be hidden for the Merchant on the Brand scope in the “Feature Options” view as well.

Impacted Functionality: Feature Options modal window

  • Template Selection Bug under charges

Default Txns and Default Charges templates are now applied from the first click.

Impacted Functionality: Templates on the Charges page

  • Added filtering for subscriptions by status

Introduced a filter feature in the Dashboard to allow Merchants to search for subscriptions based on their status.
Impacted Functionality: Subscription 

  • Introduced a fix to ensure that editing a subscription does not cause the next transaction to trigger

Previously when the customer edited a subscription, the next transaction triggered even when the following frequency/interval timing was not met. A fix has been introduced to resolve this.
Impacted Functionality: Subscription 

  • Improvements made to the Dashboard, ensuring subscription updates are smoother and more reliable

Previously when ‘End Subscription’ was set to ‘Never’ on the Dashboard, there were issues with the updates. This has been fixed.
Impacted Functionality: Subscription 

API Enhancements:

  • ‘Unable to acquire ticket with mode ‘2’ within a max lock request timeout of ‘5ms’ milliseconds

The issue in the BIN service was resolved by adjusting the MongoTransactionManager configuration. Load tests were conducted to ensure improved stability in handling transactions and preventing lock timeouts.

Impacted Functionality: Application level

  • Stop automatic status checks for authorised, and refund type of charges in case the transaction is not found on the gateway side

For authorised, refunded transactions, in the scenario where there is no updated response back from the gateway after 30 days of the initial request(creation date) being sent, automatic status checks are stopped.

Impacted Functionality: Charges in ‘authorised’ and ‘refund_requested’ statuses

  • Extend the list of errors for triggering auto-reversal with MPGS

To extend the list of errors for triggering auto-reversal with MPGS by introducing gateway_specific_code: pending_processing

Impacted Functionality: Auto-reversal with MPGS

  • Unexpected error message for invalid card number

Added a generic “Invalid Card Number” error message for all validation errors received for invalid card numbers

Impacted Functionality: Charge creation

  • Report inconsistent data extract

Fixed the report data inconsistency when filtering by ‘transactions.processed_at’ range key.

Impacted Functionality: Charges reporting

Widget Enhancements:

  • Fixes introduced so that the Māori alphabet is fully supported by the SDK

Māori Character Support in Cardholder Name: the cardholder_name field in our payment widget has been enhanced to support Māori characters (ā, ē, ī, ō, ū, Ā, Ē, Ī, Ō, Ū).

Impacted Functionality: HtmlMultiWidget, HtmlWidget

  • Improved the appearance of the Mastercard logo in Payment sources widget

 Previously there were issues with the appearance of the Mastercard logo in the Payment sources widget. This has been resolved.
Impacted Functionality: Payment sources widget

  • Gift card widget is throwing “card_scheme” error

The gift_card_scheme parameter in the widget has been renamed to card_scheme, and the processing_network parameter has been renamed to card_processing_network. This is so that both the widget and the API are aligned.

Impacted Functionality: HtmlMultiWidget, HtmlWidget

  • Widget Monitoring through New Relic

Introduced widget monitoring through New Relic to ensure that our widget’s performance is monitored and issues are identified in a swift timeframe.

Impacted Functionality: New Relic & Widgets (Zippay, Afterpay V1, Paypal classic, Afterpay v2, Flypay v1, Flypay v2, Card widgets (simple and HtmlMultiWidget), visa SRC, payment source widget, Inbuilt 3ds & vault display)

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}