Handle recurring and split transactions

Choose whether to store token metadata or fetch it for each transaction.

For recurring and split transactions, you typically need a cryptogram only for the first authorization request. Some countries can require exceptions.

The DPAN and expiry date can change over time. The first transaction after a change must use the updated token details.

You have two integration options:

• Option 1: Store token metadata

  • Get the token details and cryptogram for the first transaction.

  • Store the DPAN and expiry date in your database.

  • Use stored values for subsequent authorizations.

  • Update stored values when you receive token lifecycle notifications.

• Option 2: Fetch token metadata for every transaction

  • Request the current DPAN and expiry date each time you create a transaction.

  • Avoid maintaining token metadata locally.