Token Vault

Multi-PSP Strategy: Use Several PSPs and Own Your Card Data

Published:
November 18, 2026
Author:
Sascha Huwyler
TL;DR

When a PSP tokenizes a card, the token only works with that PSP. Stored cards then cannot be routed, failed over, or moved to another provider. An independent token vault stores each card once, outside any PSP, and sends it to whichever PSP processes the payment, so stored cards work with every PSP the merchant uses.

Multi-PSP strategy: why PSP tokens lock in your stored cards

Many merchants add a second payment service provider (PSP) to avoid depending on one provider. Then they find that the stored cards still depend on the first one. The reason is simple: when a PSP tokenizes a card, the token it returns only works with that PSP.

The fix is just as simple in principle. Store the card outside any PSP, in an independent token vault, and every PSP can be used for every stored card.

What is a multi-PSP strategy?

A multi-PSP strategy is a payment setup in which a merchant works with two or more PSPs and decides which one processes each payment. Merchants use it to keep taking payments during outages, to reach markets one provider does not cover, and to compare pricing between providers. These benefits apply only to payments the merchant can send to more than one PSP.

New cards entered at checkout can be sent to any PSP. Stored cards are different. Subscription renewals, one-click checkout, and other merchant-initiated transactions (MITs) all use cards saved earlier, and how those cards were saved decides where they can go.

Why does a PSP token only work with that PSP?

A PSP token only works with the PSP that created it because the token is a reference to a card stored in that PSP's own vault. When the merchant saves a card, the PSP stores the primary account number (PAN) and returns a token. The merchant keeps the token, and the PSP keeps the card. No other PSP can look the token up, so no other PSP can charge it.

A simple example shows the effect. A merchant tokenizes 200,000 subscriber cards with PSP A and later connects PSP B as a backup. During an outage at PSP A, new checkouts move to PSP B as planned. The subscription renewals scheduled that night do not, because PSP B receives tokens it cannot read. The backup covers new customers but not the existing subscriber base.

What problems does PSP-bound tokenization cause?

PSP-bound tokens turn a multi-PSP setup into separate silos of stored cards. Three problems follow.

  • No routing or failover for stored cards. Stored-card payments can only go to the PSP that holds the card, so outages and pricing differences cannot be used to move them.
  • Duplicate cards and card updates. A customer who pays through two PSPs ends up stored twice. Each PSP runs its own card update services, which can be paid for twice and fall out of sync.
  • Lock-in when switching. Leaving a PSP means asking it to export the card data, on its timeline and terms. The alternative is asking every customer to enter their card again.

Our guide to card-on-file transactions explains why stored-card payments, especially MITs, often make up a large part of recurring revenue.

How does an independent token vault solve the problem?

An independent token vault solves the problem by separating where cards are stored from where they are processed. The vault stores each card once and gives the merchant a vault token. When the merchant sends a payment, the vault passes the card data to whichever PSP the merchant chooses. Because the token belongs to the vault, not to a PSP, it works with every PSP connected to the vault.

Card tokenized by a PSPCard stored in an independent vault
Who issues the tokenThe PSPThe vault
PSPs that can charge the cardOnly the PSP that tokenized itAny PSP connected to the vault
Failover for stored cardsNoYes
Copies of each cardOne per PSPOne
Adding a new PSPStored cards are not available to itConnect the PSP; stored cards work at once
Leaving a PSPCard data must be exportedStop routing to it; no card migration

The independent vault also keeps the merchant's PCI DSS scope low, as PSP tokenization does. The merchant's systems store only tokens, and the vault handles the card data. The vault provider becomes a third-party service provider that the merchant must manage under PCI DSS v4.0.1 Requirement 12.8. Our explainer on what a token vault is covers how vaults work in more detail.

Where do network tokens fit in?

Network tokens complement an independent vault rather than replacing it. A network token is issued by the card network to a token requestor under the EMVCo payment tokenization framework, not by a PSP. Network tokens are therefore not tied to a single PSP's vault, and the card networks keep them updated when cards are reissued.

Not every card or PSP supports network tokens, so a merchant still needs the card number stored somewhere for the rest. An independent vault can hold both. It can send the network token where it is supported and the card number where it is not, through the same vault token. Our network tokenization guide explains how network tokens are provisioned.

How do merchants move existing cards into an independent vault?

Merchants move existing cards by asking the current PSP to export the stored card data directly to the new vault, which must be validated against PCI DSS. The card data is encrypted in transit and never passes through the merchant's systems. The vault imports the cards, issues new tokens, and provides a file that maps each old PSP token to its new vault token.

Most merchants first send all new cards to the vault, so the PSP's store stops growing. They then migrate existing cards in batches while the old PSP stays live as a fallback. Our article on what happens to stored cards when you switch PSP covers the process in detail.

This export happens once. After the cards are in an independent vault, adding or leaving a PSP no longer requires moving card data, because the cards were never stored with the PSP in the first place.