Which network token fields reach my systems?

Short answer

Order detail and API payloads carry whether a token is associated, whether tokenization was requested, whether the token was used, its expiration month and year, the requestor identifier, the cryptogram and the tokenization partner. These fields appear when they apply, and their values follow provider capability, so integrations should treat them as optional and support the PAN path alongside.

In detail

Order detail and API payloads carry a set of network token fields, so your systems and your merchants' systems can see how each payment was processed.

The fields

Whether a token is associated with the payment method.
Whether tokenization was requested.
Whether the token was used for the transaction.
The token expiration month and year.
The token requestor identifier.
The cryptogram.
The tokenization partner.

How to integrate them

These fields appear when they apply, and their values follow provider capability. A transaction routed to a provider that handles PANs only will not carry the same values as one processed with a network token. Integrations should therefore treat the fields as optional and support the PAN path alongside.

What you can do with them

Reconcile how many transactions ran on network tokens, by provider or merchant.
Feed risk and analytics tools with the tokenization context of each payment.
Support investigations, for example when comparing outcomes on tokenized and non-tokenized flows.

The same information is available in the dashboards through dedicated indicators and dimensions, and exports follow the views your merchants define, so tokenization data reaches finance and risk teams in the format they already use.

Read the full article →