Fallback using PAN

Scheme tokenization is currently being rolled out to all regions globally. However, as this is a new standard, there might be some few tokens, that are rejected due to declines at issuers.

To accommodate the conversion rate a fallback by using standard PANs for COF is recommended when creating tokens and when creating cryptograms. For that reason the integrator must store the PAN (encrypted) with the token and use the standard PAN as authorization if the token somehow fails.

Fallback when requesting token

The illustration below shows how to perform fallback for token creation.

1. Integrator requests Cardtokens to create a token by PAN data.
2. Cardtokens identifies the scheme.
3. Cardtokens requests a token against the scheme.
4. Create token fails and no token is created.
5. Cardtokens returns to the integrator without token data.
6. The integrator stores the PAN encrypted as fallback. If authorization is made it is done as standard COF using PAN.

Fallback when requesting cryptogram

The illustration below shows how to perform fallback for cryptogram creation.

1. The integrator requests a cryptogram for a token.
2. Cardtokens requests the scheme for a cryptogram.
3. Create cryptogram fails and no cryptogram is created.
4. Cardtokens returns to the integrator without cryptogram.
5. The integrator authorizes using standard PAN.