Token Vault

Payment Data Portability: How to Move Card Data Between PSPs

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

Payment data portability is a merchant's ability to move stored card data from one provider to another without asking customers to re-enter cards. It differs from interoperability, where providers share standards so data can stay in one place.

Payment data portability: how to move card data between PSPs

Payment data portability determines whether a merchant can change payment providers without losing its stored payment credentials. A subscription business that switches payment service provider (PSP) needs every subscriber's card to keep working on the next billing date. If the cards cannot move, the merchant has to ask each customer to enter their card again, and some of them will not.

What is payment data portability?

Payment data portability is the ability of a merchant to move its customers' stored payment data, such as card data, from one provider to another. Mobile number porting is a useful comparison. A customer can move their phone number to a new carrier and keep receiving calls on the same number. Payment data portability aims for the same result. The merchant changes provider, and the customer's stored payment data keeps working without the customer noticing.

How is payment data portability different from interoperability?

Interoperability means different providers agree on common data standards so they can work with the same data directly. Portability means the data itself moves from one provider to another. With portability, the data leaves one system and arrives in another. With interoperability, the data can stay where it is and still be used by several parties.

In card payments, network tokens are the closest equivalent. Under the EMVCo payment tokenization framework, several PSPs can accept the same network token for a merchant without the underlying card number moving between them.

PortabilityInteroperability
What happens to the dataIt moves from one provider to anotherIt stays in place and is used by several parties
Typical useSwitching or adding a providerRouting between providers
Payments exampleExporting stored cards from one PSP's vault to anotherNetwork tokens accepted by several PSPs
Main trade-offExposure during the transferWider access to the same credential

The two approaches carry a trade-off. Interoperability is convenient because nothing has to move, but every party that can use a credential is another party with access to it. Portability limits access to one holder at a time, but each transfer is a moment of exposure that has to be controlled.

Why is card data difficult to move between PSPs?

Card data is difficult to move between PSPs mainly because the current provider has little commercial reason to make leaving easy. A PSP's vault token works only inside that PSP. To move, the merchant needs the PSP to export the underlying card data, and the PSP controls how, when, and at what cost that happens.

Exports are often slow, can carry fees, and are usually sent only to a single named recipient that meets PCI DSS requirements. The merchant cannot receive the file itself unless its own environment is validated to store card data. Some data cannot be exported at all. The card security code may not be retained after authorization under PCI DSS v4.0.1 Requirement 3.3.1.2, so it is never part of a migration file.

How does a card data migration between PSPs work?

A card data migration moves stored card data directly from the current PSP to a receiving party that is validated against PCI DSS, without the data passing through the merchant's systems. The receiving party imports the cards, issues new tokens, and returns a mapping file so the merchant can update its records. Most migrations follow five steps.

  1. The current PSP prepares the export. The file contains the stored card data, such as card numbers, expiry dates, and cardholder names. It never contains security codes.
  2. The file is encrypted and sent directly to the recipient. The receiving party provides its PCI DSS attestation of compliance and an encryption key. PCI DSS Requirement 4.2.1 requires strong cryptography for card numbers transmitted over open, public networks.
  3. The recipient imports the cards and issues new tokens. Each stored card receives a token from the new vault.
  4. A mapping file links old tokens to new tokens. The merchant uses it to update customer records, subscriptions, and any other system that stores the old PSP tokens.
  5. New cards go to the new provider first, then existing cards move in batches. The old PSP stays live as a fallback until each batch is confirmed.

The merchant should ask for more than card numbers in the export. Merchant-initiated transactions, such as subscription renewals, normally reference the network transaction ID of the original cardholder-initiated transaction. If that ID is not exported, the new provider has no reference to send. Our article on what happens to stored cards when you switch PSP covers timelines, account updater re-enrollment, and testing before cutover.

Why does a token vault make portability the default?

A PSP-independent token vault, such as PCI Proxy, makes portability the default because card data no longer lives inside any single processor. Instead of each PSP holding its own copy, the vault holds one copy and sends card data, or a network token, to whichever PSP processes a payment. Changing or adding a PSP then means adding a connection, not migrating cards.

The difference is easiest to see as two models:

Point-to-point modelHub-and-spoke model
Where cards are storedInside each PSPIn one vault, the hub
How PSPs receive card dataEach PSP holds its own cardsThe vault sends card data to each PSP, the spokes
Switching PSPFull card migrationConnect the new PSP
Using several PSPs at onceStored cards fragmentedAny stored card can go to any connected PSP
Who controls the dataEach PSPThe merchant, through the vault

In the point-to-point model, every provider change repeats the migration described above. In the hub-and-spoke model, the merchant migrates once, into the vault, and later provider changes do not require moving card data. Our explainer on what a token vault is describes how the vault sits between the merchant and its processors. Our article on using several PSPs and owning card data explains the multi-PSP side.