- 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.
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
Amended the name Mastercard SRC to ClickToPay in the API, Paydock Dashboard, and widget. This ensures that there is no reference to Mastercard and that the service has a generic name (ClickToPay).
Impacted Functionality: ClickToPay(Mastercard SRC)
Improved connecting an external SFTP service by merging two previously required steps, activate and verify actions, into one. This enables all the required information to be provided during the service connection. Also introduced the “Test Connection” action that verifies whether you can connect to the external SFTP server.
Services activated prior to this change will continue to work and require no updates.
Impacted Functionality: External SFTP service connection
Enhanced the activation of the PGP encryptions service. This was achieved by adding the ability to choose between if it is required to import the externally created PGP public key, or if it is required to get the PGP public key for external usage. In the case that the “Generate Public Key” is chosen, you can then access the public key by selecting “Actions” → “Get Public Key”.
Services activated prior to this change will continue to work and require no updates.
Impacted Functionality: External SFTP service connection
The import of the PGP public key into the PGP encryption service remains unchanged.
Mapped the First Name and Last Name fields for the MPGS 3DS inbuild charges created using the Vault Tokens (session or permanent).
Impacted Functionality: Charges(3DS Inbuild)
Implemented a fix to address the inability to upload background images on the "Brand Styles" page, restoring full functionality.
Impacted Functionality: Brand white-label
Implemented a fix to address notifications that were not received after processing an in review charge with capture=false.
Impacted Functionality: Notifications
Implemented an enhancement for the response for the Vii Gateway - Check-Balance endpoint so that additional fields are sent to our merchants. The additional fields are as follows:
Impacted Functionality: Check Balance
Implemented Monitoring in New Relic that measures the end-user experience for each visit, as well as any failed requests in the widget (400, 403, 500), for HtmlWidget, HtmlMultiWidget, PaymentSourceWidget, CheckoutButton, WalletButtons, Canvas3ds, MastercardSRCClickToPay, VaultDisplayWidge widgets.
Impacted Functionality: Widgets
Rearranged the ClickToPay scheme logos to ensure the order of arrangement follows the appropriate order (Mastercard, Visa, AMEX and Discover).
Impacted Functionality: ClickToPay(Mastercard SRC) widget
Implemented a fix to ensure that the continue button does not continue to spin endlessly when an invalid mobile number is first provided in the email/mobile number input field.
Impacted Functionality: ClickToPay(Mastercard SRC) widget
Resolved an issue where screen readers failed to read error messages for the Card Number field on the Add new charge page. This fix enhances accessibility for users with visual impairments.
Impacted Functionality: Charges UI page
Resolved an issue where cancelling the pending Pre-auth or Pre-auth with the Failed Capture Transactions from the UI and API resulted in an error, while still creating Txn Type of Cancel in the In-Progress status.
Impacted Functionality: Charges
Resolved an issue that occurred for Charges at the merchant level, and Transactions at the Brand level. Previously for fields where multiple filters could be selected, once the filters were unchecked/removed in the following search, the field name continued to be displayed but was populated with a blank value. This has been resolved and the field is now removed entirely.
Impacted Functionality: Charges
Removed the "cancel" option from the Dashboard for Afterpay v1 as it is an unsupported operation for Afterpay v1.
Impacted Functionality: Charges
Implemented a change to distinguish between the previously duplicated “Get Registration” permission on the Dashboard. This ensures that there is a clear distinction between "Get Registration by ID" and "Search Registrations" for ClickToPay.
Impacted Functionality: ClickToPay(Mastercard SRC)
The existing Single Sign-On functionality that was previously available only for the “Merchant“ (Company level) has been enhanced and extended to other levels. Merchants can set up the Single Sign-On functionality. For example on the "Brand” level brand users can sign-on using this functionality.
The Single Sign-On only impacts the scope (level) where it was initially configured.
Merchants can update the Single Sign-On setup through either the Dashboard or contacting the support team.
Impacted Functionality: Single Sign-On functionality, Sign in Open
Introduced the reference
field at the transaction level for refunds for Flypay v2. This ensures that the reference
provided for the merchant's refund requests are saved in this field instead of in the transaction.external_reference
field at the transaction level.
Impacted Functionality: Flypay v2 and all other gateways
Stopped the triggering of the ‘transaction_sync’ process for charges with 3DS and active fraud without payments.
Impacted Functionality: Backend Charges
Enhanced the error messages for ‘Invalid Format ID’ to avoid showing underlying technology.
Impacted Functionality: Backend Charges
Restricted refunds for charges in the status ‘refund_requested’.
Impacted Functionality: Refunds
Enhanced the error message for check-balance when using incorrect gateways where before there was only a 500 error.
Impacted Functionality: Check Balance
Enhanced the validations to prevent capture for cancelled pre-authorisations for gateways without Auto-void.
Impacted Functionality: Charges
Fixed the remediation endpoint for the expiration warnings.
Impacted Functionality: Notifications
Changed the FatZebra reference field mapping.
Impacted Functionality: Charges
Fixed the mapping for the rejected responses for the FatZebra Bank Direct Debit integration. Previously Paydock was not mapping the rejected responses from FatZebra correctly, which resulted in the Paydock status displaying as 'completed' but the gateway status displaying as 'rejected'.
Impacted Functionality: Charges
Created the Cancel transaction by ID endpoint for the Stripe integration to enable the successful cancellation of a Capture transaction action when it is marked as “Failed” or “Pending”.
Impacted Functionality: Stripe Cancel Charge logic
Removed the old Zip logo from the Zip widget to ensure compliance with Zip branding guidelines.
Impacted Functionality: ZipMoney
Upgraded the currencies library in the UI to the latest version to ensure only valid currencies are used. Previously there was a discrepancy in the currency list on the front end and this has been resolved.
Impacted Functionality: Front-End Charges
Amended the wording for the Rules Toggle to clarify when the Rules are enabled or disabled.
Impacted Functionality: Rules Engine
Fixed the issue that occurred while navigating between the charges and transaction templates in Brand level reporting so merchants do not need to refresh the page.
Impacted Functionality: Transactions
Fixed misspelling of ‘In-Progress’ status, which was previously ‘In-Progres’.
Impacted Functionality: Transactions
Enabled both the transaction and charges fields to be displayed in the UI at the same time.
Impacted Functionality: Transactions
Improved the validation errors for ‘Custom Fields’ when creating charges.
Impacted Functionality: Transactions
Fixed the issue of the Afterpay v1 authorized charges being stuck in "in progress" status when the unsupported cancel operation is attempted, ensuring that the charge fails instead. This change was also replicated for other affected gateways.
Impacted Functionality: Afterpay, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Payment express, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid and Worldpay
Introduced support for merchants to be able to update the "reference" field for wallet charges using the POST /v1/charges/:id
endpoint and also ensured that the reference field is stored at the charge level.
Impacted Functionality: Wallets (Paypal, Afterpay v2, GooglePay, ApplePay, and Flypay v1 & v2)
Introduced report generation settings with the ability to select delimiter character, file type and quoted settings to provide merchants with more control over the report generation settings.
Impacted Functionality: Charge Reports
Extended report limit from 5 to 20 to provide merchants with the ability to create multiple reports simultaneously.
Impacted Functionality: Charge Reports
Introduced enhancement for New Zealand UNHCR to pass charge_id and transaction_id in customer fields 1 and 2 for Merchant Warrior.
Impacted Functionality: Custom Fields (Merchant Warrior)
Fixed issue whilst creating new Payment Source for FatZebra as Bank Account.
Impacted Functionality: Payment Sources
Changed the use of hardcoded configuration to environment configurations.
Impacted Functionality: Services and api-Core Micro-services
Enhanced error message for standalone refunds.
Impacted Functionality: Standalone Refunds
Added New Relic logging to the flow of creating a charge with a vault token. This is for both session and permanent vault, and ensures that it is possible to track ‘in progress’ charges in the future and identify the root cause of the issue.
Impacted Functionality: Analytics
Added logs for refunded charges created after a direct charge.
Impacted Functionality: Analytics
Resolved an issue where the resource.data.status
field was missing for customers created through a one-time token. The status field properly reflects customer status, ensuring data consistency.
Impacted Functionality: Customers
Addressed issue where it was possible to modify a customer’s payment source with a new vault token that differed from the stored one. Now, if a mismatch occurs, an error message prompts merchants, ensuring data integrity and preventing unauthorized modifications.
Impacted Functionality: Customers
Updated error messages for invalid ID formats across customer, subscription, and vault endpoints, enhancing usability and reducing confusion during troubleshooting.
Impacted Functionality: Customers, Subscriptions, Vaults
Updated the card_used
flag during subscription creation, enabling accurate tracking of card usage and enhancing subscription management.
Impacted Functionality: Subscriptions
Removed restrictions preventing the exchange of bank accounts into Session Vault Tokens and enabled the use of bank accounts for payment operations.
Impacted Functionality: Vaults
Implemented and exposed a new wallet SDK callback. Merchants can execute custom logic after the Paypal button is clicked and return a boolean flag to indicate whether the consumer can continue to make a payment or not.
Impacted Functionality: Paypal
Introduced support for the onCheckoutClose
event for wallets, Paypal, Apple Pay, and Google Pay, to ensure that merchants are aware that a customer has closed the wallet popup.
Impacted Functionality: Paypal, Apple Pay, and Google Pay
Implemented support to allow for validations to be run on button click through an onclick
callback. If validation fails for a wallet button, the wallet flow can be aborted by the merchant.
Impacted Functionality: Apple Pay, and Google Pay
Fixed the visibility issue of the "Update Subscription" button on the Subscription Details page, ensuring it is always visible for an improved user experience.
Impacted Functionality: Subscriptions
Corrected the error returned when the creation of a report fails in the UI. This is now shown as a pop-up message.
Impacted Functionality: Reporting
Fixed the error appearing in the console for the card number field on the ‘Add New Charge’ page.
Impacted Functionality: Charges
Fixed error message when custom fields are not populated and they are required.
Impacted Functionality: Charges
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