Thredd Public Tokens

When you submit a create card request to Thredd, using our web services API or cards API, Thredd generates the new card record and returns a unique publicToken linked to the physical or virtual card. When making a web service request, instead of supplying the PAN, you can include the card's publicToken, together with other mandatory information.

The Thredd public token is unique per card and cannot be used as a customer reference. (Tip: you can use the CustAccount field in the Create Card web service to add your unique customer reference to the card.)

Tokens enable you to use Thredd web services or cards API without needing to store or supply the full 16-digit card primary account number (PAN). This is especially important if you are not PCI Compliant (in which case, you will not be allowed to store or process the full PAN on your systems; for details, see Payment Card Industry Compliance).

Thredd generates two types of tokens:

• 9-digit unique random token, linked to the PAN.

• 16-digit, formed from the 3-digit identifier, plus the 9-digit token, plus the last 4 digits of the PAN.

For more information on using the Thredd public token, see the Web Services Guide.