Network Tokens
How network tokens work, how to activate them on a contract and where to find network token data.
Tokenization replaces sensitive card data with tokens that can be used safely across payment flows. Instead of the raw PAN (Primary Account Number, the card number), transactions are processed with tokens that:
- reduce exposure to sensitive data;
- improve security and compliance;
- make payment flows more resilient.

Tokenization is not a separate feature: it is built into the payment infrastructure. Two tokenization layers are supported.
Token types
| Token type | Issued by | What it gives you |
|---|---|---|
| Merchant token (Card Vault) | The platform | Secure storage of card data, reuse across PSPs and full control over payment routing. |
| Network token | Card schemes (for example Visa or Mastercard) | Stronger security for card transactions, better authorization performance and better lifecycle management than PAN-based payments. |
Network tokens
Network tokens are secure, scheme-issued tokens that replace raw card data during payment processing. Transactions are processed without exposing sensitive card information. Network token data is stored at transaction level.
Network tokens are more than another token format. They are:
- issued and managed by card schemes;
- updated dynamically, for example when a card is renewed or reissued;
- recognized by PSPs and acquirers.
This makes them more resilient than PAN-based payments.
You keep visibility and control over your network token usage. You can:
- track where tokens are used, when providers return this data;
- analyze performance across PSPs;
- carry tokens across your payment stack.
How network tokens work
Network tokens run inside your existing payment flow.
| Behaviour | What it means for you |
|---|---|
| No additional integration | You activate network tokenization at contract level by selecting a supported network tokenization partner. No API change is needed. |
| Automatic link with the merchant token | When network tokens are activated, they are linked to your merchant token automatically: no duplicated data and no change to your integration. |
| Routing between partners | If the provider supports network tokens, the token is used. If not, the transaction uses the PAN. |
| Automatic fallback | If a network token cannot be used, the transaction falls back to the PAN, without manual intervention. |
| No migration | Network tokens apply to existing payment flows, without migrating existing data. |
Step by step
- Activation at contract level. You enable network tokenization by selecting a supported partner in the contract configuration.
- Token link. When a payment method is tokenized, the network token is linked to the existing merchant token.
- Token check during payment. During authorization, the platform checks whether a network token is available and usable.
- Routing. If the selected provider supports network tokens, the transaction is processed with the token and its cryptogram. If not, the transaction falls back to the PAN.
- Transaction enrichment. Each transaction records whether a network token was used, so you can analyze and track performance.
Configure network tokenization
In the contract configuration (Store › Contracts), the Network tokenization field lets you select a supported partner.


The available options depend on your setup and can include:
- Finaro;
- Cybersource;
- other providers, added progressively.
The selected payment provider must also support network tokenization. Activation requires no migration and no API change.
Where to find network token data
Order details
The order detail page has a dedicated network token section. It shows:
- whether a network token is present;
- whether it was requested and used;
- token-related attributes.
Your teams can see at a glance how a payment was processed.

Transaction details
Network token data is also available at transaction level, for deeper analysis of payment performance. Each transaction can show:
- whether a network token was used;
- whether tokenization was requested;
- the outcome of tokenized transactions.

API response
Network token data is also returned in the order API response.

Analytics
Network token data is available in Analytics as filters, columns, dimensions and indicators. Use it to:
- measure the impact of tokenization on conversion;
- compare PSP performance;
- track the adoption of network tokens.



Dimensions
- Network token
- Network token requested
- Network token used
- Network token partner
- Token expiration data
Indicators
| Indicator | Definition |
|---|---|
| Network token usage rate | Percentage of transactions using a network token. |
| Transactions using network tokens | Number of transactions using a network token. |
| Authorized transactions using network tokens | Number of authorized transactions using a network token. |
| Transaction success rate using network tokens | Percentage of approved transactions using a network token. |
| Authorization success rate using network tokens | Percentage of authorized transactions using a network token. |
Deduplicated checkout indicators
Network token data makes analysis more accurate through deduplication. Available metrics:
- Deduplicated checkouts by customer ID
- Deduplicated checkout conversion rate
- Checkout-to-authorization rate
- Authorized transaction rate
Tokenization operations
Two operation types track tokenization:
- Tokenization
- Network Tokenization


These operations show when tokenization occurs, how tokens are used, and any failures or fallbacks. Tracking network token usage at transaction level helps you:
- identify performance differences between tokenized and non-tokenized payments;
- analyze provider behaviour;
- debug authorization issues.
Network token fields
In the Console
These fields are available at transaction level:
| Field | Description |
|---|---|
| Network token | Indicates if a network token is associated with the order. |
| Network token requested | Indicates if tokenization was requested. |
| Network token used | Indicates if the token was used during the transaction. |
| Network token expiration month | Expiration month of the token. |
| Network token expiration year | Expiration year of the token. |
| Network token requestor ID | Identifier of the token requestor. |
| Network token cryptogram | Cryptographic value used for validation. |
| Network tokenization partner | Tokenization provider. |
In API notifications
Network token data can be included in API payloads for order and transaction events.
| Field | Description |
|---|---|
network_token | Value of the token provisioned by the scheme. |
network_token_requested | Indicates if tokenization was requested. |
network_token_used | Indicates if the token was used. |
network_token_expiration_month | Expiration month. |
network_token_expiration_year | Expiration year. |
network_token_requestor_id | Requestor identifier. |
network_token_cryptogram | Cryptographic value. |
network_tokenization_partner | Tokenization provider. |
- Fields are present only when relevant.
- Values depend on provider capabilities.
- Token data follows the same lifecycle as the transaction.
Network tokens complement existing identifiers, they do not replace them. In your integration, handle token fields as optional, do not assume a token is always available, and support fallback scenarios.
Related pages
Updated 19 days ago