We have added a stand-alone Network Token Service Provider. You can now provision Network Tokens from multiple Card Schemes via a single integration with BR-DGE.

You can use BR-DGEs Network Token Service to:

• Create CoFs and have BR-DGE provision a Network Token.
• Provision a Cryptogram for use outside of the BR-DGE platform.
• Be kept informed of the status of your Network Tokens and whether they can be used.
• Delete existing CoFs and their respective network tokens.

For more information, please see our Network Token Service Provider page.

We have added the 5305 response code description as:

Unknown outcome due to read timeout, please contact your processor.

Updated descriptions for response codes

Added support for External 3D Secure.

We have added ignoreAvs parameter to the POST and GET /v1/payments API endpoint.

This parameter allows you to ignore the result of their Address Verification Service (AVS) and process the Payment regardless.

When tokenizing payment-instruments, we now return the underlying card metadata associated with the network token in the response.
This is useful to provide accurate and up-to-date reporting of payment instruments, for merchants who wish to use this information
within their payments workflows.

We have added the Trustly Module to our Web SDK and Trustly page to PSP Integrations. Trustly is also added as paymentInstrument to our API spec.

For more information, see our Trustly Integration page.

We have added the cardOnFileSaveEnabled field to the Hosted Payments Orders endpoint. Giving you more control over the way you display card-on-file options to your customers using the BR-DGE Hosted Payments Page.

We have added the 4281 response code description as:

Transaction Error: Unknown transaction failure.

For Vault Import, we have imposed a limit on the number of tokens that can be associated with a Customer ID.

If 400 or more tokens are associated with a Customer ID, any subsequent tokenization attempts which link to
that CustomerID will be ignored.