Network Token Provisioning
Network token provisioning is a secure method for generating card network payment credentials. This process enables cardholders to make online payments while keeping their actual card details protected. Network tokens replace sensitive card data with unique, encrypted tokens that can only be used for authorized transactions.
Use Cases
- Processor Flexibility: Pass tokens between processors for increased flexibility and network redundancy
- Subscription & Recurring Payments: Securely store tokens for recurring charges, to process recurring payments without recollecting payment credentials
- Account Funding: Process network tokens for account funding transactions without storing the underlying PAN
- Cross-Border Payments: Facilitate international transactions with reduced fraud risk and compliance overhead
- Improved security: Network tokens replace the Primary Account Number (PAN) during transaction processing, reducing exposure to sensitive card data and helping meet PCI-DSS requirements.
- Higher Authorization Rates: Network tokens stay current when eligible payment cards are reissued, replaced, or renewed. Card networks automatically update the token, helping reduce declines caused by outdated card credentials.
- Standardized Payment Tokens: Network tokens can be routed to supported payment processors with standardized payment credentials across the payments ecosystem.
Token Provisioning Flow
PCI StandardsAny client handling sensitive card information is required to meet a specified level of PCI DSS (Payment Card Industry Data Security Standards).
Raw Card Token Provisioning Flow
You are PCI Certified and can handle card in the clear.
- You add the raw card information to your Create a Token API request.
- TabaPay returns with a network token ID.
- You can now save the network token ID to send to TabaPay in the future using Retrieve Token to receive the full token number.
Token Provisioning Flow with Account ID
- You use a pre-existing TabaPay Token (accountID) to add to your Create a Token API request.
How Token Provisioning Works
Prerequisites
All requests require your FQDN and your ClientID in the URL endpoint. For more information on creating a request, refer to Make Your First API Call.
Any client handling sensitive card information is required to meet a specified level of Payment Card Industry Data Security Standards (PCI-DSS).
Optional: Help confirm your card payment instrument and customer with Query Card API with AVS + ANI.
General API Prerequisites
If you are using TabaPay Tokens for Source Account information, be sure to grab the accountID originally generated from Create Account.
Clients handling sensitive card data must comply with Payment Card Industry Data Security Standards (PCI-DSS).
Note: All requests should be in a compressed format.
Network token provisioning leverages the infrastructure of major card networks to create a secure bridge between cardholders, issuers, and merchants. When a cardholder provisions a card, Primary Account Numbers (PANs) remain secure and are never exposed as raw card information:
Create Token
PCI StandardsAny client handling sensitive card information is required to meet a specified level of PCI DSS (Payment Card Industry Data Security Standards).
Request
For request body field descriptions, refer to Create Token API Body Params.
{
"type": "Network",
"account": {
"card": {
"accountNumber": "4111111111111111",
"expirationDate": "202912",
"securityCode": "123"
}
}
}{
"type": "Network",
"account": {
"accountID": "22CharTabaPayAccountID"
}
}Response
For response body field descriptions, refer to Create Token API Responses.
{
"SC": 200,
"EC": "0",
"tokenID": "<id>"
}Frequently Asked Questions
Yes, the actual card details are encrypted and never shared with merchants. Only the token is used for transactions.
2. How long does provisioning take?
Most provisioning requests are completed within seconds.
3. Can I use a provisioned network token for future transactions?
Yes. A provisioned network token can be stored and used for subsequent transactions according to the card network's token lifecycle and your integration.
4. Does TabaPay store the Primary Account Number (PAN)?
No. Network tokens replace the PAN during transaction processing. Refer to the TabaPay Tokens for information about stored payment credentials.
5. Which card brands support network token provisioning?
Currently, supported card brands include Visa and Mastercard.
6. What is the difference between using accountIDs and network tokens for payments?
accountIDs are secure tokens issued by TabaPay, and are for payments sent to the Create Transaction API.
Network tokens are issued by card networks and can be sent to Create Transaction API, or to other third party processors.
7. What if a card with an existing network tokens is sent in Create Token again?
TabaPay will return the exact same tokenID.
Recipes
Updated about 19 hours ago
