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.

Removed TransactionId from the list of required fields in the PspInfo object.

You can use the Worldpay Worldwide Payment Gateway (WPG) as a Payment Service Provider (PSP) for the following:

• Payments
  • Cardholder Initiated Transactions (CITs)
    • Payment Instruments
      • Cards
      • Digital Wallets
        • Apple Pay
        • Google Pay
  • Merchant Initiated Transactions (MITs)
    • Payment Instruments
      • BR-DGE Card-on-File
    • Types
      • Standing Instruction
        • Unscheduled
        • Recurring
  • Split Auth and Capture (SAC)
  • Mail Order Telephone Order (MOTO)
• Payouts
  • Cards
  • Apple Pay
  • Google Pay
• Refunds

For more information, see our Worldpay Integration page.

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.