We have added a maximum number of 200 Card-on-File tokens per customerID. If you exceed 200 tokens created for a customer, you will be presented with this new error code:

• 4287 Request Error: The limit of Cards on File that can be associated with a single customerID has been exceeded.

• Updated the description field for all API endpoints.
  • Added a new guide for the BR-DGE Vault Import.

We have added a new synchronousProvisioning field to the BR-DGE Vault card-on-file creation endpoint.

This allows merchants that are enabled with BR-DGE standalone network tokens to be able to provision a network token
synchronously when creating a card-on-file. Additionally, this supports synchronously creating a cryptogram for the
network token that is created in this request.

For more information around card-on-files and network tokenization, see the BR-DGE Vault page.

We have added a Risk Engine page to explain how you would interact with various different providers.

For more information, see our Risk Engine page.

We have improved our introduction to give you more information on BR-DGE and what we provide!

For more information, see our Introduction page.

Our payment flows can now be found on their own page: Payment Flows.

We have added three new error codes that our service can produce:

• 4284 Transaction Error: Unknown decline.
• 4285 Transaction Error: Do not honor.
• 4286 Transaction Error: Resubmit transaction.

We have added a paymentInstrument field to the response of the payment-status endpoint GET /v1/payments/{paymentId}/status.

This only applies to payments made using Google Pay and Apple Pay.

Information inside the paymentInstrument field includes:

• Extra card metadata
• Decrypted payload

For more information, please see the Retrieve Payment Status section of the Google Pay Feature page.

We have changed the 4254 response code description to:

Transaction Error: Unknown or expired payment nonce or token.

We have added a new payment status, EXPIRED.

When a notification with EXPIRE is received from a Payment Service Provider (PSP), we will update the payment status to a new status of EXPIRED and return the new response code:

4283 - Transaction Error: Authorization expired.

The reason for the expiration can vary according to card scheme, please contact your PSP if you require further information.

We have added fingerprint and fingerprintExtended fields to the response of both GET /v1/payments/{paymentId}/status and GET /v1/payouts/{paymentId}/status.

This functionality is only for payments and payouts using CARD.