Process a transaction

Use a payment network token to get a cryptogram and built an authorization request for a payment.

To authorize a payment, the merchant or PSP requests token details and a cryptogram.

Token details include the token PAN and expiry date.

Flow

Transaction authorization flow

Step	Description
1	The end user initiates the transaction.
2	The merchant or PSP calls Thales backend with the tokenId and transaction details.
3	Thales backend requests token details and a cryptogram from the payment network TSP.
4	Thales backend returns the encrypted token details and cryptogram.
5	The merchant or PSP builds the authorization request and sends it to the Acquirer.

API

• API reference: Create transaction

Best practices

• Treat cryptograms as short-lived. Don't store them.
• Ensure your Acquirer flow supports payment network token transactions.

Cryptogram formats

Payment networks use different cryptogram formats.

Payment network	Cryptogram name	Definition
Mastercard	DSRP Cryptogram UCAF type	Base64-encoded cryptogram. Up to 32 characters. It should be included within the dynamic payment data (DE104 SE001).
Visa	TAVV	Base64-encoded cryptogram.
American Express	DCSC	Four-digit dynamic card security code that identifies a unique AMEX Card in a transaction context.
Discover	DCID	Base64-encoded cryptogram.

Recurring and split transactions

For recurring or split transactions, send a cryptogram in the first request.

Later authorization requests usually omit the cryptogram, some countries may require a cryptogram more often.

The token PAN and expiry date can change over time. After a token update, use the latest token PAN and expiry date.

You have two options:

• Option 1: Request token details and a cryptogram for the first transaction. Store the token and the expiry date. Use Thales notifications to keep them up to date.
• Option 2: Request token details for every transaction.