We have updated our documentation to provide better security and clearer guidance on handling webhook notifications.

What’s New:

Notification Authentication: We have released a new guide for authenticating notifications. This modern approach ensures your webhook endpoints remain secure and verified.

Notification Retry Strategy: To help you build more resilient integrations, we’ve added a detailed breakdown of our retry logic, including delivery intervals and failure handling.

Changes & Deprecations:

Notification Hashing Deprecated: The Notification Hashing documentation is now deprecated. The new Notification Authentication method officially replaces it. We recommend all users transition to the new authentication standard to ensure long-term compatibility.

For any questions regarding these updates, please reach out to our support team or your account manager.

We have enhanced the Payment Instrument Tokenisation API giving you the ability to manually trigger Network Token Provisioning for an existing BR-DGE card on file.

This endpoint can be used when a BR-DGE CoF was created but no Network Token was provisioned during this creation process. This could be due to Network Token support not being enabled when the CoF was originally created, or a temporary failure to provision Network Tokens.

Check out the Create a Network Token for a Card-on-File endpoint for more information.

We have added support for the following PSPs & Alternative Payment Methods.

PSP Connections

Walletdoc

Walletdoc is now a supported provider for card payments in our payments API, including Network Tokens, Apple Pay and Google Pay

Worldpay Access

Worldpay Access is now a supported provider for bank to bank payouts using our Payouts API.

APM Connections

OTT

We have added support for OTT, a payments voucher provider based in South Africa, to our payments API

Bank2Bank

We now have the Bank2Bank payment instrument payment instrument for both our payments and payouts APIs. Bank2Bank is an EFT solution in South Africa.

Revolut Pay

We now have the Revolut Pay payment instrument for both our payments and payouts APIs. Revolut Pay allows Revolut Account holders to make payments and payouts with their Revolut accounts

The following card types have been added to token queries, payment responses, and notifications:

• CHARGE
• DEFERRED_DEBIT
• PREPAID
• PREPAID_RELOADABLE
• UNKNOWN

We have added the following new Response Code.

• 4505 Voucher not found.

We have added the following new Response Codes.

• 4503 Voucher not Redeemable.
• 4504 Voucher Already Redeemed.

We have added the following new Response Code.

• 4803 Maximum transaction amount for merchant exceeded.

We have enhanced our Trustly integration with the below changes:

• Trustly Integration Upgrade: We've enhanced our Trustly integration with the addition of new payment instrument verification and registration endpoints. This upgrade improves security and streamlines the process for verifying and registering payment instruments.
• Payout Flow Update: The payout flow now requires an accountId to be retrieved from the new payment instrument verification or registration endpoints, ensuring a more robust and secure payout process.
• New Notification Types: Two new notification types have been introduced: paymentInstrument.accountSelection and paymentInstrument.accountRegistration. These notifications will keep you informed about the status of payment instrument account selection and registration.
• New Response Code: A new response code, 1004 Success, has been added to provide clearer communication for successful requests.

For more detailed information on these changes, please refer to the Trustly Integration page and the Notifications page of our documentation.

We have added the following new Response Codes.

• 4630 Payout has been reversed.
• 4631 Customer dispute.
• 4632 Cardholder name incorrect.
• 4633 National ID is not associated with this customer.

We have added the following new Response Codes.

• 1004 Success
• 4293 Customer Name Verification Failed
• 4294 Transaction Rejected By Customer
• 4295 Transaction Rejected By Issuer
• 4296 Transaction Has Violations
• 4297 Payment Attempt Blocked
• 4407 Refund Error: Transaction has already been refunded (fully or partially) and a full refund can no longer be performed
• 4408 Refund Error: Partial refund cannot be performed for this transaction
• 4409 Refund Error: Refund cannot be performed for this transaction
• 4410 Refund Error: Refund cannot be performed for this transaction as it has been voided
• 4501 Card not found at network
• 4502 Ineligible
• 4617 Payout has been declined
• 4618 Payout has failed
• 4624 Payout limit exceeded
• 4625 Payout payee account not found
• 4626 Payout held by merchant decision engine
• 4627 Switching key required
• 4628 Invalid switching key
• 4800 Transaction Error: Token payments or payouts not yet supported for the specified payment service provider
• 4801 Transaction Error: Token is not valid for the specified payment service provider
• 4700 Tokenization Error: Network token unsupported
• 5012 Server Error: Scheme reference data not present while trying to perform Merchant Initiated Transaction
• 5013 Server Error: Integration with payment service provider is temporarily unavailable
• 5306 Network Unavailable