Skip to main content
Regardless of which tokenization method you used to capture a card, the result is the same: a token. Every token works the same way and gives you access to the same management capabilities.

​
What a Token Contains

A token represents a complete card record. All data associated with a card is stored within the single token, regardless of how much or how little was provided at capture time:
  • PAN (Primary Account Number). The full card number.
  • Expiration date.
  • Cardholder name.
  • CVV (if captured). Subject to CVV retention policy.
  • 3D Secure authentication data (if captured). CAVV, ECI, and transaction ID from 3DS challenges.
  • Non-sensitive metadata. Card type, masked number (first 6 / last 4), creation date, creator reference.
Whether a card was tokenized with just a PAN or with full details including CVV and 3DS data, it is all stored in one token.

​
Token Identifier

Every token is identified by a cardURI:
Use this cardURI in all API calls that reference the token.

​
What You Can Do

​
Next Steps

Use Tokens Guide

All the ways to put your stored tokens to work