While network token adoption is rising rapidly, there are individual countries that can be ahead or behind in each region.
When you request a network token for a credit card, several factors determine if a token can be provisioned:
- Spreedly must support network tokenization for the card.
- Your Spreedly account must have the network-specific TRID associated. Without the network TRID, networks and issuing banks cannot return a merchant-specific token.
- The issuing bank must participate in network tokenization. Adoption of network tokenization by issuing banks depends on the region the issuing bank is located. North American banks currently have the highest adoption, while Latin American and European bank support is growing.
When I provision a token during a purchase transaction, will the token be used for the initial transaction? How will that impact transaction latency?
When a network token is requested, the request must travel to both the card network and the issuing bank. This provisioning process can take between 5-6 seconds, which is much too long for a purchase transaction.
As a result, any purchase transaction that also requests a network token be provisioned will default to using the PAN for the initial transaction. Subsequent transactions for the same Spreedly payment method token can use the network token since it will be stored with the payment method.
What if I have network tokens from a previous token requestor? Can the existing tokens be imported to Spreedly?
Network tokens are transferrable between token requestors. Depending on the number of existing network tokens, it is often advisable to transfer existing tokens rather than spend time reissuing tokens.
The transfer does require coordination between Spreedly, the original token requestor, and the card networks. If you have existing network tokens you would wish to transfer to Spreedly, please contact your Spreedly contact or support.