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.

API Reference updates:

• Added paymentAccountReference to the networkToken object in our "Network Token Status Change Event" and "Network Token Metadata Update Event" Callback responses.
• Added new tokenProvisioningStatus field to pspTokens object.
• Updated example responses for POST and GET /v1/payment-instruments API endpoint.
• Added PspTokenInstrument to paymentInstrument object in POST /v1/payments and POST /v1/payouts API endpoints.

User Guide improvements:

• Added details about making payments and payouts by using the PSP Tokens. For more information, see Vault Interoperability page.

You can now create Payment Service Providers (PSP) tokens for your Card-on-Files in multiple different ways, outside of traditional payment flows. You can also receive notifications during the provisioning process.

For more information, see our Vault Interoperability page.