To process payments with network tokens you can choose between either of the following options.
- The automatic provisioning of tokens for use with the orchestration platform.
- The standalone tokenization endpoints for using the network tokens directly with the PSPs.
Before you start processing payments with network tokens, make sure you have
enabled processing with network tokens. Please contact the support team to get set up.
Automatic provisioning of network tokens
Although network tokens are agnostic tokens, not every payment service or acquirer support
the usage of network tokens that were provisioned outside of their own environment.
When you use the system to orchestrate your payment, the routing
behavior is optimized to take into consideration the limitations of the payment services you’re connecting to.
A payment service that supports externally obtained data is generally considered an open loop connection,
while one that doesn’t is considered closed loop.
In the orchestration platform, network tokens can be supported across any open-loop
payment services. You don’t have to perform any additional integrations to use network
tokens besides storing the original card data (PAN) in the vault.
You can follow the regular flow of card integrations, and the original card details are automatically swapped out
with the network token when possible.
For each first time use of the token a cryptogram is provisioned. Subsequent merchant initiated
transactions (MIT) do not need a cryptogram (these are optional), unless the transaction is done
with a newly provisioned token. For example if you have migrated an already running billing
sequence for a card to the systems and for these cards you’re provisioning tokens for the first time,
the first transaction done with that token has a cryptogram provisioned automatically.
The token and cryptogram are provisioned as “on file” and therefore the buyer does not have
to be present for the provisioning of either the token or the cryptogram.
The usage of network tokens has been optimized by implementing scheme best practices
regarding cryptogram usage, as well as the correct payment flagging towards the payment services.
Using Flow, it is possible to choose the instrument (PAN or Network token) in your
routing rules, allowing you to optimize your routing behavior.
For best practices and advice on routing optimizations, please reach out to the support team.
Standalone tokenization endpoints
The API allows you to provision network tokens and cryptograms for use in your own system.
Please note that network tokens can be considered PCI sensitive data depending on your
interpretation of PCI guidelines, and therefore these API’s are not enabled in production by default.
You can use the network token endpoints to obtain network tokens and their cryptograms
for use in your own system.
Network token provisioning via the API is not enabled by default in production.
Please contact support for further guidance.
