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.
Introduced the "token_type" flag to enhance the identification of Click to Pay OTT types as either "card" or "card_scheme_token".
Impacted Functionality: Click to Pay
Implemented a fix to ensure the correct value is passed in the "StoredOnFile" field for Charge refunds. This ensure consistency between the original charge and the related refund.
Impacted Functionality: Network Token, MPGS gateway
Enhanced the external ID management for PayPal charges (Vaulting, Direct Charges, Wallets) ensuring charges can be partially voided after an initial partial capture.
Impacted Functionality: Paypal (Paypal Vaulting, Wallets, Direct Charges)
Implemented a fix to align UI and backend behaviour for access token creation. Users are restricted from selecting both UI and API permissions when creating Access Tokens.
Impacted Functionality: Access Tokens
Aligned the "Enable Vault Updates" checkbox on the Create Visa Registration Page within the Paydock Dashboard for consistency and improved user experience.
Impacted Functionality: Network Tokens
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.shipping_amount for Paypalshipping_amount within the shipping object for charge requests.PayPalSavePaymentSourceOTT during customer creation or modification.address_line1 and address_postcode for initialize wallet charge requests with Afterpay v2.amount stored at the charge level is consistent with the item_total value sent to PayPal.let payPalDataCollector = new paydock.PayPalDataCollector()) is not present in PayPalDataCollector.Migrated the Afterpay v1 URL from https://api.secure-afterpay.com.au to https://global-api.afterpay.com to ensure Afterpay requests point to the right URL on the Afterpay side.
Impacted Functionality: Afterpay v1
customer.payment_source.card_issuer in chargesFixed the mapping for customer.payment_source.card_issuer to align with the expected ‘Issuer’ value for the MPGS Gateway.
Impacted Functionality: Charges
Enhanced the following endpoints to accept customer_id or payment_source_id as the source for payment:
{{url}}/v1/charges/fraud{{url}}/v1/charges/standalone-3ds{{url}}/v1/charges/3ds{{url}}/v1/charges/verification{{url}}/v1/charges/refundsImpacted Functionality: Standalone refunds, Charges, Verification, Fraud, 3DS
Introduced a new optional field to {{url}}/v1/charges/3ds with supported values:
CHALLENGE_MANDATEDCHALLENGE_PREFERREDNO_CHALLENGENO_PREFERENCEREQUEST_TRUSTED_MERCHANT_LISTINGThis enhancement gives merchants control of how 3DS challenges are handled during a transaction, offering greater flexibility over the customer experience.
Impacted Functionality: 3DS
status_code and status_code_description fields to transaction and error summary (Verification API)Added status_code and status_code_description to transaction object and error summary in the response for /v1/charges/verification, offering further details on the occurred error.
Impacted Functionality: Verification
Enhanced the error message for Check Balance endpoint and response code = 9 from Vii when the card is temporarily locked: "The card has been temporarily locked. It will be unlocked on {{LockoutEndTime}}".
Impacted Functionality: Vii
Introduced new status code = 409 and error message = "Charges in request do not match attached charges in bulk: {:bulk_reference}" when not yet attached to the bulk charges passed:
{{url}}/v1/bulk-charges/:bulk_reference/cancel{{url}}/v1/bulk-charges/:bulk_reference/capture{{url}}/bulk-charges/:bulk_reference/fraud{{url}}/v1/bulk-charges/:bulk_reference/refundImpacted Functionality: Bulk Charges
Added the missing paymentsourceID field in the “Customer Card Expiration Warning (-1 month)” webhook event, ensuring that all customer and payment source fields are included in notifications by default.
Impacted Functionality: Notifications
Introduced the "Enable Customer Information Overwrite" checkbox for the PayPal gateway, enabling merchants to replace consumer information with payer details retrieved directly from the PayPal wallet at the charge level.
Impacted Functionality: Paypal
Updated the Payment Widget to perform a local Luhn check on the Cardholder Name; Billing details → First Name; and Billing details → Last Name fields before submission, further enhancing security.
Impacted Functionality: Widget
Restricted the usage of archived gateway for widget initialization, supported by the error message: Provide gateway_id or set default gateway.
Impacted Functionality: Widget
Updated domain for Pin Payments from pin.net.au to newly migrated pinpayments.com.
Impacted Functionality: Pin Payments
Implemented a 5-second timeout wait period to further enhance the reliability of the MastercardSCoF (Network Token) enrolment process, accounting for potential latency in the response from Mastercard.
Impacted Functionality: Network Token (MastercardSCoF)
Updated the subscription logic to resolve an issue with single retry failures, ensuring retries function correctly and reducing failed charges for merchants.
Impacted Functionality: Subscriptions
Removed the "Discover" card scheme from the list of supported schemes for Click to Pay as the Discover scheme has exited Australia.
Impacted Functionality: Click to Pay
Resolved a bug that incorrectly made AcquirerData fields mandatory when creating a Mastercard SCOF registration via the UI.
Impacted Functionality: Mastercard SCOF, Registrations
Introduced error categorisation for Reporting into “Recoverable” and “Non-Recoverable” errors, with automatic scheduling of the next report iteration for all Recoverable errors instead of Failing the report. This enhancement improves the reliability of our reporting system and reduces the need for manual intervention.
Impacted Functionality: Reporting
Fixed an issue where “Service” and “Service Name” fields were not displaying when filtering by “Subscription ID.” This fix ensures the gateway_type and gateway_name are transmitted from the backend as expected, restoring consistency in displayed data.
Impacted Functionality: Subscriptions
Resolved an issue where the Vault Token Reference and Vault Type fields were missing from the Vaults CSV download. These fields are now included in the exported CSV, providing merchants with complete vault data.
Impacted Functionality: Vaults
Fixed the issue causing a double “Accept/Decline” message to appear when the user first logs into UI.
Impacted Functionality: Dashboard
Implemented a fix to ensure the Click to Pay modal window DCF screen and Learn More messaging are centralised.
Impacted Functionality: Click to Pay
Fixed an issue where payment sources remained visible in the widget after a customer was deleted. Now, when a customer is removed, all associated payment sources are properly cleared.
Impacted Functionality: Payment Sources Widget
Fixed an issue where the direct report for a specific template didn’t work as expected and was failing or stuck loading.
Impacted Functionality: Reporting
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
