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 74

SANDBOX RELEASE DATE: 20/11/2023
PRODUCTION RELEASE DATE: 04/12/2023

UI Enhancements:

  • “Report delivery” tab

After requesting a report on the Charges page, you are redirected to the “Report Delivery” tab. This streamlines your settings adjustments, simplifying report customization.

Impacted Functionality: The UI of the Reporting feature.

  • Add Gift cards to Smart Routing and Charge Reject

Smart Routing and Charge Reject configurations can handle gift card transactions. Create rules by adding “Gift Cards” as a payment source type to route or reject transactions, rerouting to the appropriate Gateway service. This ensures seamless processing.

Impacted Functionality: The “Gift Cards” payment source type is added to two Rule tabs: Routing and Charge Reject.

  • VII Service setup: include the Gift Card option for Smart Routing

You can now input Gift Card numbers in the UI while selecting “by Smart Routing” during charge creation. This ensures smooth transactions with the Vii service.

Impacted Functionality: When you create a direct or pre-auth charge with “Add Charge” and select “by Smart Routing”, you can enter the Gift Card number and PIN.

  • Unable to edit subscription end date

We have introduced a fix to ensure the subscription end date is updated successfully when changed.

Impacted Functionality: Subscription charges

  • UI – introduce “vault_type” in Apply Filter for the Vault page in the Dashboard

We have introduced “vault_type” as a filter on the Dashboard for the “Vault” page. This is so that you can filter for session and permanent vault tokens.

Impacted Functionality: Vault page

API Enhancements:

  • [EFTPOS] Store correlation ID for all charges sent

This enhancement stores all correlation IDs for charges that are sent on to EFTPOS (all those that are not 5XX error codes) in the charge logs additional_params.correlation_id on the Java side.

Impacted Functionality: This does not impact clients.

  • No validation for Store ID when connecting the Vii service

We have implemented an enhancement to handle specific scenarios during the Vii service setup. With this update, when you send all fields to connect to the service, we automatically remove records of any unused fields. This ensures a cleaner and more efficient setup process.

Impacted Functionality: The change affects the API part for the Vii service. When you connect the Vii service using all 5 connection fields (merchant_store_id, merchant_store_group_id, identification_code, acquiring_institution_id, and terminal_id), the system skips and does not save the identification_code, acquiring_institution_id, and terminal_id.

  • 500 “Error checking payment status” when Creating Capture Transaction

Resolved an issue with the Stripe gateway, ensuring the successful completion of capture transactions.

Impacted Functionality: A 500 error with the message ‘Error checking payment status’ is no longer sent when processing capture transactions for pre-auth charges.

  • Improve the error message for Zippay unsupported transactions

Disabled the option to capture or void a Zippay transaction for immediate payments(capture = true).

Impacted Functionality: Change applied on both UI and API. Zippay gateway – immediate payment flow.

  • Introduce validation to block the exchange of OTT (gateway_id) into Session Vault Tokens

Introduced a validation to block the exchange of OTT with gateway_id into the Session Vault Tokens. This is because they are only applicable for payment flows where card details are not_stored.

Impacted Functionality: Session vault tokens

  • Disable the ability to refund a pre-auth or create a pre-auth charge for gateways that do not support such actions

Blocked the ability to create a pre-auth charge for gateways that do not support it, and also blocked the ability to refund a pre-auth for gateways that support pre-auth charges.

Impacted Functionality: Pre-auth charges. Gateways impacted:

Afterpayv1, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Paymentexpress, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid, Worldpay

  • Restrict the ability to cancel a transaction for gateways that don’t support “Cancel”

Blocked “Cancel” operation for gateways where “Cancel” is not supported.

Impacted Functionality: “Cancel” operation for charges

Gateways Impacted:

Afterpayv1, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Paymentexpress, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid, Worldpay

  • Card Acceptor fields absent in MPGS 3DS inbuild request to MPGS

We have introduced a fix that successfully maps the card acceptor fields to the MPGS order.statement descriptor fields when they are provided in an MPGS 3DS inbuild (with the fraud inbuild) flow.

Impacted Functionality: MPGS Gateway

  • Enhancement – MPGS 3DS inbuild (send billing address fields to MPGS for 3DS authentication)

Introduced a fix to ensure that the billing information, such as the address city, address state, address country, and so on, is successfully mapped to the associated MPGS fields for the MPGS 3DS inbuild (with the fraud inbuild) flow.

Impacted Functionality: MPGS Gateway

  • When using a session vault with MPGS in-request 3DS, storedOnFile is sent as STORED – it should be sent as NOT_STORED

Implemented a fix to ensure that “NOT_STORED” is the value passed in the “StoredOnFile” field to MPGS gateway for MPGS 3DS inbuild charge created using the session vault token.

Impacted Functionality: MPGS Gateway & Session Vault tokens

  • Inability to process or decline authorised charge during fraud in review status

Implemented a fix to ensure that fraud can be processed or declined for an authorized MPGS 3DS inbuild (with the fraud inbuild) charge through the UI and API. This fix also ensures that the status in the Dashboard is accurate for such scenarios.

Impacted Functionality: MPGS Gateway

  • Report Enhancements Output

Backend supporting the new “Report Delivery” Tab to simplify configuring reports.

Impacted Functionality: Reporting.

  • Stripe Wallet Contract refactoring

Refracted the Stripe wallet contracts to align with the Paydock contract standards and created consistency among the wallet endpoints.

Impacted Functionality: Stripe wallets

  • Paypal Wallet Contract refactoring

Refracted the Paypal wallet contracts to align with the Paydock contracts standard and created consistency among the wallet endpoints.

Impacted Functionality: Paypal wallets

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}