Release Notes 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