What’s New?

Update to Release Note Structure
Many of our merchants have shared feedback with Paydock about how we can improve our release notes. With our latest release, we are taking the first step towards more timely, meaningful, and clear release communications. Starting with the current release, we will be separating these notes into two categories:
  • Change Logs – changes to our code base to allow our merchants to update their interaction with our APIs.
  • Release Notes – new features and integrations with more detailed explanations
This is the first of many gradual improvements towards our end goal of proactive, transparent communication of our development work. For now, you can read both types of releases below, in the same place, but we have many plans to continually improve how we share news about functions and features that are impactful with each release.

Thanks for your patience and please continue to share your thoughts and feedback. We are listening.

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!

Release 71

Production Release Date: 02/10/2023

Sandbox Release Date: 18/09/2023

  • We are delighted to announce our new Welcome Page! From now on, the Merchant will see the Welcome Page once logged in. In order to see Dashboard statistics, just click on the Dashboard from the menu on the left. To enable the Merchant to see the statistics on the Welcome Page, it is required to grant corresponding permissions – Get Welcome Statistic. The new Welcome Page can also be customized using the Brand settings.

    Welcome Page


  • We have made the Card Name field optional when creating a new charge from the Dashboard. This change simplifies the charge creation process for merchants by allowing them to decide whether to include the cardholder’s name. Impacted functionalities:
    • Pre-Auth

    • Charge

    • Refund Only

    • Verification

  • We have modified the error message displayed when an invalid Vii gift card number is used during a balance check. Going forward, users will encounter the error message “Card invalid or expired” in such instances.
  • We implemented a minor enhancement to ensure that when a preauthorized charge captured (fully or partially) is voided for the MPGS gateway, the status is set to “Cancelled” in the UI instead of “Cancel Pending”.

Release 70

Production Release Date: 06/09/2023

Sandbox Release Date: 27/08/2023

  • We’ve made a minor improvement to the Report List feature. Now, when you create a report without specifying any outputs, the ‘The channel to receive the report’ field will automatically indicate “Via link’ . This enhancement ensures clear communication of the report delivery method.
  • We’ve introduced an enhancement that allows you to remove the last Permission Policy associated with different profiles or scopes by providing greater flexibility and control over your Permission Policy management.

Release 69

Production Release Date: 16/08/2023

Sandbox Release Date: 03/08/2023

  • We have implemented the Accertify Async feature! This enhancement of the integration is aimed at receiving asynchronous responses back from Accertify and triggering respective actions based on the response. Please follow this page for more information.
  • The Notifications events have been updated with new Fraud Check actions.
  • We have added the verification feature permissions into the permissions policy for the users at the company level.

  • Enhanced filtering for the Brand’s and Company’s list. The Brand or Company will be displayed if the entered email or name matches the details of an existing Brand/Company within this Brand’s/Company’s list.

Release 68

Production Release Date: 26/07/2023

Sandbox Release Date: 11/07/2023

  • We are happy to announce that the Pre-Auth option for Split Payments is available on the Dashboard now!
  • We have enhanced Merchant onboarding by adding the presence of capital letters to the Merchant Reference field. The length for this field can be between 1 and 30 characters now.

Release 67

Production Release Date: 22/06/2023

Sandbox Release Date: 06/07/2023

  • Another release another feature… We are presenting our new Permission Policies functionality! This feature allows our merchants to create specific permission policies that can be applied to a role that can be obtained by a user. Also, the Brand Permission Policies enable our Brand users to pre-set up the policies for the Company users under their Brand. As for the existing roles with their permissions, we recommend migrating the roles under the Permission Policy entity to experience all the benefits of this change. Please follow the aforementioned guides to explore more!

  • Feature Toggles update! We always love to hear back from our clients and this is why we have re-branded our Feature Toggles for a greater customer experience. We have separated this feature into Restrictions and Feature Options. The Merchant Restrictions will help to manage the actions of the Brand’s Companies and their Users. The Feature Options in its turn enable the activation of payment gateways and services that can be connected under the specific Company.

  • We have added the Pre-Auth Charges option for Vii Gift Card on the Dashboard. The Pre-Auth Split Payment functionality will be available in the upcoming release!

  • Introducing a new Allow IP component for the Company and Brand users. Using of this option enables our Merchants to simply set up IP allowance for particular users.

  • We have enhanced the Brand Charges filter by adding a timestamp to provide even more flexibility for the Charges filter.

Release 66

Production Release Date: 14/06/2023

Sandbox Release Date: 01/06/2023

  • We are happy to introduce our new PGP Encryption Feature that enables decrypting and encrypting the Charges Reports. PGP encryption provides an extra layer of security to protect sensitive data from unauthorized access and can be utilised to encrypt various types of data, including emails, files, and messages. Encrypting reports with PGP keys ensures data integrity and consistency. Only users who own the private key for decryption can view and alter the data in the file. Go ahead and try your first encrypted charge report using these instructions!

  • Another new Feature is coming out – the brand-new Split Payments technology! As we are continuously working on implementing the Vii Gift Cards payments processing into our platform, this new feature will help to split the amount of the payment between different payment methods and the Vii Gift Card(s). This feature allows you to make a Fraud check with the created bulk charge that contains a few pre-auth charges. Currently, it is only allowed to create the bulk charge using our API. Nevertheless, the pre-auth bulk charge can be managed via our Dashboard already. The next phase is coming! Please check out our new article!

  • A new “customer.payment_source.bank_reference" field has been added to the “Field Settings” in the Charges section on the Paydock dashboard at the Merchant level. A user now can check this field to be displayed on the Charges page and in CSV Report. The field is mapped to the merchant.acquirerLink.{id}.bankMerchantId MPGS field.

Release 65

Production Release Date: 24/05/2023

Sandbox Release Date: 10/05/2023

  • We have configured a new notification email for the password reset. From now on, once your password has been updated, an email notification will be sent to your email address informing you about the successful password change.

  • We have extended the filter for Charges on our Dashboard and API with new fields – Wallet ID and Channel ID.

  • Along with the above, we have introduced new fields for the Reporting Feature. It is now possible to configure wallet ID, channel ID, Card Acceptor, and external Fraud and 3DS results fields for the Transactions and Charges view mode and for your reports. This adds more flexibility for reporting and reconciliation purposes:

  • We are introducing a new optional field when creating a new Company from your Brand account – Merchant Reference. This field can be filled out in alphanumeric format with 64 characters long. The field is optional by default, therefore it is still possible to create a Company without Merchant reference. For more details, please refer to this guide.

Release 64

Production Release Date: 21/04/2023

Sandbox Release Date: 13/04/2023

  • We are delighted to announce that we have rebranded our payment platform! It has been styled with some cozy and refreshing colors to make the experience of utilising Paydock features even more enjoyable. Please check out our brand-new Dashboard and let us know how you like the transition!
  • Implemented a new functionality for Accertify (Standalone Fraud and In-built (Gateway) fraud). Now, it is possible to send the final sale transaction results to Accertify if a Standalone Fraud request was sent to Accertify previously. So that Accertify could improve its fraud detection capabilities in the future which will enhance security. It is possible to enable this option during adding or updating the Accertify service by clicking on the ‘Send Transaction results to Accertify’ checkbox.

    Please keep in mind that to enable this option, a new validation field has been introduced – Merchant ID. You will need to fill out these details to start using a new feature. If the final sale transaction was sent to Accertify, this will be indicated on the charges logs with the additional information:

    1. Synchronization Status

    2. Log creation timestamp

    3. Error details (If any)

    4. If the transaction was not sent to Accertify successfully due to infra issues

  • Extended operations for the Vii Gift Cards. Now it is possible to utilise the following workflows:

    • Refund

    • Reversal

    • Direct Token Creation

    • Auto-Void feature – The auto-void will be triggered in case of the following errors:

      • ‘unknown_error’, ‘tcp_error’ and ‘unknown_internal_error’

    • Added an ability to check the balance using the card number and PIN with the following Endpoint:

      • POST {{url}}/charges/balance

      • { "customer":

      • {"payment_source":

      • { "card_number": "62734010001621723",

      • "card_pin": "6701",

      • "gateway_id": "{{vii_gateway_id}}" } } }

  • We have improved Standalone Refund for MPGS and EFTPOS. Now it is possible to create standalone refunds from the Dashboard using raw card data or vault tokens.

  • We have implemented a new $0 Verification flow for MPGS and EFTPOS gateways. This will help to validate customers’ data and verify credit card details. To submit this payment, go to Charges > Add New > Select Verification as the Payment Type and proceed with the payment.

Release 63

Production Release Date: 03/04/2023

Sandbox Release Date: 16/03/2023

  • We have added additional custom identifiers for requests that are being sent from Paydock to MPGS:
    • order ID – A unique identifier for this order to distinguish it from any other order you create. 
    • transaction ID – A unique identifier for this transaction to distinguish it from any other transaction on the order.

    This change allows passing the merchant-generated transaction ID & order ID into the requests made to MPGS so that these values can be used for the integration workflows with payment gateways & reconciliation purposes.

    Once those fields are passed to MPGS – they will be stored in the charge external_id field in the “order_id: transaction_id format. If one of the values was not identified by the merchant, Paydock will generate this value automatically. 

  • We have improved the naming of permissions for user and access tokens to a more user-friendly as it is for Feature Toggles. This change has affected the following instances:
    • Global → Global Users → Roles / Access Tokens
    • Brand → Brand Users → Roles / Access Tokens
    • Company → Company Users → Roles / Access Tokens

Release 62

Production Release Date: 04/03/2023

Sandbox Release Date: 16/03/2023

  • We have improved our Permissions on the Company and Brand levels. Since a different set of permissions are mostly co-dependent, we have implemented a new validation for them. Now you can see a tooltip warning “Please note, this permission has co-dependencies with the following permissions: [list of permissions]”. The permission that will be activated along with the selected one are shown in the tooltip message. This logic is applied to the permissions for:
    • Feature Toggles;
    • Company and Brand user roles;
    • Access tokens for the Company and the Brand levels.
  • Another minor update is that we have removed Reports permissions which are not being used from the user role permissions. Instead, the reporting user permissions will be located under Resource Reports.

January 12th 2023

  • Improvement: We have implemented a multi-capture flow for the Zip Money service while adding or updating the service from the dashboard. Enabling multi-capture flow will provide the ability to create multiple capture transactions under one authorized charge.
  • Improvement: We also now support the multi-capture flow for Afterpay v.2. It is possible to enable it while adding or updating the service.

December 8th 2022

  • New Feature: We have upgraded the Rules Engine by executing new routing options. Now it is possible to sort your payments by amount and using custom fields. Click here to explore our Rules feature further.
  • Improvement: ZipPay Checkout now supports fraud checking using the Accertify Fraud service for enhanced security.
  • Improvement: We have also introduced the Accertify Fraud service for our Afterpay 2.0 integration and added a multi-capture for it.

November 16th 2022

  • Improvement: We are optimising some processes to improve the overall platform performance. Some of the upcoming changes will impact Paydock Dashboard. One of them is that to view your payment activity statistic charts, you will need to load them by clicking on the Load Data button. Another change in the Charges section – as soon as you go to this section, by default, you will have a filter set to show transactions for the last week (previously it was set to the last month). But you will be able to change this filter or set up a new one as previously. These changes are expected to be released within November 17th – 18th.

November 10th 2022

  • New Feature: The Core Reporting feature is available for our Master Merchant platform now. Please click here to discover how you can create reports and send them to particular email or SFTP destinations.
  • Improvement: We have made some minor improvements to the Core Reporting feature. We have added sorting and filtering functionalities for the already created profiles in the Reports section.
  • Improvement: Our Notifications feature has been updated. We have enhanced editing options for templates and notifications and implemented an option to filter the list of notifications by action, type, and template ID.
  • Improvement: We have added the customer.payment_source.card_number_bin  field to responses for all requests to ensure our merchants always receive this necessary information.

November 1st 2022

  • New Integration: We are excited to announce a new integration that will deliver additional payment solutions for merchants – Vii Gift Card! Click here to find a simple guide on how to connect a new service.

October 28th 2022

  • New Integration: We have updated our Afterpay integration to support Afterpay 2.0. This integration for the API and widget will extend Afterpay payment options and allow our merchants to use the latest version. You can connect a new version or edit the existing version from your Dashboard and start creating new payments.
  • New Integration: We have integrated Diners Club from Discover. Click here to figure out how to connect the new service and start using it.
  • Update: We have enhanced the ZipmoneyCheckoutButton widget to redirect payment flows directly through the Zip API. Check out the new Client SDK version here.
  • Improvement: We have enhanced GPayments transactions to include more details from the response code and error description that was sent from the service.

October 17th 2022

  • New Feature: We are continuously improving our Reporting Feature. This time a few new functions were implemented. Now you have an opportunity to edit an already created report and update the settings for it. Also, you can now create a one-time link to a report you have generated and share it with your colleagues. You can set an expiry time for the link and deactivate it whenever you want. There are some display improvements as well. Go ahead and check it!
  • Update: We now support 13, 16, and 19 digits cards on the Paydock Dashboard for all gateways, to ensure we support all current and older card schemes via all supported gateways.
  • Improvement: The Charges filter has been extended for more flexibility when sorting your transactions. You can now select multiple transaction and gateway types in the filter for a more granular view of your charge data.
  • Improvement: We have improved the Standalone 3DS widget. Please make sure your Client SDK version is up to date.

September 29th 2022

  • Improvement: We have implemented some minor improvements for our new Core Reporting Feature. This time, we have extended the filters for reports and added new update configurations for them.
  • Update: As promised, we are in the process of updating the supported length of cards for all the gateways. Our widget can be used now with 13, 16, and 19 digits cards with any gateway.
  • Improvement: We have increased the limit for custom fields up to 128 characters for our Rules feature. The additional length provides more flexibility for using this feature.

September 15th 2022

  • New feature: We have implemented Charges Core Reporting, which allows you to create automated reports based on charges or transactions. Using the new functionality, you can set a custom delivery interval, customise the fields which are to be passed, and set required destinations using the external or internal SFTP service. For more information, please refer to these instructions.
  • Update: We have extended the supported length for Worldpay WPG gateway. Now, it is possible to use cards with 13, 16 and 19 digits with this gateway, to ensure all schemes and card ages are supported. In the future, this will be rolled out across other services.
  • Improvement: We are continuously improving our dashboard. Another minor update is that the name of the Brand or Company will now be displayed on the left hand side of the dashboard when logged into the Master Merchant or Merchant Paydock account.
  • Improvement: We have added an authentication.transactionid field into the MPGS payload after initiating the Authentication and Authenticate Payer operations. This field will provide more accurate information during MPGS payments.

September 2nd 2022

  • New feature: Now it is possible to delete users from your Paydock Dashboard allowing the admin to control who has access to the company or brand functionalities. To find out more on how to add and manage users, click here.
  • New Integration: SFTP service has been added to the Paydock platform which provides the ability to deliver your charge reports securely to the indicated location. To connect it to your dashboard, click on the Add New button in Services and choose Internal or External SFTP Service.
  • Improvement: Paydock is continuously improving the Mastercard service. In this release, we have added a new sourceOfFunds.provided.card.storedOnFile field for MPGS transactions which will facilitate the storing of payment details for future usage. Additionally, transaction.source is added to provide the ability to support cardholder-initiated transactions for the gateway.
  • Improvement: We have added the ability to support payment_account_reference (PAR), acquiringInstitutionId and eftposFeeCode fields for the EFTPOS service.
  • Improvement: We have upgraded the WorldPay WPG service by adding the possibility to send a MOTO (Mail Order Telephone Order) value while creating a charge through Paydock Dashboard. Here you can review how to connect to WorldPay WPG from the Paydock dashboard and start accepting payments through it.
  • Improvement: reference field has been added for CyberSource transactions so that the transactions can be identified based on the unique reference numbers.

August 19th 2022

  • Improvement: We have broadened standalone fraud requests with the ability to submit additional custom fields where you can store additional information in the charge logs. Now it is possible to add up to 25 custom fields whenever you create a charge using standalone fraud and to finalise or decline it after the fraud review.
  • Improvement: We have made a minor improvement to our ZipPay integration – ZipPay charges will store the receipt_number parameter so you can reconcile charges made via ZIP with Zip’s back-end systems.
  • Update: We have updated our policy on resetting passwords. From now on, the password reset link is only valid for 72 hours. The changes are reflected in the corresponding article.

August 5th 2022

  • New Feature: A new existing notification feature is implemented into the platform – now it is possible to create your own personal templates for webhook notifications. Customise your webhooks and choose which fields to include in the notification.

July 27th 2022

  • New Feature: We are continuously improving the flexibility of the Paydock account management and this time we are happy to inform you that we have implemented a new logic for creating account users. From now on, once the credentials for a new user are indicated, a welcome email with all the details will be sent to the entered email address. For more details, please check our corresponding Merchant and Master Merchant guides.
  • Improvement: As promised, a new enhancement for the Password Policy is released. In addition to the previous updates, there are 2 new requirements: your password must contain at least one special symbol and the password cannot be changed to any of the 15 previous ones. Please keep in mind that while resetting your password. For more information, please refer to this article.
  • Update: We have updated our framework version to make your Client SDK user experience greater. A new framework version will make widgets work faster and remove vulnerabilities.

June 24th 2022

  • Improvement: We have strengthened our security protocols to further protect your Paydock account. From 24th of June 2022, you will need to create a new password every 90 days and your new password will need to include one number and one special character and will need to be at least 14 characters in length. For more details, please refer to these instructions.
  • Stay tuned for further updates on our Password policy. Paydock continues to prioritise data security and to enhance our platform’s protocols before this is required by law. There will be more enhancements in future releases, so please continue to monitor our release notes to stay abreast of these changes.

June 10th 2022

  • New Integration: This week we’re proud to announce the release of the EFTPOS payment service! Click here to follow our simple instructions on how to connect to EFTPOS from the Paydock dashboard and start processing payments.
  • New Feature: We are happy to announce that we have implemented a new feature for webhook notifications – Basic Authentication. This feature elevates the security of your Paydock account by supporting Basic Authentication protocols for encoding webhook headers. This functionality also allows you using Paydock with other software where Basic Authentication is a must. To find out more, please refer to these instructions.

May 26th 2022

  • New Integration: We are pleased to inform you about a new payment service for our merchants – Visa SRC! Click here to follow our simple guide on how to connect Visa SRC to your Paydock dashboard and start using this payment service to obtain a frictionless shopping experience.
  • Improvement: Our team is constantly optimising and expanding our brand new Roles and Feature Toggles functionality for our Master Merchant customers with some new options.

May 12th 2022

  • Improvement: We are continually improving our Master Merchant platform for our customers. For this release, we have integrated a new functionality that allows you to manage the 2-Factor Authentication of your Brand users. Please click here to view more details.
  • Improvement: We have also updated our Client SDK with some useful improvements.

April 29th 2022

  • New Feature: We are happy to announce a new feature for the Master Merchant platform – Feature Toggles. This feature allows you to manage the features of your Merchant accounts and set permissions for them from a list. For more details, follow these instructions.
  • New Feature: We have a new name for the Brand Users feature on the Master Merchant platform. We have implemented new functionality which allows you to create custom roles for brand users and set a list of permissions for them on Master Merchant (Brand) and Merchant (Company) levels. We have also created a handy and user-friendly display for the new feature. You can read more about it in this guide. In this article you can learn how to manage your users and their permissions.
  • Improvement: We have updated our Client SDK with some user-friendly improvements. Check out the details of version 1.11.2 here.

March 31st 2022

  • New Feature: Now you can use the GPayments standalone 3DS service with your Master Merchant account. All you need to do is activate this option while adding the service to your Paydock account.
  • Improvement: We have broadened the options for using vault tokens. Now you can use vault tokens to create customers, charges, subscriptions, payment sources, and update a customer’s payment source. For more details, please refer to this guide.

March 24th 2022

  • Update: We have updated the 3DS charge flow with Mastercard by adding the Device IP address field. This improves the smooth operation of creating 3DS payments.
  • Improvement: We have added several important changes to the Fat Zebra and Flo2Cash services to bring a completely seamless experience to our Direct Debit Flow. Click here to learn how to create a new direct debit charge.
  • Improvement: To avoid confusion when creating new charges, we’ve made some minor adjustments to the NAB error mapping. These will help display the correct error reason received from the service.

February 22nd 2022

  • New Feature: We have released a brand new feature for our Master Merchant accounts – Introducing Fee Profiles! This feature enables you to set fees to charge Sub Merchants for using your services. For more information on how you can set up a Fee Profile, please refer to these instructions.
  • Update: We have made it even easier to localise your global payment experiences. Our Direct Debits processing feature can now be adapted to your public holidays in your region to ensure funds from Direct Debits are processed accurately on a working day. Find out more here.
  • Improvement: We are continually improving our Notifications feature. You can now choose to include all charge data or the last transaction to be sent via webhook notification.
  • Update: We have added new events to our Notifications feature: reversal_transaction_success, reversal_transaction_failure. This enables you to know whether a transaction has been voided (cancelled) or not.
  • Update: For our client’s security, we have added a new function for using Access Tokens. From now on, you have the option to use access tokens only with specified domain names (for UI only, e.g. when opening a widget in a browser) and from specified IP addresses (for both API and UI). If you wish to add this parameter, please refer to these instructions.

February 2nd 2022

  • Update: Payment Express has now rebranded to Windcave. Feel free to refer to these instructions to find out more about how to connect this service to your Paydock account.
  • Improvement: We have mapped Paydock’s reference’ field to WPG Worldpay’s ‘orderCode’ field to enhance our experience with the WPG Worldpay payments. If you pass an orderCode value through your Worldpay account, this data will automatically be passed through to Paydock’s reference field, enhancing your reporting and enriching your integration.
  • Improvement: We have added some optional fields to our Apple Pay and Google Pay wallet integrations. raw_data_initialization and style. You can now use your own configuration instead of Paydock’s default values for those wallets, directly through our integration. For more details, please refer to our Client SDK documentation.

January 20th 2022

  • New Feature: Introducing Standalone 3DS! This feature enables you to send a 3DS transaction separately from the sale transaction for any PSPs that support a 3DS2 flow. Click here to follow our simple guide on how to create a new 3DS charge.
  • New Integration: Paydock now supports GPayments! This new service allows you to use the standalone 3DS feature without any interruptions. Click here to find out how to connect GPayments to your Paydock account.
  • New integration: We are pleased to inform you that we have integrated the Google Pay™ wallet product for use with your Mastercard gateway. In order to connect Google Pay™ Wallet to Mastercard, please refer to these instructions.

January 14th 2022

  • New Integration: We are pleased to inform you about a new payment service for our US merchants – Worldpay WPG! Click here to follow our simple guide on how to connect Worldpay WPG to your Paydock dashboard and start accepting card and ACH payments.
  • Update: We have updated our Notifications feature by implementing new logic for a faster user experience. To set up notifications for your payment activities, please follow this link.
  • Update: We have improved the overall user experience when editing role permissions. It’s now even easier for administrators to assign permissions to users. For more details regarding user role permissions, please refer to these instructions.
  • Update: We have upgraded the two-factor authentication (2FA) flow to ensure that the security system works smoothly even if you reset a password on your Paydock account.
  • Improvement: We’re continually improving the Till Payments experience via Paydock. Merchants can now use the void feature for complete charges with this gateway. In order to connect Till Payments, please check this guide.
  • Improvement:  We have added a new ‘particulars’ field for you to be able to pass and keep more detailed information about your customers with Direct Debit. The field is available when creating charges with the Flo2Cash gateway.

November 1st 2021

  • New Feature: Introducing Shared Customer Profiles! Master merchants can enable Customer sharing among Sub-Merchants via your Master Merchant dashboard. This improvement will give possibilities to view shared customers, update them and create new charges for them and better manage sophisticated payment networks across a group. Here you can find out how to share customer profiles via the Master Merchant account.
  • New Feature: Master Merchants can create multiple admin users and track their actions from the Master Merchant dashboard. This feature significantly enhances the capabilities and scalability of the Master Merchant capability in large-scale deployments. Click here to learn how to add a new brand user.
  • Improvement: We’re continually improving the ‘Activate/deactivate merchants’ option in the Master Merchant facility. You can now pause/reinstate Merchant access tokens and API keys in a couple of clicks.
  • Update: We have added new filters to our Charges section to help you differentiate your authorised charges from those which were authorised and captured at once and include them into the charge report separately.

October 22nd 2021

  • Improvement: We have improved our Apple Pay payment integration within the SDK to speed up loading times. Please refer to our Client SDK documentation for more details.

October 15th 2021

  • New Feature: Standalone fraud workflow has taken a big boost with this update enabling fraud flows independent of charge flows. Now create ‘stand-alone’ conditional actions based on the fraud result such as initiating a charge request.
  • Improvement: We have broadened our PaymentSourceWidget capabilities by including an option to use a payment source with a vault token in the payment workflow. From now on, a vault-token payment source created with no gateway ID can be utilized in the payment source widget.
  • Improvement: We have improved our Client SDK by adding an extra validation which identifies if the iFrame is loaded before sending any request to it.

October 8th 2021

  • Update: We have updated Custom Templates in the Master Merchant platform by adding more merchant-related fields improving the ability to track transactions. This is to help master merchants reconcile and manage merchant transactions better. Example: adding ‘Company_ID’ as a custom field for all reporting and recon requirements.
  • Improvement: We have made some minor changes to the PayPal Smart Gateway fields mapping to include ‘invoice_id’ to the service connection.

October 1st 2021

  • New Feature: Activate/deactivate the ‘login’ option for merchants in the Master Merchant facility including Dashboard and API. This feature helps you manage merchant dashboard access in a couple of clicks.
  • Improvement: Upgraded the process for creating a new customer using the Flo2Cash gateway. Now you can add the bank account details in the Payment information form via Paydock Dashboard.
  • Update: We continue to deepen our gateway integrations. We have extended our First American gateway interface to support standalone refunds.

September 24th 2021

  • New Integration: Another week, another payment service. This week we’re proud to announce the release of First American payment gateway! Click here to follow our simple guide on how to connect to First American from the Paydock dashboard and start accepting payments.
  • New Feature: We have broadened the Apple Pay via MasterCard capabilities by including capability for dynamic fraud check in the payment workflow. Now your customers can have better security and reduced fraud risk when paying with their preferred wallet.
  • Update: Split Payments has now rebranded to Zepto. Feel free to refer to these instructions to find out more about how to connect this service to your Paydock account.

September 17th 2021

  • Improvement: We have improved the logic for displaying the status of BSB charges arising from the Flo2Cash gateway improving the ability for Merchants to reconcile and track their transactions by their statuses.
  • Improvement: We’re continually improving the MasterCard ApplePay experience via Paydock. Now Merchants can pass customer shipping details to the checkout flow for even more seamless checkout experience. To use this option for your widget, you will need to include the identifications depending on the use case.
  • ImprovementWe have added a ‘Payment Source Type’ column to the Charges section, identifying the type of Payment Source used for each payment, this includes wallet (e.g. Paypal, Apple Pay, Google Pay), card or bank account. The Payment Source Type details will help Merchants with Recon & Reporting.

September 10th 2021

  • New Integration: Paydock now supports Moneris, underlining our continued promise to deliver premium orchestration payments solutions for merchants. Click here to find out how to connect Moneris to your Paydock account.
  • New Integration: US Merchants can now enjoy our direct connection to Elavon, an innovative, secure, and global partner for your payment processing needs. To find out how to connect to this service from your Paydock account, please click here.
  • New Feature: We are excited to announce that we have launched support for Stripe ACH. Click here to find out how to connect Stripe to your Paydock account.

September 3rd 2021

  • Update: We have made further improvements to our MasterCard Apple Pay payments. Now you are able to customize the checkout button while creating an Apple Pay charge.
  • Update: We have extended the PayPal Classic transaction response with a shipping address chosen at Paypal when confirming the payment. This improvement will help merchants access and store more information about their customers.

August 26th 2021

  • New Feature: We have broadened the PayPal Smart Button gateway capabilities to include Fraud service support, providing better security and reduced fraud risk. Click here to find out about the PayPal fraud service flow.
  • New Feature: We have added further improvements to the Till Payments gateway. This service now supports multiple captures, making your transaction experience easier. Click here to find out how to capture your authorized charge.
  • Improvement: We have extended the gateway response for the Mastercard gateway. Now you can find the connected wallet (e.g. Apple Pay, Google Pay) in the response after creating a gateway with a wallet.
  • Improvement: We have improved the PayPal refund flow. Now the payments processed with PayPal Classic which were refunded, will have the “Refunded/Failed” status immediately after the refund issuance.
  • Improvement: We continue to optimize the Paydock Dashboard. To simplify the navigation experience, the ‘SSO Setup’ and ‘API & Settings’ configurations are now located in the ‘My Company’ tab.
  • Improvement: We have tweaked the Company Information fields in the Master Merchant platform to make them easier to understand. You can read more about our Master Merchant platform here.

August 19th 2021

  • Update: Upgraded licencing is now available for Master Merchant accounts to enable manual billing options.
  • Update: Improved Charge filter flexibility to enable multiple statuses while searching for Charges. It is possible to select more than one status in the Charges tab or via API. For more information, please check this documentation.
  • Improvement: To prevent confusion, we have changed the error message when accessing the Paydock account and API endpoints from an unwhitelisted IP address where IP restrictions are in place. Now the user will receive the “Invalid Credentials or the IP address is not whitelisted” error message while trying to connect to the Paydock account from an IP address which is not added to the whitelist. For more details regarding the whitelist IPs, please refer to these instructions.

August 12th 2021

  • Improvement: We have added the possibility to set a custom order of default and non-default bank account and card fields in our widget, giving you even more control of how these fields are displayed to your customers.
  • Improvement: We have revised the 3DS statuses and extended the list with  ‘authentication_not_in_effect’ and ‘authentication_exempt’ that can give even more insight on what has happened during the 3DS flow. Now, merchants can see all authentication statuses from the Mastercard gateway on the Paydock side.
  • Improvement: We have introduced a new ‘reference2’ field and revised the mapping of reference fields with MPGS so that you can make the utmost use of the information passed from and stored at Paydock.

August 6th 2021

  • New Integration: We are pleased to inform you that we have integrated our next Apple Pay supported service! Now you can use it with your Mastercard gateway or any gateway authorised by ApplePay. In order to connect Apple Pay Wallet with Mastercard, please refer to these instructions.
  • Improvement: We have extended the logic of our notifications engine. Now notifications can cover events triggered manually such as a manual charge status update. To find out more about the notification creation, click here.
  • Improvement: We’ve tweaked our widget to dynamically show card scheme logos based on card entry. For more details, click here.
  • Improvement: Introduced a handy filter to enable merchants to dive into Charges and separate out specific Transaction types via the Charges tab. This allows merchants to drill into a Transaction workflow associated with any Charge. You can find out more about our filter parameters by clicking this link.

July 30th 2021

  • Improvement: We have added a possibility to create custom templates for Charges and Transactions for Master Merchant accounts. For more details on how to create a Master Merchant account, please check this article.
  • Improvement: We have extended the transaction response with the fraud ‘reason’ field. If the payment was rejected due to fraud, the transaction response will include the cause value of the rejected transaction. This saves time and enables downstream automated actions.

July 23rd 2021

  • New Feature: We have broadened Till Payments gateway capabilities to include full 3DS support providing for better security and reduced fraud.
  • New Feature: Flo2Cash supports Direct Debit payments! This feature allows merchants to create direct debit plans and schedule Charges against it using the Paydock native API. Click here to read more.
  • New Feature: Manually update Charge statuses. Since some processors do not have the ability to provide statuses of their charges/transactions in a platform addressable manner, Paydock provides an easy to use tool that can help you display the correct status.
  • Improvement: Pre-save filter templates! Now you can not only pre-save chosen fields and labels in your custom Charges or Transactions templates but also the pre-set filters saving you time and providing more value from the Paydock dashboard. You won’t need to choose the required filters again and again when working on reports, which makes Paydock a greater tool to rely on for payments reconciliation. For more details, please refer to this article.

July 16th 2021

  • Update: Tuned MasterCard gateway connection with merchants now enjoying the option to process charges with or without 3DS authentication workflows, providing more choice in their payment strategies.
  • Update: Upgraded live payments data in the Paydock Dashboard to provide better transparency on charges with the ‘Authorised’ charge status.
  • Update: Introduced a handy filter enabling merchants to track Charges with a “Search by Transaction Type” on the Charges section. This allows merchants to identify target transactions even faster.
  • Update: We have updated the SSO feature to include the ability to sign a SAML Request. Now, the SSO as an authentication capability grants users access to multiple applications in a new security level.

July 9th 2021

  • New Feature: Now you are able to capture a custom amount for the authorised charges using the Paydock dashboard. This feature can help you choose any amount required for capturing. The captured amount should be less or equal to the authorised amount.
  • Improvement: The Adyen live URL can be generated according to the Adyen API documentation. This improvement will help to communicate with the Adyen live API endpoints and have a seamless experience when using the Adyen gateway.

July 2nd 2021

  • New Feature: Introducing our Vault-as-Payment Source! Merchants can now create Vault Tokens independent of any connection to a gateway. This vault token is created on the Paydock side only and does not pass a gateway_id when creating a payment source. With this feature, you can easily switch between various gateways using only one set of payment details against multiple service providers. This enables greater flexibility and agility in defining an orchestration-first payments strategy. To find out more about the Vault-as-Payment Source feature click here.
  • Update: We have upgraded the Paydock 3DS transaction object to include  ‘gateway_status’ and ‘challenge’ parameters. Now, merchants can benefit from 3DS authentication in the Mastercard gateway by checking the ‘gateway_status’ parameter. The ‘challenge’ parameter provides visibility of how the 3DS flow has been passed by the end-user – either challenge or frictionless.
  • Improvement: We have improved our Proxy feature and the way vault tokens are created from a fetch request, this broadens the choice of payment gateways when making a charge with a vault token.

June 25th 2021

  • Improvement:  We have simplified our SSO set up by reducing the characters in the login links, providing a quicker and easier experience for businesses sharing these links internally.
  • Improvement: We have made some minor adjustments to our dashboard, by displaying businesses’ Company ID in their Paydock account. To check this, you can log into your Paydock Production or Sandbox account, click on the Profile menu on the left hand side and go to ‘My Company’, and the ID is displayed in the upper right corner of the dashboard.
  • Update: We have extended the Paydock transaction object. The Retrieval Reference Number (RRN) from the MPGS response is stored in the Paydock transaction now.
  • Improvement: We have updated the status for cancelled charges processed through the Adyen gateway, this has changed from “cancel_requested” to “cancelled” enabling more transparency for our customers.

June 17th 2021

  • New Integration: We are excited to announce that we have launched a new integration from PayPal… PayPal Smart Button. With PayPal Checkout Smart Buttons, merchants are able to provide a simplified and secure checkout experience. This feature intelligently tailors the needs of your customers by automatically presenting their preferred payment types, making it easier to complete their purchases. Along with the Smart Button feature, you can now opt into using PayPal’s popular Buy Now Pay Later option, Pay in 4. Here you can find out how to initialise the widget with the new PayPal Smart Button.
  • New Integration: We are pleased to announce that Paydock supports Till Payments, underlining our continued promise to deliver additional payments solutions for merchants looking to scale! Click here to find out how to connect the new payment processor Till Payments with your Paydock account.
  • Improvement: We have improved our overall user experience with our reporting feature. Users can now see the progress of their CSV download once this has been selected from the Paydock dashboard.
  • Improvement: We have improved the way refunds are handled in the PayWay gateway. Users are able to more easily track and confirm the status of refunds with upgraded asynchronous message handling between the gateway and Paydock.

June 10th 2021

  • Improvement: We have upgraded the BPoint gateway integration by adding Customer Reference Numbers (CRN). These helpful parameters reduce administration efforts for our merchants when tracking and monitoring their customer’s charges, whilst providing them with an efficient and effortless reconciliation process.
  • Improvement: We are continually upgrading our Rules feature. We have refined the prioritisation experience for ease of use.
  • Improvement: We have made some minor adjustments to display the  gateway_specific_description parameter during a charge creation with the EMS gateway.
  • Improvement: Now pass customer and payment source details along with a one-time or a vault token in a 3DS charge for improved 3DS performance.
  • Improvement: We have made improvements related to our Paydock widget to reduce failed charges by improving the client side validation experience for card entry.

June 4th 2021

  • New Feature: We have rebranded our Smart Routing section in the Paydock dashboard! Introducing… ‘Rules’, our automated routing of charges feature which allows you to combine several parameters while creating a rule. This creates a truly hands-off’ experience for merchants as multiple payment gateways are managed via the dashboard rather than through heavy integrations or codebase changes. This feature enables you to control charge processing based on parameters such as PAN (card number), payment source, amount, currency, card type, etc. It can also eliminate the risk of fraud with our nifty ‘reject’ rules feature.
  • Improvement: We have upgraded our Zip link to provide improved support for global merchants.
  • Improvement: Merchants can now create one-time tokens independent of any connection to a gateway with our ‘Vault as Payment Source’ feature, providing greater flexibility and more opportunities within its usage. To find out more about creating and using one time tokens, click here.
  • Update: We have updated the Flo2Cash gateway connection. API key is now required instead of the legacy username and password solution to start transacting with Flo2Cash through Paydock.
  • Improvement: We have refined the Paydock widget workflow experience and improved the CVV validation in our Client SDK.
  • Improvement: We have improved the logic of creating a charge with a one-time token to ensure merchants and consumers have a seamless experience when creating charges. Updated API documentation on how to create a charge when using a one-time token can be found here.

May 28th 2021

  • New feature: We continue to extend the Proxy feature. Along with general cardholder data Paydock will proxy sensitive authentication data, such as CVV2 in PCI DSS compliant way so that it can be used for online and offline/manual processing.
  • New Integration/Link: Paydock now supports Qualpay. Click here to follow our simple guide on how to connect to Qualpay from the Paydock dashboard and start accepting payments.
  • Improvement: We have made some minor adjustments to the Paydock widget to improve workflows within a 3DS cancellation process event management.
  • Improvement: We have upgraded the GET /v1/customers?id= endpoint to display additional fields for the ‘payment_sources’ reducing the need for extra API calls in specific scenarios.
  • Improvement: We have extended the Proxy fetch flow. Now make fetch requests to the Booking.com platform without requiring card details in live mode.

May 21st 2021

  • New feature:  Introducing Paydock Proxy! This feature enables merchants, hoteliers and other third-party platforms who receive card data from third parties (but do not necessarily take payment immediately) to securely store in the Paydock Vault ensuring they are available in a PCI-DSS manner for later online or offline/manual payments. Paydock Proxy works in both ‘push’ and ‘pull’ modes where card data can be ‘pushed’ to Paydock using our transparent API or ‘pulled’ by Paydock if the third party platform supports. Paydock Proxy provides seamless payments orchestration when working with B2B omni-channel, e-commerce and industry integrations.
  • New Integration/Link: Paydock now supports the FlyPay gateway.
  • New feature: We have introduced some handy new filters enabling merchants to track their customers with a search by full email address on the Master Merchant dashboard. Also works with partial matches. To find out more about our filter parameters, click here.
  • Improvement: 3DS request parameters have been extended for even better fraud detection and improved reporting output. These additional request and response parameters can also be selected and used for building Custom Reports and are now available on our dashboard under the Charge menu.

May 14th 2021

  • New feature: We have upgraded the EMS setup to support a 3DS flow with a one-time token. Click here to learn how to do it via the API.
  • New feature: Now it is possible to use a tag in the Client SDK to scan card details on mobile iOS devices in both Sandbox and Production mode. The feature is available in the widget version 1.10.15 and later.
    Click here to find out how to add a tag to the Paydock widget and how to use our new credit card scanner.
  • New feature: We have added the ability to set a transaction reference using a vault token and passing it to the Secure Pay gateway.
  • New feature: We have made new changes related to the 3DS authentication. We have added transaction and service logs inside an authentication request.
  • Improvement: The ‘card_scheme’ parameter is now added to the ‘payment_sources’ object when creating a customer without a gateway ID.
  • Improvement: We have changed the filter logic to now select a specific date range on the Charges page. This eases and speeds up the overall process with filters.

May 7th 2021

  • New feature: Now you can use a tag in the Client SDK to scan card details on mobile iOS devices. It enables you to easily fetch card number and cardholder name. For now, the feature is available only for the Sandbox environment but we plan to release it on Production as well.
    Click here to check how to add a tag to the widget and scan your credit card with its help.
  • New feature: We have added new ‘payer_id’ and ‘payer_fee’ fields for you to be able to pass and keep more detailed information about your customers. The fields are available when creating charges with the PayPal gateway.
  • New feature: Now it is possible to use Smart Routing along with EMS 3DS. The feature allows you to route payments to different EMS gateway IDs (3DS and non-3DS) based on a chosen currency.
  • Improvement: We have made some minor adjustments to retrieve archived customers by calling the GET v1/customers?archived=true request.
  • Improvement: We have improved the logic for resetting the password in Sandbox and Production environments to make sure you have a seamless experience when using our product.

April 30th 2021

  • New feature: Upgraded EMS link to include direct 3DS using the EMS gateway. Click here to learn how to do it via the API.
  • Improvement: We have made some minor adjustments to the mapping of 3DS fields in the MasterCard gateway response.
  • Improvement: We have improved the overall logic of creating direct 3DS charges for gateways that support this feature.

April 23rd 2021

  • New feature: Paydock now supports the Adyen gateway. Here you can review how to connect to Adyen from the Paydock dashboard and start accepting payments through it.
  • Improvement: We have added the ability to set a transaction reference and pass it to the gateway for Secure Pay.
  • Improvement: We have made some minor updates for a customer payment source with a one-time token.
  • Improvement: Now you can also send the shipping method for a transaction during the 3DS flow.
  • Improvement: We have increased the allowed number of characters for metadata for an SSO setup. Now it can be possible to add a metadata consisting of 30 000 symbols.

April 15th 2021

  • New feature: Now it is possible to choose fields that will be included in the CSV reports from the Charge page, both Charges and Txns view mode. You can also drag fields in templates to change their order on the Charges/Txns page and the CSV report. The option to do that appears on the left when hovering over the field name.
    More information can be found here.
  • Improvement: We have improved the schedule.authorised_pended_at feature to provide better checking for the status check when checking against an archived gateway.
  • Improvement: We have made some minor adjustments on the Dashboard page related to company users that don’t have permissions to see all charts. Now they are redirected to the page that every role has access to by default – Charges.

April 8th 2021

  • New FeatureWe have expanded the functionality that allows creating custom fields, storing them at Paydock and even passing them to gateways. Now it is possible to create and apply multiple custom templates for the Charges page with various sets of custom fields. Merchants can also set the view mode: for Charges or Transactions, with the list of fields they have chosen for a particular template.
    Click here to check more details.
  • New Feature: We have added an ability to set custom fields from the ‘Add new charge’ page. Also, merchants can choose the custom fields they passed previously from the dropdown when making a charge.
    Click here to find out more.
  • New Feature: We have enabled merchants to cancel a charge before its settlement date. It applies to charges in Completed, Pending, Failed and Requested statuses.
  • Improvement: We have updated the length of a redirect link generated with the ZipmoneyCheckoutButton widget. Please make sure that you use the latest NPM version with the implemented changes.
  • New Feature: We have added a settlement/remittance date for charges made with the BPoint gateway. Now it is displayed in the charge response as a remittance date.
  • Improvement: We have optimised a search query for Charges and Customers to reduce the time for loading the Paydock dashboard and improve your experience as a user.

April 1st 2021

  • New Feature: The filter for GET /charges and GET /charges/charge_id endpoints has been expanded with new values.
    More information can be found here.
  • Improvement: We have made some minor changes so that all the subscription details that you need are included in the CSV reports that you download from the Charges section in the dashboard. This should make your reconciliation process as smooth as possible.
    The article on how to download the CSV report can be found here.
  • Improvement: We have polished our Charges chart. Now it properly handles the cases with switches from and to daylight saving time.
    Click here to check more information about chart management.
  • Improvement: We have improved the logic for filtering the allowed response properties to update the custom fields endpoint.
  • Improvement: When making a charge with a vault token from a customer, the details of this customer are used instead of those with whom the vault token was created initially.

March 26th 2021

  • New Feature: Now you can send new fields on the /charges/3ds endpoint. We have also added the ability to set new fields in the Paydock widget for your convenience.
  • New Feature: Now it is possible to create a customer with a payment source without any gateway.  The functionality applies to making a charge and creating a subscription from the customer. Currently, it is available via the API only.
    More information can be found here.
  • New FeatureThe Single-Sign-On feature via SAML was implemented. It enables the secure exchange of user authentication data between web applications and identity service providers. With this feature, users can log into the Paydock dashboard after authenticating with the identity provider using only one set of credentials. It simplifies and speeds up the whole login process, say nothing of enhanced security.
  • Improvement: We have updated the error handling for charges made with 3DS and Fraud with no Fraud service connected.
  • Improvement: To improve performance, we have reviewed and improved an approach of calculating the charge refund.
  • Improvement: We have made some minor adjustments on the Dashboard page related to URL redirects. If the user of the Master Merchant account does not have permission to view some page, they will be redirected to the default page accessible to any user.

March 19th 2021

  • New FeatureThe Paydock API now supports custom fields for charge transactions. You can pass custom fields in the transaction object when creating, capturing, canceling and refunding charges. Custom fields can be stored on the Paydock side and sent to EMS (by default) and Stripe (this option should be enabled upon gateway creation or update).
  • New FeatureNow it is possible to make charges in dinars (KWD, BHD, IQD, JOD, etc.) with 3 decimal numbers against the EMS gateway via Paydock. This feature is available for direct charges only.
    The guide on how to create a charge can be found here.
  • Improvement: The HTTP status code is now stored in logs for the Bambora gateway. It adds an extra value to those clients who rely not only on the error code and error description but also on the HTTP code.
  • Improvement: We have updated the live URL for sending requests to the Fiserv and EMS gateways.

March 11th 2021

  • ImprovementThe aggregation for the charge chart statistics has been optimised to reduce the chart loading time.
    Click here to check more information about chart management.
  • New FeatureWe have introduced error messages pop-ups with adaptive height which makes it more convenient to work with a long text.
  • Improvement: We try to improve your experience of using our Client SDK with its every new version. We have released a more stable widget version 1.10.9 which contains an advanced .useAutoResize method. To enjoy all the enhancements, please make sure that you use the latest version.

 February 25th 2021

  • New Feature: Two settings are available for the Fiserv gateway now: with and without multicurrency. If you have a non-multicurrency account at the gateway, when activating it at Paydock, you can mention the default currency in which you would like to receive money for the payments. We have added a possibility to check exchange rates at Fiserv for the non-multicurrency setup even before creating a new charge or subscription. This enables you to check in advance what will be the amount of the transaction in your default currency.
    More information about dynamic pricing can be found here.
  • New Feature: To improve your experience of using ApplePay and GooglePay, we have added the expiration time for the wallet token for you to keep it utilizable for 24 hours.
  • Improvement: The Visa logo was updated in the widget with a possibility to choose between blue and white logos depending on the background color of your widget.
  • Improvement: We have updated the status of the pre-auth charge with Stripe. If you do not capture it within 7 days, Stripe cancels the charge, though the status at Paydock remains ‘pending’. If you attempt to capture it after this time range, the status will change to ‘failed’ instead of ‘expired’ which better reveals the actual process behind this.
  • Improvement: The 500 error code, shown after you create a wallet payment without mentioning a payment source, has been replaced with the 400 one with additional error details.

February 22nd 2021

  • New Feature: We have created a great tool for viewing charges and subscriptions statistics right from the dashboard. Now you have a visual representation of all your payments chunked by time, status, amount, etc.
    Click here to check more information about chart management.
  • New Feature: We have introduced a schedule for calculating a total refunded amount. No manual calculations are needed now, you can find the necessary value in the new field ‘statistics.total_refunded_amout’ in the charge object.

February 12th 2021

  • New Service Connection: Paydock now supports the Advam gateway. You can explore more payment opportunities with another gateway available at Paydock. Here you can review how to connect to Advam from the Paydock dashboard and start accepting payments through it.
  • Improvement: The customer object was extended with the gateway name and type fields. Now these fields are also available for a charge from a customer and standalone refund.

February 2nd 2021

  • New Service Connection: Paydock now supports the EMS gateway. With every new integration, we aim to offer more opportunities for your payments freedom.
    Feel free to check here how you can connect to the gateway through the Paydock dashboard.
  • New Service Connection: We have added a possibility to pay with ApplePay and GooglePay via the Stripe gateway. Now you are free to accept payments via wallets with the help of our Client SDK.
    Implementation documents are available at NPM.
  • Improvement: We have made some minor adjustments to the Stripe gateway integration process. You will need your Stripe public key as well which, in its turn, enables you to enjoy our new features, such as ApplePay and GooglePay via Stripe, Stripe sub-accounts and many more.

January 21st 2021

January 14th 2021

  • New Feature: “Login as Sub Merchant”: Another great feature has been added to the Master Merchant platform. To have a closer look at Sub Merchants’ settings and charges, the Master Merchant can log into and out of their accounts with just one click.
  • New Feature: “Easy to identify Stripe Subaccounts via Labels”: The Stripe subaccounts functionality has been extended with a new ‘Label’ field that makes it easier to identify a particular subaccount among others. Currently, it is available via API only.
    Click here to check more details.
  • New Feature: “Style iFrame Background Colour”: We have made minor styling changes to our widget. Now it is possible to apply the background color to the whole iFrame.
  • New Feature: “Virtual Connection to PSPs”: Now you can connect to some payment gateways not only in a sandbox or production mode but also in a virtual one.

January 5th 2021

  • Improvement: We continue improving the Master Merchant facility and its branding functionality. In this release, we have added more elements which can be styled from the Master Merchant dashboard, e.g. the color of the loading bar, API keys, support email, etc.
    Click here to find out more.
  • Improvement: We have added the ability to pass a Paydock charge description as an order description at Authorize.net. It will make payments reconciliation much easier for our Auth.net customers.
  • New Feature: The Shared Vault Group functionality is available in the dashboard now. It enables Master Merchants to share vault tokens across multiple Sub Merchants with just a few clicks.

December 24th 2020

  • New Feature: We continue expanding the charge object. Now all payments made with Stripe and Fiserv contain the stub remittance date.
  • New Feature: We have added the ability to create Stripe accounts to route payments between multiple recipients who need to get paid. Currently, the functionality is available through the API only but we are in the process of adding it to the dashboard.
  • New Feature: The Master Merchant platform was extended with another feature – Shared Vault Group. Now your Sub Merchants can access and use shared resources, namely, vault tokens. It enables them to re-use customer’s billing details for future payments instead of collecting them again. It is available via the API for now.
    Click here to check more details.

December 18th 2020

  • New Feature: Now it is possible to configure specific retry settings for every subscription. Each and every subscription can have its own retry interval, frequency, count and fail status.
    The guide on how to create a subscription can be found here.
  • New Feature: When creating charges with the Stripe gateway, you can specify a descriptor suffix to pass additional details on the transaction.
  • Improvement: Paydock has improved the 3DS initiation flow with the MasterCard gateway that allows preventing charges stuck ‘in progress’.

December 9th 2020

  • New Feature: The additional search fields “Amount” and “Card number last 4 digits” are available on the “Charges” page in the dashboard.
  • Improvement: Now the charge object for all gateways includes the “gateway_name” and “gateway_type” fields. You can view them via the API only.
  • Improvement: Paydock stability has been increased thanks to the ongoing integrity monitoring checks.

December 3rd 2020

  • New Feature: The Master Merchant facility has been improved. Now it is possible to set styles and images specific to your brand. You can change buttons and links colors, modify slogans on sign-in and sign-up pages, add URL references to your website, etc.
    Click here to find out more.
  • New Feature: The API functionality of the charge object has been expanded. Now charges made with the Stripe gateway can contain the “meta.stripe_descriptor” option mapped to a descriptor suffix field at Stripe.
  • Improvement: We have blocked the possibility to attempt a refund of the ‘refund only’ transaction in the dashboard.
    Click here to check more information about the refund feature.
  • Bug Fix: Email notifications for the “subscription_creation_failure” event were not displayed on the History page in the dashboard.

November 25th 2020

  • Improvement: The ‘reference’ field was included in the 3DS pre-authorize request with the MasterCard gateway.
  • Improvement: Now it is possible to create pre-auth charges with the Fiserv gateway from the Paydock dashboard.
  • Bug Fix: The user faced ‘Access forbidden’ error messages in the dashboard when opening pages that contained endpoints where the user did not have access.
  • Bug Fix: The Bambora gateway errors did not map properly for direct debit charges after consequent API requests on charge status checks.

November 20th 2020

  • New Service Connection: Paydock now supports a new gateway – Fiserv PSP for Merchants. Wondering how you can start using it?
    Visit our helpdesk article for more details.
  • Feature release: The customizable branding for the Master Merchant facility is live. Now a master merchant can upload a logo/favicon/background from the dashboard (from the new “My Brand” page).
    Click here to find out more.
  • Improvement: Updated the format of the expiry date passed to Bambora. Previously, the charge for the customer created with a one-digit month failed with the ‘invalid expiry date’ error message.

November 13th 2020

  • Bug Fix: A user couldn’t set time when trying to reactivate a subscription.
    More information about reactivation can be found here.
  • Improvement: Not all gateway errors were processed correctly for Windcave. Error mapping was reviewed and updated.
  • Improvement: Not all gateway errors were processed correctly for Bambora. Error mapping was reviewed and updated.

November 6th 2020

  • Feature release: Now a user can whitelist IP addresses from the dashboard (there is a new “Security” tab in the “My Company” page).
    Click here to check more details.
  • Bug Fix: If the error message was too long, a part of it was invisible in the pop-up window.
  • Bug Fix: CSV exports did not contain all the filtered items from the dashboard because of the missing timezone.
  • Bug Fix: The “Return to sign in page” link was broken on the 2FA confirmation page.
  • Improvement: Security improvements added.

April 17th 2020

  • New Service Connection: MasterCard Gateway Service is now available at Paydock. We have integrated this new gateway to offer more opportunities to you and contribute to your seamless experience.
    You can check this Helpdesk article on how to set it up in your Paydock account.
  • Bug Fix: Fixed the issue with Client SDK when using it as a module.
  • Bug Fix: Solved the issue with a Merchant Warrior bank account created as a card.

March 26th 2020

  • Feature release: Released the new policy to keep the user’s password secure as a part of the PCI DSS Compliance. Now you get a warning if your password is too weak and does not comply with security requirements.
  • Improvement: Added a filter parameter to search by cards or bank account only in the vault.
  • Bug Fix: ‘Amount’ and ‘Currency’ columns are combined and shown as one column in the dashboard tabs.
  • Bug Fix: Left-hand side navigation menu below your name is not collapsed when navigating sub-pages.
  • Bug Fix: Resolved the issue with capturing an authorized charge.

March 20th 2020

  • Improvement: Extended charge information from API now included in dashboard bulk-download capability.
  • Improvement: Small clean up of dashboard currency display to save space.
  • Improvement: Tightened up permissions and security around Owner vs Admin role behaviour.
  • Bug Fix: Small UI clean up on the password reset page.

March 5th 2020

  • Feature release: Dashboard tracker on Subscriptions to help identify if status changes were triggered by the Paydock engine or applied manually. Column is titled ‘Last Status Change’.
  • Improvement: Dashboard user can now move Subscriptions to the ‘Complete’ status manually on the Paydock dashboard.
  • Improvement: Updated UI for archived Customers.
  • Improvement: Minor UI improvements across Dashboard.

Feb 22nd 2020

  • Feature release: Now download complete sets of filtered records when on Vault, Customer, Subscription, Transfer and Charges pages. Click the “All Filtered Items” button to export the complete set of requested data.
    View Helpdesk Article 
  • Improvement: Updated Vault search via Dashboard to include bank accounts.
  • Improvement: Customer objects can now have a Company attribute.
  • Improvement: Updated Vault search via Dashboard to include bank accounts.
  • Improvement: Updated integration with Fat Zebra gateway to enable omit_expiry parameter.

Feb 7th 2020

  • Feature release: New parameters available when running reporting queries on the PayDock API. Now filter Charges based on last updated date both ‘from’ and ‘to’.
    View API docs here.
  • Feature release: Richer queries available from Charges API. Dynamically include related Subscription current and historical/snapshot information within the Charges request by using the new “expand” parameter.
    View API docs here.

Feb 3rd 2020

  • Feature release: Enhanced transaction/charge report downloads. Now download complete, filtered and/or unlimited row transaction searches directly from the dashboard.
  • Fixed. Small bug in resetting start dates for Subscriptions in Dashboard
  • Upgraded logging microservice to enable us to provide richer support to our merchants

Jan 10th 2020

  • New Service Connection: Proud to announce the inclusion of Bpoint to the Paydock family further adding to the value we bring Merchants and Vendors.  Now accessible via Paydock Dashboard and API and works alongside all our core features including Smart Routing, Recurring Payments, Notifications, Vault and more. To find out more:
    Helpdesk Article
    Services List
  • Performance improvements and bug fixes

Dec 27th 2019

  • Feature Release: Extension to Customer object to include Description field (not just Reference)
    Accessible via both API and Dashboard
  • Inclusion of Vault Token ID when reviewing Customer Payment Sources (if applicable)

Dec 21st 2019

  • Feature Release: Bank accounts now included directly in Vault
    Previously, bank account details were attached to Customer Payment Sources, however you can now directly add, store and manage bank account details in the Paydock Vault via API and Dashboard interfaces.
  • System improvements and performance optimisations

Dec 5th 2019

  • Feature Release: Paydock X-Ray/Audit Tool. 
    Introducing end-to-end system activity traceability throughout the Paydock orchestration platform. This includes any third parties who have been granted access and internal admin users. Please view the Helpdesk article here
  • Minor bug fixes

Nov 28th 2019

  • Feature Release. Ability to filter Notification history by Subscription, Charge, Transaction objects
    This improves the ease of searching historical Notifications for re-issuing when required.
  • Minor bug fixes and tidy-ups

Nov 11th 2019

  • Improvements to the CSV download capabilities in the Paydock merchant dashboard.
  • Improvements to the error information available in the Charge object when triggering a POST request via the API
  • Improvements to the Paydock merchant license billing details update

Sept 27th 2019

  • Feature Release: Ability for Merchants to configure retry parameters at a subscription level
    This enables fine-grain controls of how Paydock Subscriptions handle failed-payment activity including the ability to configure interval, frequency, limit and failed status.
  • Feature Release: Place Subscriptions in ‘held’ status

Sept 11th 2019

  • Improvements to the credit card expiry date workflow.
  • Improvements to Subscriptions when the payment source is changed including the ‘default’ setting.

June 11th 2019

  • Feature Release: Smart Routing Engine
    This enables merchants to build cascading rules to direct payments to specific services depending on rulesets.
  • Improvements to 2FA experience
  • Tweaks to the dashboard to improve user experience (and reduce brain-power required)
  • Improvements to phone number handling in the Paydock SDK

Release 71

Production Release Date: 02/10/2023

Sandbox Release Date: 18/09/2023

API changes:

  • This change primarily focuses on altering the error response for invalid charge requests. As a result, the ‘resource.type’ field will now consistently contain a string value. Please take the enhancement into account during error mapping to avoid unexpected errors.

    Impacted Functionality:

    This modification affects several charge creation endpoint flows ( {{url}}/v1/charges ):

    • creating a pre-auth charge

    • creating a charge with an existing customer

    • creating a charge with an attached standalone fraud

    • creating a charge with an attached standalone 3DS

    • creating a charge with custom fields

  • We have improved the Fee Profiles feature with a new validation within the API to allow positive amounts only when creating a Fee Profile rule.
  • Extended our Database with some more UnionPay BIN ranges to make sure the system properly handles and returns the ‘card_scheme’ field.
  • We have made the ‘card_name’ field optional for MPGS gateway charges. This change allows merchants to make the ‘card_name’ field optional for MPGS Gateway charges, aligning our system with MPGS documentation.

    Impacted Functionality:

    This modification affects several charge creation endpoint flows ( {{url}}/v1/charges ):

    • Direct charge with a card or vault token using MPGS as a gateway

    • Pre-Auth charge with a card or vault token using MPGS as a gateway

  • We fixed an issue where error responses in Vii’s balance check scenario didn’t populate the ‘status_code’, ‘status_code_description’, and ‘gateway_specific_description’ fields as anticipated. Please note that the response message from Vii’s service is mapped and stored in the ‘gateway_specific_description’ field, and the ‘status_code’ and ‘status_code_description’ fields will be null as expected. Populating gateway validation response, as per structure:


    message: string,

    code: string,

    details: {

    path?: string,

    gateway_specific_code: string,

    gateway_specific_description: string

    messages: string[]

    } }

    Impacted Functionality:

    POST {{url}}/v1/charges/balance

  •  Accertify Notifications – From now on, only the information about the latest transaction state and a charge ID are added to the Accertify notification when the request parameter ‘transaction_only’ is set to ‘True’.
  • The ‘schedule.payment_date’ field is now used for checking the status of BSB charges made with Flo2Cash, as the gateway does not provide any other identifier.
  • Mapped the Worldpay error code 103 to ensure that the right error message, “fraud_warning”, is shown to clients as against showing “unknown error” when the Worldpay gateway returns error code 103. Also, we mapped the Worldpay general error code category to ensure the appropriate error message is shown for the error codes returned by Worldpay.

Widget changes:

  • We’ve fixed an issue where the Vault Display Widget didn’t display the “Show card number” button as expected. The issue occurred when following specific steps involving the Vault Display Access Token. Now, the widget functions correctly.

    Impacted Functionality: The issue resided in the process of verifying whitelist IPs for all widgets utilizing the access token instead of the public key for widget initialization. In theory, this could impact clients employing the access token with the following widgets:

    • Simple Widget

    • Payment Source Widget

    • Visa-SRC

  • We enhanced the GooglePay workflow to ensure that the GooglePay button is displayed appropriately on Safari, Google Chrome, and other browsers.

Release 70

Production Release Date: 06/09/2023

Sandbox Release Date:27/08/2023

API changes:

  • Implemented a new enhancement to handle the gateway error (400 Invalid Request Details) more effectively for PayPal transactions, specifically when updating `transaction_shipping_address` or `reference`.
  • Enhanced the MPGS 3DS In-build flow by mapping the MPGS `transaction.reference` field to the Paydock  `reference2` field.
  • Unmasked the `account_number` in the charge log when creating a charge through the following endpoints:

  `POST /charges`

  `POST /charges/direct`

  `POST /charges/authorized`

  • Implemented an enhancement to handle pre-authorization charges for WorldPayWPG.
  • Removed the `customer.payment_source.card_number_hash_uuid` field from the Accertify notification payload. This change applies when the request parameter `transaction_only` is set to `False`.
  • Refined the error mapping for Stripe, enhancing the clarity of `generic_error` and other error messages.
  • Updated error mapping for Pin Payments to improve accuracy and reporting.

Release 69

Production Release Date: 16/08/2023

Sandbox Release Date: 03/08/2023

API changes:

  • Added the “order_id” or “transaction_id” fields for the MPGS charges created within the subscription. If the values are not passed by the customer, Paydock to auto-generate the value(s) and pass them to the gateway.

  • Improved error mapping for Worldpay where the error codes and error descriptions were unknown.
  • Remapped the gateway connection error from ‘Unauthorized’ to “Invalid Gateway Credentials” for MPGS.

  • Now it is possible to assign the existing charge to a subscription using the:

    HTTP method: POST
    endpoint: /v1/charges/
    example payload: {"subscription_id": ""}

  • Improved the error messages for MPGS capture transactions.

Release 68

Production Release Date: 26/07/2023

Sandbox Release Date: 11/07/2023

API changes:

  • Fixed error description for Flypay in case of failed auth charges.

  • Improved FatZebra refund handling.
  • Mapped new fields for MPGS + ApplePay flow:
    • referenceorder.reference

    • reference2 – transaction.reference

Release 67

Production Release Date: 22/06/2023

Sandbox Release Date: 06/07/2023

API changes:

  • Improved error mapping for Afterpay gateway in case of timeouts to properly handle the service responses.

  • Fixed the EFTPOS connection workflow. Previously, to connect the gateway, the Merchant Name was supposed to be in the format MyMerchantName | Trans Desc | Trans 299. Now the format is MyMerchantName for this field.

Release 66

Production Release Date: 14/06/2023

Sandbox Release Date: 01/06/2023

API changes:

  • Updated response error when DCI servers are unavailable. In the case when the DCI servers do not respond, we had the following response format:

    HTTP STATUS: 500

    "error_code": "InternalError",
    "error": "Didn't receive the response from DPOP!"

    Now, it will start returning a 200 HTTP status with an exception described in the response body.

    The response structure will be as follows:

    { "process_error_code": "tcp_error", "process_error_code_message": "Message with description"

  • Implemented a new gift_card_number field for both Check Balance and Direct Charge requests for Vii service. This field is mapped with the Vii ‘CardNumber’ field from the request and contains the full gift card value.

  • Added a new bulk_reference field for the new Split Payments functionality. The field will be also reflected in our Notifications feature.

  • Adjusted GPayments mapping with the correct values and fields.

  • Now, If the Paypal capture operation fails with the ‘CAPTURE_AMOUNT_LIMIT_EXCEEDED‘ error, the charge status will be ‘Failed’ instead of “Complete” as it was previously.

  • Previously, when our system tried to get a transaction status for a direct debit charge and gets a 400 error – the transaction is treated as successful, and the status is updated to “completed“. This has been fixed, now the status will be failed for this scenario.

  • Updated our API docs. Added a new Fraud endpoint for Split Payments functionality and added Fraud transaction type to the Transaction Types table.

  • Updated the Timestamp format while sending payment results to Accertify. Timestamp for Sending transaction results to Accertify will be in the following format: yyyy-MM-dd’T’HH:mm:ssZ. The example: external_creation_date: “2023-05-21T23:59:56-0000”.

Widget changes:

  • Fixed value of the status_code field for successful sale transactions completed using the Afterpay v.2.0, ApplePay, GooglePay, and PayPal wallets. Previously, after completing a successful sale transaction, the status_code field would have a “pending” value in the logs. Now this has been fixed and the status_code will have a “null” value in case of successful transaction.

  • Check out our latest Client SDK version!

Release 65

Production Release Date: 24/05/2023

Sandbox Release Date: 10/05/2023

API changes:

  • Included reference and source_id fields for a scenario when creating a charge with a customer who does not have a default gateway.

  • Fixed refund error handling for FatZebra and Afterpay V1 where previously charge status would get stuck at the “refund_requested” phase.

  • We added a new card_acceptor.name optional field for EFTPOS payments. The EFTPOS service does not accept more than 40 characters for the card_acceptor.name field.

  • Improved capturing customer.payment_source.type in the logs when the charge is made with OTT or Vault Token.

  • Fixed the logic for switching between virtual and test modes for gateways that support these modes. Previously when performing API requests against the Virtual mode, gateways would switch to Test mode. This now should only happen when explicitly changing the mode.

  • Updated our API documentation with new meta.region value that allows setting region for Direct Debit business days logic.

  • Improved error message when canceling verification charge. Now, 400 status code and Invalid Operation for Verification Charge error message will be received.

  • Improved handling of the custom order_id and transactin_id for MPGS charges:

    • Now if a custom transaction_id value is provided in the void/cancellation request, it will be included in the URL parameter to MPGS.

    • Now the transaction_id character limit is 40. If exceeded, 400 status code and transaction_id/order_id must be shorter than or equal to 40 characters error message will be received.

Widget changes:

  • We have improved our Canvas 3DS widget to handle properly InitAuthTimedOut response.

Release 64

Production Release Date: 21/04/2023

Sandbox Release Date: 13/04/2023

API changes:

  • We have improved the error mapping for the GPayments and Bambora. We have also improved the way we handle MPGS and Worldpay responses to make sure the provided information is full and corresponds to the description.

  • We have unmasked the Cardholder name for the Standalone 3DS logs.

Widget changes:

  • We have improved validation for the Cardholder Name field to make sure that only relevant information can be passed using this field.

  • Canvas 3DS widget documentation has been updated.

Release 63

Production Release Date: 03/04/2023

Sandbox Release Date: 16/03/2023

API changes:

  • We have mapped the “cardholderAuthenticationResult” EFTPOS field with “transactions.cardholder_authentication_verification_value” Paydock field to make sure our clients receive full and proper information. Field params are described below:Field type: StringMin/Max symbols: 1Possible values:
    • 0 – CAV not validated due to data error
    • 1 – CAV failed validation
    • 2 – CAV passed validation
    • 3 – CAV validation could not be performed (Authentication attempted, but not completed)
    • 4 – CAV validation could not be performed (System error or authentication failure)
    • 5 – CAV not validated (Issuer is not a CAV service participant)
    • 6 – CAV not validated (Issuer is not set to participate in any CAV service)
  • We have increased the time for processing Direct Debit charges when the “503/504” status code is received to make sure those charges are handled properly and display the correct status.
  • We have added the following additional fields to the logs to provide our clients with full and correct information on the processed charges:
    • service_id
    • service_name
    • service_type

    Those fields will store the id and name of the Fraud or 3DS service that is being used, and the service type (Fraud or 3DS). To test this new enhancement, it is required to create a standalone charge with a vault token and Fraud/3DS service and check the response.

Release 62

Production Release Date: 03/04/2023

Sandbox Release Date: 16/03/2023

API changes:

  • We have improved the error mapping for the PayPal gateway. Now the “INSTRUMENT_DECLINED” gateway-specific code corresponds to the accurate error description:  “The instrument presented was either declined by the processor or bank, or it can’t be used for this payment” in the Response logs.
  • The “gateway_specific_description“, “error_message“, and “error_code” are displayed now after capturing the already voided and authorised Afterpay charge. To reproduce, the following steps should be taken:
    • Create Afterpay charge;
    • Void full amount;
    • Try to Capture;
    • Check the Response:

      “type”: “capture”,
      “status”: “failed”

Widget changes:

  • Updated MastercCard logo, and implemented alerting and monitoring enhacements. Please make sure you Widget version is up-to-date!

Release 61

Production Release Date: 31/01/2023

Sandbox Release Date: 30/01/2023

Core changes:

  • Improved the scheduler for authorised charges so that it doesn’t check the transaction status after the transaction was voided.

API changes:

  • A new fraud operation mode called flex has been added to the fraud flows. It needs to be be accepted as fraud.mode charge overriding the service one:

POST v1/charges (or v1/charges/wallet)



    fraud: {

        mode: ‘flex’,




  • Map response fields from  MPGS 3DS transaction:
    1. gateway_specific_code = order.status
    2. gateway_specific_description = order.authenticationStatus
    3. error_message = transaction_declined
    4. error_code = gateway_specific_description
  • Merchant Warrior error mapping improvement.

Widget changes:

  • Validation for GooglePay wallet transactions has been updated. If there are an empty string for address_state field, the transaction will no longer result in a failure and will be processed based on the available information.
  • Set up a delay for the AfterpayCheckoutButton to make sure the data is saved for further processing on the backend storage.
  • Validation improvement for the cardholder field to make sure that correct information is passed in this field. This is being done to prevent issues such as card numbers being passed into the cardholder name field, or other unintended data being passed here.

Release 61 (Hotfix)

Production Release Date: 24/01/2023

Sandbox Release Date: 23/12/2022

Core changes:

  • Validation enhancement for all the gateways to reduce processing time for subscription charges.

API changes:

  • Fixed Get transaction status request for Merchant Warrior to receive appropriate information.

Release 60

Production Release Date: 12/01/2023

Sandbox Release Date: 21/12/2022

Core changes:

  • Add Merchant ID and Merchant Website URL to the Request Headers for Afterpay v.2 service.
  • Calculating transaction.remittance_date for EFTPOS virtual mode txns in a similar manner as on EFTPOS real environments to enable more efficient testing.
  • Added the ability to overwrite the payment_source_information that had already been captured in the vault token but at the time of charge creation, some updated information has been processed either via customer payment source (If present) or input field payment source (If present).
  • Added validation for total_refunded_amount field for all the payment services to make sure the refunds are processed properly.

API changes:

  • Extend only_matched_transactions filter (“Filter transactions“ on UI) for transactions.remittance_date.

Release v1.84.1

Production Release Date: 12/01/2023

Sandbox Release Date: 08/12/2022

Core changes:

  • Upgrade Angular version to latest stable v14.

API changes:

  • Updated the EFTPOS CNP API paths from V2 to V3 (latest version).
  • Added API requests for Webhook notifications templates.
  • Extended webhook templates with Standalone Fraud check events: standalone_fraud_check_in_reviewstandalone_fraud_check_successstandalone_fraud_check_failedstandalone_fraud_check_in_review_approvedstandalone_fraud_check_in_review_declined.

Widget changes:

  • Added a new validation for meta.hide_shipping_address field for PayPay Checkout. If the field has the value=false, the payments will be processed as usual. 
  • Resolved an issue with shipping.amount validation for payment wallets.

Release v1.83.1

Production Release Date: 08/12/2022

Sandbox Release Date: 24/11/2022

Core changes:

  • Extended the flow for supporting Fraud check with Zippay and Afterpay v.2
  • Added an option to utilise standalone 3DS with the Cybersource payment gateway
  • Update Access level for SFTP service.

Release v1.82.1

Production Release Date: 10/11/2022

Sandbox Release Date: 10/11/2022

Core changes:

  • Paydock Dashboard performance upgrade.
  • Store customer.payment_source.card_number_bin  for all successful and failed requests irrespective of the gateway.

API changes:

  • Appending the API channel code to the acquiringInstitutionID while configuring the EFTPOS gateway which will allow a gateway to be sponsored by multiple acquirers.

Release v1.80.1

Production Release Date: 28/10/2022

Sandbox Release Date: 27/10/2022

Core changes:

  • Add Error code and description for GPayments transactions.
  • For the Gpayments client SDK, the secondary_url has been set to null. 

API changes:

  • Cardholder name will be sent as a part of every transaction captured in MPGS to ensure that this information is present in the transaction details.

Widget changes:

  • Zippay redirect integration for Zippay widget.

Release v1.79.1

Production Release Date: 17/10/2022

Sandbox Release Date: 13/10/2022

Core changes:

  • Extend the charges filter by transactions.type to support multiple values. 

API changes:

  • Standalone 3DS API documentation update.


Click here to add your own text

Let us keep
you updated
on the latest