• 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 73

SANDBOX RELEASE DATE: 30/10/2023
PRODUCTION RELEASE DATE: 13/11/2023

API changes:

  • Updated Spring Boot dependencies to the latest 3.x version

Impacted Functionality: Split Payments and Encryption Services.

  • Hid permissions for metrics until they are deployed to production.

After a technical deployment during the last release, a few new permissions related to Metrics were added, but they were still not available for our users. This change is to hide these extra permissions until the functionality is fully available to our users.

Impacted Functionality: Permissions Management

  • Introduced payment source “type” field in response to 3DS charge.

Ensure the ‘payment_source.type’ is displayed accordingly in response to a pre-auth 3DS charge.

Impacted Functionality: 3DS charge.

  • Improved validation for card number field in charge creation

Enhancement to ensure that a body validation error is returned when a user attempts to create a charge using ‘card_number’ such as {{card_mpgs_sta10}}.

Impacted Functionality: Charge creation

  • Included ‘reference2’ field in request to MPGS for charge with fraud inbuild

Ensure the ‘reference2’ field is sent in the request to MPGS for charges with fraud inbuild flow.

Impacted Functionality: MPGS transactions

  • Removed Paydock phone validations from GPayments MicroService for Standalone 3ds

Ensure reliance is placed only on the GPayments validation for phone number.

Impacted Functionality: 3DS charges

  • Fixed refund error for multiple capture transactions in Dashboard & API

Implemented a fix to support refunds for multiple capture transactions.

Impacted Functionality: Refund charges

  • Corrected status display for companies’ license transactions

Implemented a fix to ensure license transaction status = ‘complete’ instead of failed when funds have been deducted successfully.

Impacted Functionality: License transactions

  • Vii gateway fields – Validation and Renaming Improvements

settings.acquiring_institution_id – field renamed, length validation added
settings.terminal_id – field renamed, length validation added
settings.identification_code – field renamed, length validation added
settings.merchant_store_id – length validation added
settings.merchant_store_group_id – length validation added

Impacted Functionality: Vii gateway fields

  • EFTPOS gateway updates – Support for prepaidDebit BIN type

Support for the prepaidDebit BIN type with EFTPOS, along with various filter logic adjustments.

Impacted Functionality: EFTPOS gateway

  • Added ‘wallet_type’ field to /charges/wallet endpoint for Apple Pay on Mobile

Ensure the wallet used for payment can be sent in the initialize wallet charge request.

Impacted Functionality: Wallet initialization

  • Enhanced Paypal integration – Pass Partner BN Code in all API calls

Introduced the Bank Notation (BN Code) as a static header for all Paypal API requests to ensure Paypal can identify if the request is from a Paydock multi-tenant (Paydock_PSP) or from a CBA single tenant (CommonwealthBankofAustralia_PSP).

Impacted Functionality: Paypal gateway

  • Webhook notification type improvement: “Standalone fraud”

Streamline webhook notifications by including only transaction-specific data, making the messages more concise and user-friendly.

Impacted Functionality: Webhook notification type: “Standalone fraud” passing transaction payload only instead of full charge logs.

UI Enhancements:

  • Accessibility Enhancements

No functional changes applied.

Impacted Functionality: Front-End – Dashboard

  • Improved UI message for report exports exceeding limit

This improvement provides a clear error message when exporting reports that exceed the limit, guiding users to utilize the ‘Request report’ option.

Impacted Functionality: If the scope of the filter exceeds 20,000 charges, the following error message displays: “The filter scope exceeds the export limit; please adjust the filter range or use the Request Report option for Charges”.

  • Afterpay field validation for minimum_amount and maximum_amount

This release includes an improvement for the ‘minimum amount’ and ‘maximum amount’ fields in the Afterpay integration.

Impacted Functionality: In the ‘Edit’ Afterpay popup, the minimum_amount and maximum_amount fields now validate and display error messages if the fields do not contain numeric values.

  • Hover to Split Payment tab

Added hover hints to the Split Payment tab when viewing bulk reference, ID, status, creation date, and update information.

Impacted Functionality: Front-end – Dashboard: Splint Payment tab

  • Unable to Edit Gate

Ensured ‘gateway label’ via the UI could be updated without having to provide the credentials again

Impacted Functionality: Gateway configuration

👋 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

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}