How to Move Stored Card Tokens When You Switch Processors

Quick Answer

You can't move the tokens themselves. A token issued by one processor only works inside that processor's vault. What you can move is the card data behind the tokens: your old processor sends the encrypted card numbers directly to your new processor, the new processor creates new tokens for them, and you get a file that maps each old token ID to its new one. Your customers don't re-enter anything and you never see a card number. You have to request the transfer as the account owner, the receiving processor has to prove PCI DSS compliance, and turnaround depends on the old processor, so keep your old account open and billing until the import is confirmed. Planning a switch and worried about stored cards? Talk to our team at Argent Payments.

Short Answers to the Questions People Ask Most

Can a small business switch payment processors without losing customer data? Usually, yes. Most large processors will export stored card data to another PCI-compliant processor on request. Customer names, emails and billing addresses tied to those cards typically come along. What often does not come along is subscription schedules and payment history, so export those yourself before you close anything.

Can I move tokens from my payment processor to a new one? Not the token strings. You move the underlying card data through a processor-to-processor transfer, and the new processor re-tokenizes it. Your software then swaps old token IDs for new ones using a mapping file.

I replaced an expired business card. How do I keep every recurring payment from breaking? This one is the cardholder side of the same problem. Many merchants who bill you automatically use an account updater or network tokens, which can pick up your new expiration date or number without you doing anything. Not every issuer and merchant participates, so update the card directly with anything critical (payroll software, insurance, utilities, hosting) and watch the next billing cycle for declines.

Key Takeaways

Gateway and processor tokens only work inside the vault that created them
Migration moves the encrypted card numbers between processors, then the new processor issues new tokens
The account owner requests the export; the receiving processor must show proof of PCI compliance
Subscriptions, payment history and some wallet credentials usually don't transfer
Keep billing on the old processor until the import is verified, then turn on account updater at the new one

Why Your Tokens Don't Work at a New Processor

When a customer saves a card with you, the card number goes into your processor's or gateway's secure vault. You get back a token, a random reference string that stands in for the card. Your billing software stores the token and sends it whenever it's time to charge. This is what keeps raw card numbers off your systems and keeps your PCI compliance burden small.

The catch is that the token only means something to the vault that issued it. Send it to a different processor and it's a meaningless string, because the new processor has no record of which card it points to. That's why a processor switch can't be a simple credential swap for any business that stores cards. The card numbers have to move from one vault to the other, and only the two processors can do that.

Network tokens vs. gateway tokens

There are two kinds of tokens in play, and they behave differently in a switch.

	Gateway / processor token	Network token
Issued by	Your processor or gateway	The card network (Visa, Mastercard and others)
Works where	Only inside that provider's vault	Tied to a registered token requestor, which may be you or a provider acting for you
Card reissued or expired	Stays stale unless an account updater refreshes it	The network can update the card behind the token
In a switch	Must be migrated as card data and re-tokenized	Depends on who the token requestor is; often re-provisioned at the new processor

Network tokens get a lot of attention because the card network keeps them current when a card is reissued, which cuts down on declines for stored cards. For a switch, though, the question that matters is who registered as the token requestor. If your processor requested the tokens on your behalf, they generally belong to that relationship, and your new processor will provision fresh network tokens from the migrated card data. Ask both processors how they handle this rather than assuming network tokens travel with you.

How a Card Data Migration Actually Works

The details vary by processor, but the published processes at Stripe and Braintree follow the same basic shape:

You request the export. Stripe's documentation notes that many processors require the account owner to request the data transfer. Your new processor can't do it for you.
The receiving processor proves it can hold the data. Stripe will only transfer card data to a PCI DSS Level 1 processor and asks for its current Attestation of Compliance (AOC) or its listing on Visa's Global Registry of Service Providers. Braintree asks for an attestation of the receiving provider's PCI compliance.
The data is encrypted for the receiver. The receiving processor supplies a public encryption key (Stripe requires a PGP key of at least 4096 bits), and the outgoing processor encrypts the file with it. Only the receiver can open it.
The file moves processor to processor. It goes over a secure channel such as SFTP. Card numbers should never pass through your email, your shared drive or your laptop.
The new processor imports and re-tokenizes. It reviews the file, flags problems, creates new customer and card records, and issues new tokens.
You get a mapping file. It links each old customer and card ID to the new ones, so your billing software can point every subscription at the right new token.

Two things to know about what comes across. Card security codes (CVV) are not part of any migration, because PCI DSS doesn't allow them to be stored after authorization, so they don't exist in the old vault to begin with. And not everything in your old account is card data: Stripe, for example, exports card details, emails and metadata but not payment history or subscriptions, and excludes cards saved through its Link wallet. Pull the rest through your old dashboard or API while the account is still open.

What Argent Looks For

Before we set a cutover date, we find out where a merchant's stored cards actually live. Sometimes it's the processor's vault. Sometimes it's a gateway or the business's own scheduling or billing software, and that party is the one who has to agree to the export. That answer decides the whole plan.

Thinking about switching but stuck on stored cards?We’ll map how your cards on file and recurring billing come over before you commit to anything.

Get My Free Rate Review

What to Ask Your Old Processor, in Order

Ask these before you sign with anyone new. The answers tell you whether a clean migration is possible and how long to plan for.

Where are my customers' cards stored? In your processor's vault, a separate gateway, or your software platform's vault. The party holding the cards is the one who runs the export.
Do you export stored card data to another processor, and what does the receiver need to provide? Expect a request for the new processor's AOC and an encryption key.
Who can make the request, and is there a form or a fee? Get the exact steps in writing.
What's included and what's excluded? Ask specifically about billing addresses, customer IDs, metadata, bank account (ACH) details, wallet credentials, subscriptions and payment history.
How many exports will you run? Braintree, for example, limits merchants to two: one for the bulk of customers and one for customers added during the switchover. Plan your timing around that.
Are my cards stored with network tokens, and who is the token requestor? This tells you whether network tokens need to be re-provisioned.
How long does an export take once you have everything? Ask for their typical turnaround, not a promise.

Then ask the new processor three things: will it accept an import from your current provider, how long its import takes once the file arrives, and whether it will turn on account updater and network tokens for the imported cards.

Timeline Realities

There is no standard timeline, and anyone who quotes you a fixed number of days before talking to your old processor is guessing. The two halves move at different speeds. Stripe's own migration guide says a previous processor "might take a few days or several weeks" to transfer the data, and that Stripe typically imports within 10 business days of receiving correct data. Problems with the file, such as an expired encryption key or missing fields, add another round trip.

The practical rule: don't set a cutover date until the old processor has confirmed it will export, and build in a buffer. Our post on how to switch payment processors without disrupting billing covers the rest of the switch plan, from hardware testing to timing the cutover.

How to Keep Recurring Billing Working During the Cutover

The risky stretch is the gap between the export and the moment every subscription is pointed at a new token. A few habits keep it quiet.

Run both processors for a while. Put new customers on the new processor and keep charging existing ones on the old processor until the import is done. Stripe describes this exact approach so customers see no downtime.
Plan for card updates during the gap. If a customer updates their card at the old processor after the export file is created, that change won't be in the file. Stripe warns that such changes are lost. Either save new card details to the new processor from day one or use a second, final export to catch them.
Turn on account updater at the new processor right away. Some imported cards will have expired or been reissued in the weeks the migration took. An automatic card updater catches many of those before the first billing run.
Flag imported cards as stored credentials. Stripe notes that if cards on file aren't marked correctly for merchant-initiated charges, issuers may decline them.
Watch the first billing cycle closely. Look at decline reasons rather than retrying everything at once. Stripe cautions that mass retries after a migration can look suspicious to issuers.
Tell customers if your billing descriptor changes. A new name on the statement can trigger "I don't recognize this" disputes.
Shut off billing at the old processor. Once everything runs on the new side, confirm the old account has stopped all automatic charges so nobody is billed twice. Keep the account open, without new charges, until refunds and disputes from before the switch have cleared.

Our guide to recurring billing without failed payments covers retry schedules and customer communication in more detail.

What if the old provider won't export?

Some software platforms keep cards in a vault they don't release. If that's your situation, the fallback is asking customers to re-enter their cards through a secure payment link before their next charge. Do it in waves, starting with your highest-value accounts, and keep billing on the old system until each customer has moved. It's more work but very manageable if you start early.

How Argent Payments Approaches This

We treat stored cards as the first question in any switch, not the last. Our customer vault holds migrated and new cards as tokens, pairs with automatic card updating, and runs recurring billing on the schedule you set. We help you collect the answers from your current provider before a cutover date is on the calendar.

Want to know what a switch would involve for your stored cards? Contact Argent Payments.

Frequently Asked Questions

Will my customers have to re-enter their cards when I switch processors?

Not if your old processor exports the card data to your new one. The cards are re-tokenized behind the scenes and customers don't see anything. Re-entry is only needed when the old provider won't export or for credentials that can't be transferred.

Can I just download my customers' card numbers and upload them to the new processor?

No. Processors don't hand raw card numbers to merchants, and handling them yourself would put your business deep into PCI scope. The transfer happens directly between the two processors over an encrypted channel.

Do network tokens transfer to a new processor?

It depends on who registered as the token requestor. If your processor requested the network tokens on your behalf, expect the new processor to provision new network tokens from the migrated card data. Ask both processors before you plan around it.

How long does a card data migration take?

It varies by provider. Stripe says a previous processor might take a few days or several weeks to send the data, and that its own import typically takes up to 10 business days after it receives correct data. Plan in weeks, and don't set a cutover date until the export is confirmed.

Do subscriptions and payment history transfer with the card data?

Usually not. Card migrations cover card data and some customer details. Export subscription schedules and transaction history yourself from your old dashboard or API before closing the account, and rebuild the schedules on the new system.

Sources & Further Reading

Stripe — Request a payments data import
Stripe — Request a payment data export
Braintree — Data migration: exports
J.P. Morgan Payments — Token lifecycle
PCI Security Standards Council — pcisecuritystandards.org

Next Steps

Stored cards are the part of a processor switch that customers notice when it goes wrong, and the part that's easiest to get right with a few early questions. Connect with an Argent Payments specialist to plan how your cards on file move before you commit to a switch.