When a merchant uses the Spreedly API to complete a payment transaction for a given Spreedly token they can include the element "attempt_network_token": true to attempt using a network token for the transaction.
Spreedly has logic that checks multiple variables to determine if a network token will work for a transaction; if any variable does not pass, then the transaction will be made using the PAN associated with the Spreedly payment method token.
Alternatively, if the merchant desires the transaction be completed with PAN then the merchant can set "attempt_network_token": false, skipping the use of a network token. This fits use cases where the merchant may desire to A/B test.
What gateways support network tokens?
Check out our for currently supported gateways. Support for additional gateways is in active development. For specific gateway requests, we recommend you contact your Spreedly Account Representative so they can share it with our product team.
How soon can I start using network tokens for a transaction, after a provisioning request has been made?
- If you are retaining upon success for an authorize or purchase transaction, PAN will be used for the initial transaction and the network token will be available for subsequent transactions. This is done to prevent delays in the checkout experience for customers.
- If you are retaining a payment method without a transaction, the network token should be available for usage between 5-6 seconds after being retained. Depending on your use cases and UX you may choose to use the network token for the transaction at this point.
Can I tell if a network token was used in a transaction?
For more information we recommend reading and sections of our Network Tokenization Guide.
Could there be latency concerns for transacting with NT?
Can I choose if I want to use network tokens or not for particular transactions?
Yes, merchants can choose whether or not network tokens are used for a transaction. The transaction element "attempt_network_token" can be set to true or false, where true will attempt to use the network token and false will default to using the PAN regardless of if the payment method has a network token. If the flag is not set, the transaction always defaults to PAN.
For more information we recommend fully reading the section of our Network Tokenization Guide.
When a transaction fails using a network token, do you retry it using the credit card?
If a transaction is made with a network token but the transaction fails with the network token, we do not proactively retry the transaction with the PAN instead.
Our conversations with the networks suggest that if the transaction fails with NT it will also fail with PAN. The merchant can choose to retry the transaction with PAN if they desire by setting the "attempt_network_token": false for the 2nd transaction attempt.
Can you share a comprehensive list of possible errors when transacting with NT?
A list of network token errors, including error codes and verbose messages, can be found in the response body portion of the section of our Network Tokenization Guide.