|
|
Contact Cybersource Customer Support to configure your account for the Token Management Service. |
The Cybersource Token Management Service (TMS) tokenizes, securely stores, and manages:
nPrimary account number (PAN)
nPayment card expiration date
nCustomer data
nElectronic check data
TMS is compatible with the Cybersource Account Updater service for Visa and Mastercard payment cards, except with credentials-on-file (COF) network tokens. All payment information stored with Cybersource can be automatically updated by participating banks, thereby reducing payment failures. For more information, see Account Updater User Guide (PDF | HTML).
All token types are also available using the TMS RESTful services. For more information about RESTful services, see the Cybersource Developer Center.
|
Token Type |
Description |
Format |
|
Customer token For more information, see Creating Customer Tokens. |
Payment Card Transactions and Payouts Represents the tokenized: nPayment card PAN nCard expiration date nBilling information nShipping information nMerchant-defined data |
n32 character hexadecimal (default) n19 digits, Luhn check passing n16 digits, last 4 digits of card preserving, Luhn check passing1 n16 digits, Luhn check passing1 n22 digits2 (Request ID) |
|
Electronic Checks Represents the tokenized: nBank account and routing numbers nBilling information nShipping information nDriver license information nAccount type nCompany tax ID nSEC code nAlternate merchant descriptor nMerchant-defined data |
n32 character hexadecimal (default) n19 digits, Luhn check passing n16 digits, Luhn check passing1 n22 digits2 |
|
|
Available only with TMS RESTful services. For more information on creating this token using TMS RESTful services, see Cybersource Developer Center. |
||
|
Payment Card Transactions and Payouts Represents the tokenized: nPayment card PAN nCard expiration date nBilling information |
n32 character hexadecimal n19 digits, Luhn check passing n16 digits, Luhn check passing n22 digits2 |
|
|
Electronic Checks Represents the tokenized: nBank account and routing numbers nBilling information nDriver license information nAccount type nCompany tax ID nSEC code nAlternate merchant descriptor |
||
|
Instrument identifier token |
Helps you identify when the same card or bank account is used while keeping sensitive customer data secure. |
|
|
Payment Card Transactions and Payouts Represents the tokenized payment card PAN. |
n32 character hexadecimal n19 digits, Luhn check passing n19 digits, last 4 digits of card preserving (default) n16 digits, Luhn check passing n22 digits2 |
|
|
Electronic Checks Represents the tokenized bank account and routing numbers. |
n32 character hexadecimal n19 digits, Luhn check passing n16 digits, Luhn check passing n22 digits2 |
|
|
1 Token format for existing merchants who implemented Cybersource services prior to 2019. 2 Can be used only for one token type—customer, payment instrument, or instrument identifier. For instrument identifier tokens, you can use the 22-digit format for payment cards and electronic checks. |
||
|
|
Multiple merchant IDs can be configured for various token types. You receive the instrument identifier token regardless of your account’s token type. Reasons for multiple merchant IDs include: nYou have multiple processors. nPoint-of-sale terminals have unique merchant IDs, which are usually configured for the PAN-only instrument identifier token. When you have multiple merchant IDs, you can set up one token vault to which all of your merchant IDs have access or set up multiple vaults to segregate access to tokens. See Token Types and Formats. |