Tokenization

Store the token. Never the card.

Local vault, Visa Token Service and Mastercard Secure Card on File in one platform. Recurring and one-click payments without card data in your merchants' systems.

PCI DSS Level 1 vault VTS since 2022 Mastercard SCOF since 2024
How tokenization works

The card number never reaches your merchants.

Tokenization replaces the card number (PAN) with a token that is worthless outside the platform. Merchants keep the token for the next payment; the card data stays in the PCI DSS Level 1 vault.

  1. Tokenize the card

    A tokenization request checks the card and runs 3-D Secure. No money is taken from the card account.

  2. Receive the token

    The response carries the card token. The merchant stores it instead of the card number.

  3. Pay with the token

    Send a payment or an authorization with the token. When the token saves card details, make that transaction within one hour, or 3-D Secure runs again.

Token types

Local vault and network tokens, side by side.

Use the platform’s own vault for every card scheme, and the card networks’ token services where the scheme supports them.

Local tokenization and card vault

Cards are tokenized on the platform and held in a PCI DSS Level 1 vault. Raw cardholder data never enters or stays in your merchants’ systems.

Visa Token Service (VTS)

Network tokens issued by Visa, supported on the platform since 2022.

Mastercard Secure Card on File

Mastercard SCOF tokens for stored cards, supported on the platform since 2024.

Recurring and one-click

Charge a returning customer without asking for the card again.

One token serves subscriptions, memberships, one-click checkout and refunds. The merchant never holds the card number, so its PCI DSS scope stays small.

  • Subscriptions and memberships. Tokenized recurring payments, fully automated.
  • One-click checkout. The customer confirms, the token pays.
  • Refunds. Back to the same card, by token.
Token migration between acquirers

Change acquirer and keep every stored card.

When a PSP moves to a new acquirer, the platform extracts the tokens, converts them and tokenizes them again for the new partner. It happens at the infrastructure level, so customers do nothing.

Read the case study
Case study 02 / High-risk PSP, recurring payments
Tokens migrated95%Of available tokens
Full migration~1 weekNo rebuild of the base
Customer action0No card re-entered
1. Token extraction from the previous acquirerDone
2. ConversionDone
3. Re-tokenization for the new acquirerDone
Card stamps for your rules

Use card lists in rules without storing card numbers.

The data encryption service turns card numbers into stamps: a secure representation of the card. Stamps go into file sets in Smart Routing, so a rule can match a list of cards while nobody keeps the PANs.

  • PAN, or PAN and expiry date. With the expiry date, a reissued card is not caught by limits set on the old one.
  • CSV in, CSV out. Up to 30,000 rows and 1 MB per file.
  • On request. The service is activated for the PSP.
Data encryption in the knowledge base
For developers

One request to get a token.

The tokenization request takes the order and card details and returns the token with the 3-D Secure verification details. The same API then accepts the token in payment and authorization requests.

Frequently asked questions

A payment tokenization service provider replaces a card's primary account number with a token, stores the card number behind it and turns the token back into a usable credential when a payment is made. Card schemes, gateway vaults, standalone vaults and acquirers all act as providers, and whoever runs the vault controls the stored cards.

There are four types. Card scheme token services issue network tokens. A gateway or PSP vault issues tokens that work with every acquirer connected to that gateway. A standalone vault stores cards outside any gateway and forwards them. An acquirer or processor issues tokens that only it can charge. Most operators combine a gateway vault with scheme network tokens.

A gateway token is issued by your vault and works only inside the platform that created it; the acquirer still receives the card number. A network token is issued by the card scheme, travels to the acquirer with a cryptogram for each transaction and is checked with the issuer as a valid credential. Visa describes network tokens as carrying up-to-date card information.

Tokenization

Keep card data out of your merchants’ systems.

Talk to us about local, Visa and Mastercard tokens, and about moving your stored cards from another acquirer.