- Solutions
- Our Platform
Our Platform
Paydock
Quick Contact
- Developers
Developers
Paydock
Resources
- About
About
Paydock
Newsroom
Keep up to date with all the latest changes to our code base.
Make sure to follow our Status Page for more information on product performance. We highly recommend clearing the cache in your browser after every release and keeping your Client SDK version up to date.
Enhanced the card_used
flag for Vault Tokens to ensure the flag will no longer change from "false" to "true" for the following operations:
Now, only financial authorizations (direct charges; authorized charges) and verification will trigger changes to card_used
.
Impacted Functionality: Vault Token
Removed the auto-overwrite of the customer’s details (first name, last name, email, and phone number) sent in the wallet init
request with customer information extracted from the Paypal wallet. This will ensure the customer information sent in the wallet init
request is retained in the charge.
Impacted Functionality: Paypal (smart button)
Updated the error message for Edit Network Token API from "Network Token not in active/suspended status" to "The edit action is supported only for Network Tokens in active status" to improve clarity.
Impacted Functionality: Network Tokens
Added validation preventing OTT (One-Time Token) creation with an expired card.
Impacted Functionality: OTT
Introduced recognition tokens for Click to Pay to ensure consumer profiles will be remembered in case browsers stop supporting third-party cookies by utilizing recognition tokens used as first-party cookies. The implementation covers:
"Not you", "Not your cards"
, or a returning consumer unselect the "Remember Me"
checkbox.Please note this change will not impact merchants until browsers stop supporting third-party cookies. Merchants will then have to handle these events:
recognitionTokenRequested
event: triggered upon the completion of the checkout process by consumers.recognitionTokenDropped
event: occurs when new consumers click "Not you", "Not your cards"
or returning consumers unselects the "Remember Me"
checkbox.Impacted Functionality: Click to Pay
Ensured the SDK reinitialises upon signOut
to prevent cards from one Click to Pay profile from appearing in another profile within the same browser.
Impacted Functionality: Click to Pay
Introduced the "Remember Me
" checkbox option for new and returning users for Click to Pay UI flows. Also, ensured the “Remember Me"
flag is sent in the SDK calls to Mastercard for new and returning user flows.
Impacted Functionality: Click to Pay
Fixed the error “merchant_settings.acquiring_institution_id: is missing but it is required"
on Sandbox while connecting Vii Gateway.
Impacted Functionality: Vii
Resolved the issue with incorrectly calculated transaction numbers in the Dashboard Graph, ensuring the data displayed is now accurate.
Impacted Functionality: Dashboard
Enabled the UI tab to use ‘Bank Account’ as the payment source when creating a charge with FatZebra gateway.
Impacted Functionality: Dashboard
Replaced the UI widget from HelpScout to HubSpot as part of our internal platform migration.
Impacted Functionality: UI Dashboard
Fixed the issue where the Dashboard Graph failed to load for clients with large volumes of transactions.
Impacted Functionality: Dashboard
Introduced a solution to ensure the resending of the email notification from the notifications log list to a different destination (email) is correct.
Impacted Functionality: PUT /v1/notifications/logs/:id
endpoint
Implemented a solution to ensure the configuration of AU phone numbers for Visa profiles in Click to Pay, with proper format validation.
Impacted Functionality: Click to Pay
Implemented a solution to ensure that the storedOnFile
value "Stored" is correctly sent to the MPGS gateway for Click to Pay charges refunds.
Impacted Functionality: Click to Pay
Implemented a solution to prevent the missing onlinePayment Cryptogram error when processing Visa cards added to Click to Pay profiles via MPGS.
Impacted Functionality: Click to Pay
Removed Luhn checks from reference
, reference2
and reference3
fields in charge requests to prevent merchants from encountering validation errors.
Impacted Functionality: Charges
Implemented a solution to ensure subscriptions are correctly displayed when searched by Subscription ID in the Paydock dashboard. This resolves the issue where valid subscriptions were not appearing in search results, eliminating the need for manual workarounds.
Impacted Functionality: Subscription - UI section
Implemented a unified structure for error summary as documented in API Documentation. Potential impact on those customers processing the response for the endpoints below where the structure will change.
AS-IS:
Code Block |
---|
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "messages": [ { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "description": "Invalid Transaction Details", "status_code": null, "status_code_description": null } ] } } |
TO-BE:
Code Block |
---|
"error_summary": { "message": "Invalid Transaction Details", "code": "invalid_transaction_details", "details": { "gateway_specific_code": "9", "gateway_specific_description": "Invalid PIN", "messages": [ "Invalid Transaction Details" ] } } |
Impacted Functionality: Error messages
Changed maximum expiration date for all keys from 90 days to 1 year for “global” scope.
Impacted Functionality: Keys
Blocked the exchange of Click to Pay OTT into permanent Vault tokens, customers, and subscriptions flows. This is to ensure customers do not use the Click to Pay OTT (FPAN/Card scheme token), intended for one-off payments, for recurring payments.
Impacted Functionality: Click to Pay, Customer & Subscription
Introduced a fix for the Click to Pay OTP screen to ensure proper alignment of information when a user switches the OTP receipt channel from Email to Mobile.
Impacted Functionality: Click to Pay
Improved the "Signup" page by adding a text reminder to indicate that users are in the signup flow, not the sign-in flow. We have also introduced the ability to return to the previous step for better user experience.
Impacted Functionality: Sign-up flow, Frontend
Changed text for File Settings → Quotes information icon in the Request Report functionality from "When enabled, the quotes will be added to the field values in the report" to “When enabled, quotes (“) will be added to the start and end of each value in the report. Please enable this option if you expect delimiters to be populated in the report values to prevent interference with file formatting” to make it more descriptive and clear for merchants.
Impacted Functionality: Reporting
Implemented a fix ensuring that merchants can send the "card_ccv" in a request for charge creation with the Click to Pay OTT via Pin payments. Also made improvements ensuring that the card_name, if it is not sent by the merchant, can be obtained from the customer payment_source.card_name. field.
Impacted Functionality: Click to Pay, Pin Payment gateway
Implemented support for Gift cards in a standalone fraud endpoint to unify them with split fraud. Following this change, merchants can use gift cards in standalone fraud.
Impacted Functionality: Standalone Fraud
Implemented a fix to ensure that when the feature option flag is disabled for the Click to Pay registration, merchants cannot modify or revoke the registration. This has been applied at both Brand and Global levels. If the Click to Pay service is disabled, the merchant does not have the "Action" option for the service and cannot connect a new service.
Impacted Functionality: Click to Pay
Removed the fields from the fraud related API request responses that contained Null values inside fields. This does not impact existing functionality.
Impacted Functionality: Fraud API functionality
Implemented a fix to ensure that the Click to Pay card scheme token can be processed via the MPGS gateway. Also restricted the support for processing subscription to only the customer vaulted payment source.
Impacted Functionality: Click to Pay, Subscription
Introduced the ability to process subscription charges with the C2P OTT (card scheme token) through MPGS. Currently this functionality only supports the customer-vaulted payment source flow.
Impacted Functionality: Click to Pay, Subscription
Implemented a fix to enable the use of Vault tokens created from the CtP OTT (card scheme token), which then authenticate 3DS in the inbuild flow.
Impacted Functionality: Click to Pay, MPGS 3DS inbuild
Introduced a “close” event for Afterpay v1 to ensure that in the event that a customer closes the Afterpay v1 popup, a close event is sent to the merchant.
Impacted Functionality: Afterpay v1
Added a “More Information“ link for the Vii service in the Services Dashboard.
Impacted Functionality: Services
Introduced the optional "display name" field for the Click To Pay registration in the UI, ensuring that merchants can populate the field for registration.
Impacted Functionality: Click to Pay (SRC)
Deprecated the Visa SRC solution by removing it from the microservice, remote app, UI, API, Postman, and SDK at all Paydock levels (merchant, brand, global).
Impacted Functionality: Visa SRC
Implemented a fix to ensure that when modifying the details for the MPGS gateway through the Dashboard or the API associated with the wallets (ApplePay and GooglePay), the linked wallet does not disconnect with the gateway.
Impacted Functionality: MPGS
Orchestrate without clutter, confusion or code. Connect a world of payments and
commerce services to your business.
Orchestrate without clutter, confusion or code. Connect a world of payments and commerce services to your business.
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