- 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.Â
Â
As part of a wider move away from PostgreSQL, we are moving Token-based Click To Pay checkouts datastore. This change has no change from a merchant perspective.
Impacted Functionality: Click To Pay
Introduced reference3 parameter to the /intent creation endpoint and pass/store reference3 for all subsequent charges done using this intent. The main purpose is to use this field to pass information from eComm plugins and store it against charges.
Impacted Functionality: Checkout
Set enable_rejection_rules to true to fix front-end charge creation.
Impacted Functionality: Charges UI
Fixed pagination logic that incorrectly showed all items even when the selected item size is 10.
Impacted Functionality: Charges UI
Fixed the amount input on verify charges that prevented customers from submitting it.
Impacted Functionality: Create Verification Charge UI
Fixed issue when submitting empty fields from the UI Dashboard Charge creation screen.
Impacted Functionality: Create Charge UI
Fix incorrect customer.payment_source.type for wallets being set to ‘card' instead of ’wallet' from the UI Dashboard.
Impacted Functionality: Create Wallet Charge UI
Improved Promise rejection handling for better merchant developer experience while integrating with the PaypalDeviceDataCollector widget.
Impacted Functionality: PayPal
Rebuilt the mechanism to identify a card scheme based on the real BIN list used to identify the card scheme and other card attributes in the API.
Impacted Functionality: Card widget
Updated the logo of AMEX-type cards in the card input field.
Impacted Functionality: Card widget
Improved validation error enhancement for POST /intent api endpoint.
Impacted Functionality: API
Upgraded MPGS payments API integration version to latest v100.
Impacted Functionality: MPGS integration, all flows.
To prevent double evaluation, Rejection Rules are now disabled by default during standard Charge processing. Since our Analysis API is the recommended path for merchants—and already includes this logic—this change ensures a leaner, faster execution for every transaction. If needed, merchants can still explicitly trigger these rules within the Charge API by setting the "enable_rejection_rules": true flag.
Impacted Functionality: Charges
We’ve boosted the speed of Charges Search, making it much faster for merchants to find exactly what they need. You can now combine multiple filters and get results faster, creating a much smoother experience. This upgrade also speeds up reporting, making data generation quicker.
Impacted Functionality: Charges, Reporting.
A synchronisation mechanism was introduced to the Checkout flow to prevent the automatic compensation (voiding or refunding) of completed wallet payments. The updated logic ensures the system waits for a final wallet status (Completed or Failed) before concluding the flow. Automatic voiding and refunding have been excluded from the expiration logic and manual cancellations will now only succeed if financial processing has not yet started.
Impacted Functionality: Checkout
Add match_value to the analysis endpoint response when a reject rule is triggered, with the value that match the condition. (e.g. if IP is bloqued, the IP value should be the match_value).
Impacted Functionality: Analysis Endpoint.
Fix so that valid UUID values, that used to also be considered PANs by our PAN detector logic, are no longer identified as such and therefore no more validation error raised.
Impacted Functionality: Wallet Initialization with custom_fields
Added a popup to input the reference for ZipMoney reference on the UI.
Impacted Functionality: ZipMoney refund flow from UI.
Change in the default initialization_source field passed to MPGS by default during the charge creation from UI, from INTERNET to MOTO.
Impacted Functionality: Charge creation from Dashboard.
Updated the First Name field validation to allow a minimum of one character, ensuring users can successfully create profiles for customers with shorter names without encountering unnecessary validation errors.
Impacted Functionality: Customers
Fix a bug that under some SDK Meta configurations for ApplePay threw an error when parsing and processing the ApplePay Payment callback.
Impacted Functionality: ApplePayWallet and ApplePayWalletExpress
Upgraded MPGS integration version to latest v100.
Impacted Functionality: MPGS integration, all flows.
In Click To Pay registrations, the threeDSDefaultdata.defaultAcquirerBin was incorrectly mapped. This is now fixed.
Impacted Functionality: Click To Pay Registrations
.
Improved User Experience in the dashboard when certain transaction queries time out on the API.
Impacted Functionality: Dashboard Charges/Transactions list
.
There are no widget enhancements in this release.
The Postman docs for the Click to Pay registration modify endpoint now clearly list all fields that can be updated.
Impacted Functionality: Api Docs
Fix the logic when routing rules haven’t worked with the processing_networks field as expected during charge creation.
Impacted Functionality: Charge creation with Vault or Raw Card
.
An issue was resolved that provided an incorrectly formatted cURL command when creating a Checkout Intent in Preview, which caused execution issues due to unescaped newlines and an unnecessary single quote after the x-access-token field.
Impacted Functionality: Checkout > Preview.
.
There are no widget enhancements in this release.
Improved error handling on the /v1/charges/wallet/capture endpoint. Timeout errors from the MPGS gateway are now handled more gracefully, ensuring clearer and more accurate error messages are returned to clients. This enhancement helps prevent unexpected 500 Internal Server Errors and improves reliability for our merchants.
Impacted Functionality: Wallets
The /v1/routing/analysis API now supports BIN and IP-based reject rules. Merchants can block transactions by specifying an IP address or card BIN in the request. If a reject rule is triggered, the transaction is stopped before 3DS or charging. The endpoint remains backward compatible—existing integrations are unaffected if new fields are not used.
Impacted Functionality: Rules
storedOnfile value passed for charges & charge refundFixed an issue where the stored payment source flag was incorrectly set for certain charge and refund requests. Now, payments using Network Tokens are correctly marked as stored, and refund requests no longer include unnecessary payment source information. This ensures more accurate processing and compliance with gateway requirements.
Impacted Functionality: Charges
verificationResults is empty object in Send Result Back to ForterUpdated our fraud check integration to remove empty verification results from requests sent to Forter. This change ensures cleaner data exchange and prevents unnecessary fields from being included in the request payload.
Impacted Functionality: Charges
Resolved an issue affecting wallet payments for our merchants, where custom fields were not being validated consistently with credit card payments. The validation logic for custom fields in wallet transactions now matches that of credit cards, preventing unnecessary errors and ensuring continued support for existing integrations.
Impacted Functionality: Wallets
The analysis endpoint now supports extracting the Bank Identification Number (BIN) from card or vault token, and will use the provided IP address or fall back to the source IP if not specified. This improves accuracy for rule creation and fraud analysis.
Impacted Functionality: Rules
.
.
Resolved an issue where the "Return to Merchant" button in the Click to Pay widget did not redirect users as expected and caused the screen to keep spinning. Users can now successfully return to the merchant page after attempting card enrollment.
Impacted Functionality: Click to Pay
Fixed an issue where card widget validation errors (such as incomplete CVV) were displayed with incorrect formatting, showing each letter as a separate bullet point. Error messages now appear as clear, plain text for a better user experience.
Impacted Functionality: Card Widget
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
3rd Floor,
1 Ashley Road
Altrincham,
Cheshire,
England,
WA14 2DT
Copyright © Paydock 2023. All Rights Reserved | Privacy Policy | Website Terms of Use