Payment tokenization service providers are the parties that swap a card number for a token and keep the link back to it: card schemes, gateway vaults, standalone vaults and acquirers. This guide is for PSPs, acquiring banks, electronic money institutions (EMIs) and platforms deciding where their merchants’ stored cards live and who controls them.
What Is a Payment Tokenization Service Provider?
A payment tokenization service provider generates tokens that stand in for a card’s primary account number (PAN), stores the PAN behind them and turns a token back into a usable credential when a payment is made. Only the provider can make that exchange, so whoever runs it controls the stored cards.
The term covers two roles. In the card scheme sense, a token service provider is the scheme service that issues network tokens, such as Visa Token Service. The party that asks it for tokens is the token requestor: a merchant, a PSP or a gateway. eComCharge, for example, is certified as a Visa token requestor.
In everyday use, “tokenization service provider” or “tokenization solution provider” also means any vault that issues its own tokens for card data it stores. That is the sense most operators meet first, because their gateway already does it.
Definition
Token vault
The system that stores each PAN, maps it to its token and holds the keys that protect it. In a white label payment gateway the vault sits inside the platform, and merchants receive only tokens.
Tokenization is not encryption. Encrypted card data can be decrypted by whoever holds the key. A token is looked up, not decrypted: the PAN comes back only from the vault’s mapping, and only to systems the vault allows. Our post on how a gateway token works walks through the classic flow.
How Does Payment Tokenization Work, Step by Step?
A card is tokenized once, at the first payment or when the cardholder saves it, and the token carries every later charge. Your gateway, the scheme’s token service, the acquirer and the issuer each do one part. After the first step the merchant never holds the PAN.
The cardholder enters the card
The payment page or widget that your gateway hosts for the merchant captures the card number, expiry date and security code and sends them to your gateway, not to the merchant’s servers.
Your vault stores the PAN
The gateway writes the PAN to its vault and returns a gateway token to the merchant with the payment result. The merchant stores only that token against its customer.
Your gateway requests a network token
As token requestor, the gateway asks the scheme’s token service for a network token for that card and merchant. The scheme checks with the issuer that the card behind the token is a valid credential.
The merchant charges the token
For a repeat or recurring payment, the merchant sends the gateway token, the amount and one of the card transaction types. Where 3-D Secure applies to a payment the cardholder starts, your 3DS Server authenticates it first.
The acquirer submits the network token
Your gateway swaps the gateway token for the network token and a cryptogram generated for that one transaction, and sends both to the acquirer. The acquirer passes the authorization request to the scheme.
The scheme maps it, the issuer decides
The scheme maps the network token to the PAN and forwards the request to the issuer, which approves or declines. The acquirer that submitted the payment clears and settles it.
Note
Tokens change what is stored, not who is liable
Whichever token carried the payment, the acquirer that processed it receives any chargeback, and you stay financially liable to each acquirer for your merchants. Settlement also follows the acquirer, not the token type.
What Types of Payment Tokenization Service Providers Are There?
There are four types: card scheme token services, the vault inside your gateway or PSP platform, a standalone vault run by a third party, and the acquirer or processor that stores cards for you. They differ in who issues the token, where it can be used and who can take it along when you leave.
The four types of payment tokenization service provider
Type
Who issues the token and holds the PAN
Where the token works
Who controls it
Card scheme token service
The scheme issues a network token; the issuer and the scheme hold the PAN
Any acquirer that supports network tokens, for the merchant it was issued for
The token requestor that provisioned it
Gateway or PSP vault
Your platform’s vault
Every acquirer connected to that gateway
You, as the gateway operator
Standalone vault
A third-party vault outside the gateway
The gateways and acquirers that the vault forwards card data to
The vault operator, under your contract
Acquirer or processor
The acquirer’s own system
Only that acquirer
The acquirer
Card scheme token services
A scheme token service sits behind your vault, not instead of it: your gateway connects to it as token requestor. For Visa that service is Visa Token Service, which substitutes Visa card numbers with tokens. For Mastercard that service is Secure Card on File, which replaces Mastercard Digital Enablement Service (MDES) for Merchants at the end of 2026.
Gateway or PSP vault
The vault inside your gateway is the default for most operators. One integration covers card capture, the vault, network tokens and routing to every connected acquirer. A modular payment platform keeps the vault as a separate component of the same gateway.
Standalone vault
A standalone vault stores cards outside any gateway and forwards card data to the gateway or acquirer you pick for each payment. It is common in payment orchestration setups that join several gateways, and it adds a contract and a hop to every payment.
Acquirer or processor tokens
An acquirer that stores cards for you returns its own tokens, which no other acquirer can charge. It is the simplest start with one acquirer and the hardest exit, as the portability section shows.
Network Tokens vs Gateway Tokens: What Is the Difference?
A gateway token is issued by your vault and works only inside the platform that created it. A network token is issued by the card scheme, replaces the PAN up to the scheme and is checked with the issuer as a valid credential. Most operators use both: merchants hold the gateway token, your gateway the network token.
Gateway tokens and network tokens compared
Criteria
Gateway token
Network token
Issued by
Your gateway vault
The card scheme’s token service
What the acquirer receives
The PAN, which the gateway takes from the vault
The network token and a cryptogram for that transaction
When the issuer reissues the card
The stored card goes out of date unless an account updater refreshes it
The scheme checks the card behind the token with the issuer
Portability
Moves with your gateway between acquirers
Not specific to a processor, issued for one merchant
Coverage
Every card your gateway accepts
Only the schemes your gateway is connected to as token requestor
Network tokens also change approval rates. Visa reports that its tokenized card-not-present transactions show a 4.6% lift in authorization rates globally compared with the PAN.
Lifecycle updates
Network tokens stay current through the scheme: Visa says it checks with the issuer that the card behind each token is a valid credential, and its tokenization knowledge hub describes network tokens as carrying up-to-date information. Visa Token Service also lets stored credentials with an outdated expiry date be used to provision tokens.
Gateway tokens need account updater services or a new card from the customer to stay current. That gap matters most in recurring billing for software-as-a-service (SaaS) and other card-on-file models.
Rule
Mastercard is retiring MDES for Merchants
Mastercard will decommission MDES for Merchants (M4M) at the end of 2026, according to its developer documentation. Existing M4M users must integrate with Secure Card on File (SCOF) and migrate their tokens. Ask any provider which Mastercard service it uses today.
What Is Token Portability, and How Do You Migrate Tokens?
Token portability is whether stored cards keep working when you change acquirer, gateway or vault. Tokens in your own gateway vault move with you between acquirers. Tokens held by an acquirer stay with it. Without portability, every customer with a stored card has to enter it again.
Portability also decides what payment routing can do with stored cards: a card-on-file payment can go to a second acquirer only if that acquirer can charge the token.
A migration in practice
In one of our cases a high-risk PSP lost its acquirer overnight. eComCharge extracted the tokenised card data the previous acquirer could share, generated tokens for the new acquirer and resumed recurring payments with no customer action. The PSP moved 95% of the available tokens in about one week: tokens migrated in one week.
Conditions for a token migration
The previous acquirer or provider is able and willing to share the tokenised card data.
The new acquirer can accept and process the migrated tokens.
The token formats of both providers are compatible.
Someone owns the coordination: you, the outgoing provider and the new one.
The 95% in that case covers the tokens that were technically accessible. Not all tokens could be transferred, so agree the export terms before you need them.
Illustrative example
What acquirer-bound tokens cost at exit
The figures are assumptions made up for the example, not benchmarks. You hold 40,000 stored cards on monthly recurring charges, with an average charge of EUR 25. Your acquirer exits. Customers asked to enter their card again do so 55% of the time.
Illustrative figure
Acquirer-bound tokens
Portable tokens, 95% migrated
Cards migrated without customer action
0
38,000
Cards re-entered by customers
22,000 of 40,000
1,100 of 2,000
Stored cards kept
22,000
39,100
Recurring volume a month
EUR 550,000
EUR 977,500
In this example portability keeps 17,100 more cards and EUR 427,500 more volume a month. Your own figures depend on your re-entry rate and on what the outgoing provider releases.
How Does Tokenization Change Your PCI DSS Scope?
Tokenization shrinks PCI DSS scope for systems that store only tokens and cannot turn them back into card numbers. The vault, the de-tokenization process and every system connected to them stay in scope. Tokenization does not remove the need to maintain and validate compliance.
The PCI Security Standards Council sets this out in its tokenization guidelines, published in August 2011 for PCI DSS 2.0. The current standard is the PCI DSS v4.x family, so confirm the scope of each system with your assessor.
Who carries which part of PCI DSS scope
Party
What it holds
PCI DSS position
Merchant storing gateway tokens
Tokens only, card captured on your payment page
Systems that hold only tokens, segmented from the vault, may fall outside the cardholder data environment (CDE). If the merchant can retrieve the PAN, its environment is in scope
You, as gateway operator
PANs in the vault, the token mapping, the keys
In scope as a service provider for the vault and every system connected to it
Your platform vendor
Hosts and runs the vault software
Validates the platform and gives you a written split of responsibilities. Scope is shared, not handed over
Standalone vault operator
PANs for the cards it stores
In scope for its vault. Your systems that send card data to it or receive card data from it stay in scope
Rule
Tokens that can pay
Section 4.1 of the same guidelines warns that tokens usable as payment instruments, called high-value tokens, may have the same value to an attacker as the card data. Such tokens might be in scope even if they cannot retrieve the PAN. Ask your acquirer, or the schemes, which requirements apply to yours.
Handing the vault to a certified platform reduces the work you do yourself. Our post on outsourcing PCI DSS explains what moves to the vendor and what stays with you.
How Do You Choose a Payment Tokenization Service Provider?
Choose by control first and features second. Decide who must own the tokens and the token requestor relationship, then check network token coverage for each scheme, PCI DSS scope, lifecycle updates and exit terms. Put the same questions to every provider and get the answers in writing.
A gateway vault fits when
One gateway carries all your merchants’ traffic.
You want card capture, vault, network tokens and routing in one integration.
You route stored cards between several acquirers on that gateway.
A standalone vault fits when
You run more than one gateway and need one card base across them.
You plan to replace the gateway itself and keep the cards.
You accept an extra contract, an extra hop and shared PCI DSS scope with one more party.
Questions to ask each provider
Who is the token requestor for Visa and for Mastercard: you or the provider?
Which scheme token services are live today, and is Mastercard on Secure Card on File?
Can every token be exported, in which format, within what time, and who pays for it?
Can every connected acquirer charge the tokens, including for recurring payments?
How are stored cards kept current: network token updates, an account updater, or both?
What does the current PCI DSS Attestation of Compliance cover, and what is left to you?
How is vault availability measured, and what happens to payments when the vault is down?
Score every candidate on the same criteria and weight them by what failure would cost you. Portability and the token requestor role weigh most, because they decide whether you can ever leave.
Criteria for choosing a tokenization solution provider
Criterion
Why it matters
How to verify
Token ownership and requestor role
Decides who controls the tokens and the scheme relationship
Written answer for each scheme; check the contract wording
Portability
Decides whether you can switch provider without asking cardholders to re-enter cards
Export format, time and fee in the contract; a test export
Network token coverage
Network tokens stay current when a card is reissued
List of live scheme token services, per scheme
Acquirer reach
A token you cannot charge through your acquirers is useless for routing
Test charges through each connected acquirer, including recurring
PCI DSS scope
Determines what stays on your compliance list
Current Attestation of Compliance and a written responsibility split
What Are the Risks of Tokenization, and Who Does Not Need a Separate Provider?
The main risks are lock-in to tokens you cannot export, a vault that stops every stored-card payment when it fails, network token coverage that differs by scheme and high-value tokens that attract attacks. Each has a known control, listed in the table.
Tokenization risks and how to reduce them
Risk
What goes wrong
How to reduce it
Acquirer-bound tokens
An acquirer exits or goes offline, and its tokens cannot be charged anywhere else
Keep the vault at gateway level and sign an export clause with format and timeline
Vault outage
No stored card can be charged until the vault is back
Ask how vault availability is measured and how the vault is isolated from other components
Uneven scheme coverage
Cards of one scheme run on network tokens and the rest on stored PANs, with different update behaviour
Track the share of stored cards with a network token for each scheme
High-value tokens
A stolen token that can start a payment is used for fraud
Bind tokens to one merchant and monitor token use for attempted fraud
No backup route for stored cards
A recurring payment declined on one acquirer cannot move to another
Use tokens every route can charge, so cascading logic can use the second acquirer
Stored cards survive an acquirer outage only if the tokens do not depend on that acquirer. In another of our cases a slow acquirer was isolated in seconds: see acquirer failure contained.
Good to know
Who does not need a separate provider
If your gateway already runs a PCI DSS vault and connects to the scheme token services, a standalone vault adds a contract without adding control. If you are still choosing an acquirer and a licence, read how to start a payment processing company first. With one acquirer and no stored cards, you have nothing to port yet.
Payment Tokenization with eComCharge
eComCharge runs tokenization inside its white-label gateway. Cards are tokenized on the platform and held in its vault, and your merchants keep only tokens for recurring payments, one-click checkout and refunds. Because the vault sits at gateway level, the tokens work across the acquirers you connect.
A local tokenization service and card vault at PCI DSS Level 1, with annual security audits since 2012.
Visa Token Service supported since 2022 and Mastercard Secure Card on File since 2024.
Token migration between acquirers: extraction, conversion and re-tokenisation at infrastructure level.
Tokenized recurring payments with smart retry logic.
Smart Routing with more than 50 routing conditions, including bank identification number (BIN), geography, currency and amount.
A 3DS Server certified by Visa, Mastercard and UnionPay.
A SaaS installation of eComCharge takes from 1 week and an installation on your own servers from 3 months.
eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
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.
Tokens in your own gateway vault already work with every acquirer on that gateway. Tokens held by an acquirer or a third-party vault can move only if that provider shares the tokenised data, the new acquirer accepts it and the formats are compatible. In one of our cases a PSP moved 95% of available tokens in about one week.
No. Tokenization reduces scope for systems that store only tokens and cannot recover the card number. The vault, the de-tokenization process and every system connected to them stay in scope, and you still maintain and validate compliance. The PCI Security Standards Council says so in its tokenization guidelines. Confirm the scope of each system with your assessor.
No. Encrypted card data can be decrypted by anyone who holds the key. A token is looked up, not decrypted: the card number comes back only from the vault's mapping, and only to systems the vault allows. Most platforms use both, encrypting the card numbers inside the vault and handing out tokens to merchants.
Mastercard's developer documentation says MDES for Merchants will be decommissioned at the end of 2026. Existing users must integrate with Secure Card on File and migrate their tokens. If a tokenization provider still relies on MDES for Merchants, ask for its migration plan and timeline before you sign.
It depends on the deployment model, the number of stored cards, the scheme token services you need and the acquirers you connect. On eComCharge, tokenization is part of the white-label gateway. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote.
Respectfully, the eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
How PSPs and acquirers process high-risk card payments: which merchants count as high risk, who carries the liability, Visa VAMP thresholds, reserves and limits, the gateway features you need, multiple acquirers and the risks.
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, cost drivers and a 9-step launch plan.
How PSPs, acquiring banks and EMIs onboard high-risk merchants: which MCCs count as high risk, the KYB, UBO and sanctions checks EU law requires, underwriting and reserves, Visa registration and monitoring, what to automate and how to keep an evidence trail.
How a PSP protects itself from a sudden acquirer shut-off, outage or limit change: concentration risk, scheme and underwriting triggers, backup acquirers, portable tokens, volume split, an outage runbook, costs and who does not need it.
A guide to cascading payments for PSPs and acquiring banks: soft, hard and technical declines, which Visa response codes may cascade, cascade design, duplicate-charge prevention, 3DS, scheme rules, recovery KPIs and who should not cascade.
A guide for PSPs, banks and platforms on custom payment solutions: custom build vs off-the-shelf vs white-label, what can be customised, how a connector or payout flow is scoped and delivered, what drives cost and time, and the risks.