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 92

SANDBOX RELEASE DATE: 16/01/2025
PRODUCTION RELEASE DATE: 29/01/2025

API Enhancements:

  • Introduced blocking of capture for failed Flypay v2 orders
    Implemented an enhancement to prevent the capture of failed Flypay v2 orders, ensuring merchants cannot capture such orders.
    Impacted Functionality: Flypay v2
  • Enabled cancelation of Flypay v2 charges in “wallet initialized” status
    Enabled merchants to cancel Flypay v2 charges in “wallet initialized” status, preventing abandoned wallet charges.
    Impacted Functionality: Flypay v2
  • Enabled the GPayments configuration with Master Merchant Accounts
    Implemented a fix to enable Brands or Master Merchant accounts to configure the GPayment service.
    Impacted Functionality: GPayments
  • Validated GPayments standalone 3DS request
    Introduced validation to ensure customer.payment_source.address_country & shipping.address_country are provided when customer.payment_source.address_state & shipping.address_state are provided for standalone 3DS request to GPayments.
    Impacted Functionality: Gpayments
  • Stored shipping_amount for Paypal
    Implemented an enhancement for Paypal Vaulting to store the shipping_amount within the shipping object for charge requests.
    Impacted Functionality: Paypal gateway (Paypal Vaulting)
  • Enhanced Customer Email for Paypal Vaulting
    Implemented an enhancement to prevent the Customer “Email” from being overridden by the email returned in PayPalSavePaymentSourceOTT during customer creation or modification.
    Impacted Functionality: Customer
  • Enhanced COF Field for subscriptions with Network Token (SCoF and VTS)
    Enhanced subscription processing with Network Tokens (SCoF and VTS) by ensuring the correct Credential on File (COF) fields are sent to the MPGS gateway.
    Impacted Functionality: Subscription
  • Validated required fields for AfterPay v2 init wallet charge
    Implemented validation for the required address_line1 and address_postcode for initialize wallet charge requests with Afterpay v2.
    Impacted Functionality: Afterpay v2
  • Ensured consistency in the values stored and sent to Paypal
    Implemented a fix to ensure the items amount stored at the charge level is consistent with the item_total value sent to PayPal.
    Impacted Functionality: Paypal Smart Buttons
  • Enhanced logs to tracking Network Token issues
    Extended logs with “Process Error Codes” and “Process Error Code Description” to simplify troubleshooting Network Token creation.
    Impacted Functionality: Network Tokenisation
  • Fixed fallback for deleted Network Tokens
    Ensured Vault charges with deleted Network Tokens correctly follow the card flow.
    Impacted Functionality: Network Tokenisation
  • Improved error handling for Network Token Failover
    Extended failover functionality to handle internal errors (not only scheme-related) ensuring reliable Network Token provisioning flow.
    Impacted Functionality: Network Tokenisation

Widget Enhancements:

  • Improved performance and reliability for the Payment Form widget
    Enhanced the Payment Form widget by reducing redundant API calls, modernising token generation, improving load times and reliability while maintaining backward compatibility with legacy features. Deprecated mechanisms were removed to streamline maintenance and enhance security.
    Impacted Functionality: Client SDK
  • Added asterisks to the “Mobile Number” field for Click to Pay
    Implemented a fix to display the mandatory “Mobile Number” field with an asterisk and ensure the pre-filled mobile number appears correctly in the widget UI.
    Impacted Functionality: Click to Pay
  • Enhanced PayPal DataCollector widget
    Implemented a fix to ensure that the widget initializes correctly even when the optional config (let payPalDataCollector = new paydock.PayPalDataCollector()) is not present in PayPalDataCollector.
    Impacted Functionality: PayPalDataCollector
  • Added control for Paypal Paylater messaging display
    Enabled merchants to control the display of the “Paylater messaging” for both the regular Paypal Paylater button & Paypal express checkout Paylater button.
    Impacted Functionality: Paypal & Paypal Express Checkout

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}