We have added the 4281
response code description as:
Transaction Error: Unknown transaction failure.
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.
paymentAccountReference
to the networkToken
object in our "Network Token Status Change Event" and "Network Token Metadata Update Event" Callback responses. tokenProvisioningStatus
field to pspTokens
object.PspTokenInstrument
to paymentInstrument
object in POST /v1/payments and POST /v1/payouts API endpoints.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:
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.
description
field for all API endpoints.
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.