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.
Shops / Demo shop / Card tokens
Card tokens
Card data is held in the PCI DSS Level 1 vault. Your merchants store only the token.| Card | Token | Used for |
|---|---|---|
| Visa •••• 1246 | tok_7f3a…9c21 | Recurring |
| Mastercard •••• 4410 | tok_c08e…31aa | One-click |
| Visa •••• 0087 | tok_51d2…e7f0 | Recurring |
| Mastercard •••• 9931 | tok_a4b9…06cd | Refunds |
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.
-
Tokenize the card
A tokenization request checks the card and runs 3-D Secure. No money is taken from the card account.
-
Receive the token
The response carries the card token. The merchant stores it instead of the card number.
-
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.
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.
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.
Subscription / Monthly plan
| Date | Amount | Status |
|---|---|---|
| 1 November | €29.00 | Successful |
| 1 October | €29.00 | Successful |
| 1 September | €29.00 | Successful |
| 1 August | €29.00 | First payment |
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 studyUse 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.
# Input: PAN,MMYY (test card numbers) 4200000000000000,0128 5555555555554444,1127 # Output: one stamp per card, ready for a Smart Routing file set stamp a91f…e2c4 07bd…5f13
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.
{
"request": {
"amount": 100,
"currency": "EUR",
"description": "Save card for subscription",
"return_url": "https://example.com/return",
"credit_card": {
"number": "4200000000000000",
"verification_value": "123",
"holder": "John Doe",
"exp_month": "01",
"exp_year": "2028"
}
}
}
// Response: the card token, then pay or authorize with it
Where it’s used
95% of tokens migrated in one week, acquirer switch with zero customer impact
A high-risk PSP lost access to their acquiring partner overnight. The question wasn't whether to find a new acquirer. It was whether they could keep their entire recurring …
95% Tokens migrated~1 week Full migration0 Payment interruptions Read the case studyFrequently 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.
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.