- 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.
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
Enhanced verification status where a new column for MPGS has been added to show ‘completed’ instead of 'n/a'.
Impacted Functionality: Reporting
Fixed error where previously customers were unable to configure a Report when the 3DS fields or card acceptor fields were selected.
Impacted Functionality: Reporting
Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields in the FrontEnd.
Impacted Functionality: Charges, Subscriptions and Payment Sources
Removed a console error that occurred when opening the report creation page.
Impacted Functionality: Reporting
Improved the visibility of page content at 200% zoom, particularly focusing on the Payment Activity graph on the Dashboard and ensuring a minimum height of 45%. This enhancement aligns with accessibility guidelines (1.4.4 Resize Text, AA), which improves the user experience for individuals relying on browser zooming.
Impacted Functionality: Dashboard
Fixed an issue where previously users with the "Get current configuration" permission could interact with and change the "Auto Generate" toggle, contrary to expectations. This enhancement ensures proper access control by allowing users to view but not modify elements of the Vault Token Reference Configuration page. This prevents unauthorized changes and ensures data integrity.
Impacted Functionality: Company Permissions
Implemented a fix to resolve the issue where the Charges Template view was broken and incorrectly displaying Vault token template names. This enhancement ensures the accurate representation of the Charges Templates, improving the user experience and facilitating smooth template creation without confusion.
Impacted Functionality: Charges Templates
Amended the Afterpay v2 User-Agent Header from "custom" to "Paydock" to ensure that Afterpay can identify the Afterpay v2 requests initiated by Paydock merchants.
Impacted Functionality: Afterpay v2
Introduced support for the Afterpay v2 "popupOriginUrl", and also set the value to https://static.afterpay.com for Afterpay v2 requests initiated through the Mobile checkout. This ensures that the requests are processed.
Impacted Functionality: Afterpay v2
Implemented support for the Inbuild 3DS performance to be monitored through New-Relic Monitoring.
Impacted Functionality: New-Relic request service tracking
Resolved 500 response code that previously occurred when a customer created a charge through the Paperless Gateway and used customer bank account data.
Impacted Functionality: Paperless Gateway
Added new MPGS fields (card_funding_method, card_issuer and authorization_code) in charges.
Impacted Functionality: MPGS Gateway
Implemented the differentiation between STORED and TO_BE_STORED payment sources based on Vault Token Flags.
Impacted Functionality: MPGS Gateway
Added Vault_type in charge: services where previously Vault_type was not captured.
Impacted Functionality: Charges
Added Vault_type in charge: api-core where previously Vault_type was not captured.
Impacted Functionality: Charges
Fixed 500 error when deleting a transfer with an incorrect ID to be shown as 400.
Impacted Functionality: Transfers
Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields in the API.
Impacted Functionality: Charges, Subscriptions and Payment Sources
Added Vault Token as part a of customer.payment_source for "check balance".
Impacted Functionality: Gift Cards
Removed success operations from internal error log files.
Impacted Functionality: Internal Logs
Implemented changes to align the communication of the MPGS field sourceOfFunds.provided.card.storedOnFile
with the updated requirements. This enables more accurate handling of transactions with Paydock vault tokens by introducing new behaviour such as TO_BE_STORED
and implementing the card_used
flag. This enhances functionality overall and aligns with the MPGS requirements.
Impacted Functionality: MPGS Gateway
Implemented a new field, customer.payment_source.vault_type, in charge logs generated from subscription transactions with a permanent vault token. This enhances traceability and the completeness of logs. This improvement ensures that charge logs accurately reflect the vault type used during transactions, providing valuable visibility into payment source types.
Impacted Functionality: Charges, Subscriptions, Customers (Customer Create API endpoint)
Previously, customers could be created with a Session Vault as a Payment Source without a gateway_id, leading to unexpected behaviour. With this fix, the request now fails with a validation error message, ensuring the proper handling and preventing the unauthorized creation of customers.
Impacted Functionality: Session Vault
Previously, VTR was not being saved into charges when used during In-build fraud or Standalone 3DS flows, causing data inconsistency. With this fix, VTR is now properly saved into charges in these scenarios, ensuring accurate tracking and reporting.
Impacted Functionality: Charges, Token Management
Implemented restrictions to prevent the creation of Session Vaults with gift card or bank account payment types, aligning with expected behaviour. This fix ensures data integrity and prevents the unauthorized creation of potentially invalid vault types, improving system stability and security.
Impacted Functionality: Session Vault Token
Implemented a new feature to add a "card_used" flag in vault tokens created during one-time token flows with gateway IDs, ensuring clear differentiation between stored and to-be-stored payment sources. This enhancement improves the accuracy in data transmission to MPGS during payment sessions, and optimizes the overall system functionality and performance.
Impacted Functionality: MPGS, Vault token
Renamed the "Edit Service" button to "Save". This is for editing existing services, and the intent is to avoid confusion by making the user journey more intuitive.
Impacted Functionality: UI
Implemented restrictions to prevent users from adding new service connections for Booking services. This is applicable if two routes, GetModifiedReservations and GetNewReservations, are already connected. The system also now removes the service group from the filter in the "Add new" section.
Impacted Functionality: UI
Addressed the visibility issue of the "Save as a new template" button in the "Fields Settings" modal window on the Vault page. The button text will now be visible.
Impacted Functionality: UI
Introduced a fix to ensure that the customer payment source can be successfully updated when a customer is created through a One Time Token (OTT).
Impacted Functionality: API
Implemented a fix to ensure that a new payment source with a session vault type cannot be added for the customer.
Impacted Functionality: API, UI
Amended the Afterpay v2 cancel operation error message that is returned from "Invalid Transaction Details. The amount was less than the minimum capture amount, or more than the openToCaptureAmount.
" to "Invalid Transaction Details. Void amount exceeded open to capture amount
."
Impacted Functionality: Afterpay v2 (UI, API)
Fixed the license recurring billing for our customers.
Impacted Functionality: API merchant billing scheduler
Resolved an issue where the payment sources widget did not correctly display the card scheme logos for the Maestro and Discover cards. This fix ensures that all card logos are accurately represented, providing users with clear and recognizable payment options.
Impacted Functionality: Payment Sources Widget
Added a mask for the public and secret keys, as well as the last key reset date. This provides an additional layer of security.
Impacted Functionality: API and Settings section in Dashboard
After the release, UI users often need to clear their cache manually to enable the latest changes to be reflected. To ensure that there is no need for manual cache clearing following the release, the deployment process has been improved.
Impacted Functionality: Dashboard caching
If the header options in the “Feature Options” modal window are disabled/unticked for a specific Brand on the Global scope, these options will be hidden for the Merchant on the Brand scope in the “Feature Options” view as well.
Impacted Functionality: Feature Options modal window
Default Txns and Default Charges templates are now applied from the first click.
Impacted Functionality: Templates on the Charges page
Introduced a filter feature in the Dashboard to allow Merchants to search for subscriptions based on their status.
Impacted Functionality: Subscription
Previously when the customer edited a subscription, the next transaction triggered even when the following frequency/interval timing was not met. A fix has been introduced to resolve this.
Impacted Functionality: Subscription
Previously when ‘End Subscription’ was set to ‘Never’ on the Dashboard, there were issues with the updates. This has been fixed.
Impacted Functionality: Subscription
The issue in the BIN service was resolved by adjusting the MongoTransactionManager configuration. Load tests were conducted to ensure improved stability in handling transactions and preventing lock timeouts.
Impacted Functionality: Application level
For authorised, refunded transactions, in the scenario where there is no updated response back from the gateway after 30 days of the initial request(creation date) being sent, automatic status checks are stopped.
Impacted Functionality: Charges in ‘authorised’ and ‘refund_requested’ statuses
To extend the list of errors for triggering auto-reversal with MPGS by introducing gateway_specific_code: pending_processing
Impacted Functionality: Auto-reversal with MPGS
Added a generic "Invalid Card Number" error message for all validation errors received for invalid card numbers
Impacted Functionality: Charge creation
Fixed the report data inconsistency when filtering by ‘transactions.processed_at’ range key.
Impacted Functionality: Charges reporting
Māori Character Support in Cardholder Name: the cardholder_name field in our payment widget has been enhanced to support Māori characters (ā, ē, ī, ō, ū, Ā, Ē, Ī, Ō, Ū).
Impacted Functionality: HtmlMultiWidget, HtmlWidget
Previously there were issues with the appearance of the Mastercard logo in the Payment sources widget. This has been resolved.
Impacted Functionality: Payment sources widget
The gift_card_scheme
parameter in the widget has been renamed to card_scheme
, and the processing_network
parameter has been renamed to card_processing_network
. This is so that both the widget and the API are aligned.
Impacted Functionality: HtmlMultiWidget, HtmlWidget
Introduced widget monitoring through New Relic to ensure that our widget's performance is monitored and issues are identified in a swift timeframe.
Impacted Functionality: New Relic & Widgets (Zippay, Afterpay V1, Paypal classic, Afterpay v2, Flypay v1, Flypay v2, Card widgets (simple and HtmlMultiWidget), visa SRC, payment source widget, Inbuilt 3ds & vault display)
Important: You must update your SDK to the latest version for all changes to take effect.
Fixed critical vulnerabilities identified in the Client SDK repository
Impacted Functionality: Client SDK (Wallets, Checkout Buttons, HTML Widget, Canvas3DS)
Implemented a fix to ensure that when a charge request only contains the “amount” and “currency” properties, the application returns a 4XX error. Previously this returned a 504 Gateway time-out error. This has been amended.
Impacted Functionality: Charge creation
Implemented a fix to ensure that the application returns a 4XX error rather than a 504 Gateway time-out error when the incorrect format of the fraud charge ID is used in a request.
Impacted Functionality: Accertify (Fraud charge)
Implemented a fix so that clients can now generate reports without any size limitations.
Extended the limitation on the amount of IPs and domains that can be whitelisted.
Impacted Functionality: Reports
Implemented a fix to ensure that the flows for standalone 3DS, standalone refund and wallets are accurately monitored by New Relic.
Impacted Functionality: New Relic external request service tracking
Implemented a fix to ensure that when address details are provided during charge creation through the UI, they are sent to the gateway. Previously only the country code was sent, and so this has been amended.
Impacted Functionality: Charge creation
Implemented a critical recommendation for text colors to align with the WCBA guidelines. These are otherwise known as the Web Content Accessibility Guidelines, referenced internally by A11Y and developed by the W3C Web Accessibility Initiative (WAI). The contrast for UI elements has been enhanced, and some colours have changed.
Impacted Functionality: Front-End - Dashboard
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