Release Notes

• PRODUCTION RELEASE DATE: 13/01/2025
• SANDBOX RELEASE DATE: 10/12/2024

Go to Changelog Release 91

New Features:

• Introduced Paypal Vaulting Payment Processing

Implemented support for merchants to utilise the OTT (One-Time Token) returned by the PayPalSavePaymentSource widget for payment processing.

Key flows covered:

1. Customer Creation and Modification: Merchants can now create or modify customers using the PayPalSavePaymentSource OTT.
2. Charge Processing with customer created/modified with the PayPalSavePaymentSource OTT and supported:
   a. Direct Charge
   b. Authorized Charge
   c. Capture (Full & Partial)
   d. Refund (Full & Partial)
   e. Cancel
3. Introduced support for merchants to send the “correlation_id” returned by the Paypal DeviceDataCollector in charge requests.
4. Subscription Processing: Direct use of the PayPalSavePaymentSource OTT and customer for a subscription charge.
5. Enhanced reporting and extended notifications with the payment source type: gateway token
6. Blocked using the PayPalSavePaymentSource OTT for MPGS Inbuilt 3DS and direct charge processing (without exchange into a customer).

Impacted Functionality: Customer, Charge, Subscription, Reporting, Notification, Paypal gateway

• Enhanced the Reporting Performance

Implemented an optimised solution to improve the performance and reliability of the “Download Report” feature on the Charges Page, which previously faced challenges with slow and unreliable report generation for merchants with a large number of transactions. Additionally, we enhanced the pagination UI on the Charges Page to further improve its overall performance.

Impacted Functionality: Reporting, Charges

• Enhanced Standalone 3DS with Network Tokens

Introduced Gateway ID as a parameter in standalone 3DS requests. Previously, merchants needed to use NT instead of card data during 3DS checks. To simplify the merchant experience, we now automatically determine if 3DS can be performed with NT based on the provided gateway. This enhancement improves payment security and eliminates the need for merchants to conduct these checks manually.

Impacted Functionality: Standalone 3DS, Charges

• PRODUCTION RELEASE DATE: 04/12/2024
• SANDBOX RELEASE DATE: 20/11/2024

Go to Changelog Release 90

New Features:

• Introduced Paypal Vaulting

Implemented the PayPal Vaulting feature to enable merchants to use stored PayPal account credentials for initiating payments on behalf of their customers.

Key Functionality:

1. Development of the PayPalSavePaymentSource widget.
2. Handling callback for PayPalSavePaymentSource widget.
3. Enabling the widget to return a PayPalSavePaymentSource OTT (One-Time Token).
4. Blocking the exchange of the PayPalSavePaymentSource OTT into a Vault Token.
5. Implementation of the PaypalDataCollector to capture device information for enhanced fraud detection.

Please note, this is the initial release, with additional features planned for R91.

Impacted Functionality: Paypal

• PRODUCTION RELEASE DATE: 30/10/2024
• SANDBOX RELEASE DATE: 13/11/2024

Go to Changelog Release 89

New Features:

• Implemented Network Tokens: Failover

Implemented an automatic failover mechanism for network tokenisation errors. If a network token cannot be created during the initial vault creation process, our system will automatically attempt to create it in the background. This enhancement ensures uninterrupted transactions and seamless payment experiences for both merchants and customers, even in cases of initial network token creation failures.

Impacted Functionality: Vaults

• Implemented Network Tokens on Fly generation (Subscriptions & Verify)

Enabled the creation of Network Tokens for existing Vaults during Verify and subscription charges processing ensuring seamless migration from FPAN (Funding Primary Account Number) to Network Tokens.

If a permanent Vault token does not already have associated Network Tokens, the system will attempt to provision one, provided the following conditions are met:

• The gateway used for the charge supports Network Tokens.
• Network Token Service is connected for the relevant scheme and “Set as default” = true.
• The registration connected to the Network Token Service is in “Completed” status.

Impacted Functionality: Subscriptions, Verify

• Extended Data Migration reporting capability with encrypted file output using Merchant PGP key

Added encryption for migration output report before sending it to the merchants. This ensures secure delivery of sensitive information.

Impacted Functionality: Data Migration Reporting

• Updated the Data Migration reporting to correct some field names

Updated Data Migration result reports for MPGS, Stripe and Braintree gateways by renaming specific fields to ensure consistency across reports.

Impacted Functionality: Data Migration Reporting

• PRODUCTION RELEASE DATE: 23/10/2024
• SANDBOX RELEASE DATE: 9/10/2024

Go to Changelog Release 88

New Features:

• Enhanced security for storing data according to PCI DSS v4.0 requirements

Implemented field-level, or file-based, encryption in accordance with PCI-DSS v4, which surpasses the previous disk-level encryption standard in v3. This ensures sensitive data is encrypted using industry-standard encryption algorithms, enhancing overall data security.

These improvements minimise the risk of data breaches, safeguard sensitive information and reduce the potential for financial loss and reputation damage.

Impacted Functionality: Vaults

• Implemented EFTPOS compliance mandate changes (and passed certification with EFTPOS)

Implemented EFTPOS compliance mandate changes including:

• Passed the FirstPayment flag for /purchases and /reversals EFTPOS API. Paydock defines if this is a First Payment or not. If using the Vault for the first time for a financial transaction, the flag is set to true. For subsequent payments with Vault First Payment, the flag is set to false.
  • Note: 3ds and fraud check with Vault are NOT considered financial transactions. EFTPOS requires to provide CVV for financial transactions when First Payment = true
• Added fbkResponse field to the response for /purchase, /refund, /accountVerify endpoints. This field indicates if a transaction has been approved/declined in stand-in mode by EFTPOS hub due to the Issuer being unavailable.
• Added an optional repeat flag in request for /reversals endpoint. Paydock will send this flag to EFTPOS when a reversal fails due to EFTPOS issues during retry attempts.

Impacted Functionality: EFTPOS

• Network Token generation “On Fly“ during charge processing

Enabled the creation of Network Tokens for existing Vaults during charges processing ensuring seamless migration from from FPAN (Funding Primary Account Number) to Network Tokens.

If a permanent Vault token does not already have associated Network Tokens, the system will attempt to provision one, provided the following conditions are met:

• The gateway used for the charge supports Network Tokens.
• Network Token Service is connected for the relevant scheme and “Set as default” = true.
• The registration connected to the Network Token Service is in “Completed” status.

Impacted Functionality: Charges

• Enhanced Network Tokens for Visa Vault

Visa Vaults cannot create Network Tokens without an associated email. If an email is not provided in the Vault creation request, Paydock will automatically generate one. We recommend merchants to use Paydock generation for rare cases, despite this not impacting the success rate of provisioning request or transactions.

Impacted Functionality: Network Tokens

• Added logs for Network Tokens

Improved error troubleshooting by adding the ability to view logs for Network Tokens provisioning, Network Tokens revoke, and Network Tokens issuer updates.

Impacted Functionality: Network Tokens

• PRODUCTION RELEASE DATE: 2/10/2024
• SANDBOX RELEASE DATE: 19/9/2024

Go to Changelog Release 87

New Features:

• Data Migration Extension: MPGS Fetch

This extension enhances the existing “Data Migration” feature, offering merchants a secure and reliable method to fetch large volumes of sensitive records from the old processor API (e.g., MPGS) and import them into the Paydock Vault. The goal is to ensure a seamless transition with no data loss.

Key Benefits:

• Merchants can easily transition to Paydock and begin transacting with migrated tokens with minimal effort.
• Ensures secure transfer of sensitive payment data, upholding data accuracy and compliance with security standards such as PCI DSS.
• Addresses encryption, tokenisation, and secure transmission challenges to maintain high data protection standards.

Please note that the reporting capabilities for MPGS Fetch will be released as a part of R88.

Impacted Functionality: MPGS

• Introduced registrations & services creation for Network Tokenisation via Dashboard

Enabled registrations and services creation for Network Tokenisation using Dashboard to simplify merchants onboarding and encouraging self-onboarding, as well as Network Tokens provisioning.

Impacted Functionality: Services, Registrations

• Introduced support for the processing of NT via Cybersource Gateway

Enabled support for the processing of Network Tokens (Mastercard & Visa) via Cybersource gateway for charges (direct charge, charge refund, cancel, auth & capture) and subscriptions.

Impacted Functionality: Network Token (Mastercard & Visa), Cybersource gateway, Charge & Subscription

• Introduced support for the processing of NT for standalone refunds via MPGS

Enabled support for the processing of Mastercard and Visa Network Tokens via MPGS gateway for standalone refunds requests.

Impacted Functionality: Network Token (Mastercard & Visa), MPGS gateway, Standalone refund