What Happens to Saved Customer Cards When You Switch Payment Processors
By Yan Payments
Do saved cards move automatically when you switch processors?
Usually not. If you’re shopping for a better processing rate and you bill customers on a card you keep on file, this is the question to ask before you sign anything. The card number itself typically isn’t what’s sitting in your system. It’s a token, a stand-in string that your current processor’s vault created and maps back to the real card on its own servers. That token is only meaningful inside that processor’s system. Hand it to a new processor and it’s just a random string with nothing behind it.
Why your old processor holds the keys
Moving real token-to-card mappings between two processors isn’t something you can do yourself with an export button. It’s a PCI DSS-governed handoff between two certified environments, and it generally needs both sides, your outgoing processor and your new one, to agree to do it. Some will cooperate for a fee. Some won’t do it at all, especially for smaller merchants. One payment infrastructure provider’s own migration guidance puts it bluntly: if you’ve got under a few hundred cards on file, it’s often not worth the formal migration process, and you’re better off just re-collecting payment details from customers directly.
What breaks if nobody plans for it
Say you run a 40-location contractor billing service, or a studio with 300 members on a monthly membership, and you switch processors without a migration plan. Every card on file at the old processor stops being chargeable the day you cut over, because the new processor has never seen those tokens before. If you don’t get ahead of it, you or your software has to re-ask every one of those customers for their card number again, and every day that takes is a day you’re not collecting on a bill that was otherwise current. Some of those customers won’t come back to re-enter a card. That’s real, avoidable revenue loss, not a processing fee.
Network tokens are slowly changing this
There’s a real exception worth knowing about: tokens issued directly by Visa (Visa Token Service) or Mastercard (MDES, now also branded Secure Card on File) aren’t tied to your processor at all. They’re tied to the card itself and recognized by the issuing bank no matter which processor submits the transaction, and the networks automatically update them when a card is reissued or expires. If both your old and new processor support network tokens, rather than only their own proprietary vault tokens, a switch can be far less disruptive. The catch is that not every processor has built this in yet, and getting access generally means your processor is set up as a registered “token requestor” with Visa and Mastercard. Ask directly whether a prospective processor uses network tokens or its own closed vault; it’s a fair question to put to a sales rep before you sign.
What a migration fee actually covers
If a formal token migration is on the table, some processors charge for it, since it involves compliance sign-off and real engineering work on both ends, not just a data export. That’s a legitimate cost, not padding, but it’s one more number to get in writing before you switch, alongside your new processing rate. If your old processor won’t cooperate or the fee doesn’t make sense for your size, the common fallback is a phased cutover: keep the old processor running the existing book of recurring customers while new customers go straight to the new processor, and let the old book wind down naturally over a billing cycle or two instead of cutting it off all at once.
A checklist before you sign with a new processor
- Ask your current processor directly whether it will do a formal token migration, and get the cost in writing.
- Ask the new processor whether it accepts network tokens from Visa and Mastercard, not just its own proprietary vault tokens.
- If cards will be migrated, confirm who re-enrolls you in Visa Account Updater or Mastercard’s updater service afterward, since that enrollment doesn’t automatically carry over either.
- If migration isn’t realistic, plan a phased cutover instead of a hard switch date, and budget time for customers who’ll need to re-enter a card.
- Give recurring customers advance notice if they’ll need to take any action at all, even a card re-entry on a web form you host for them.
None of this means you shouldn’t switch processors over a better rate or better support. It just means the card-on-file question belongs in the same conversation as price, right alongside the rate sheet, not as something you discover after you’ve already signed. If you want a second opinion on what a processor’s migration terms actually commit them to before you switch, reach out and we’ll look at it with you.
Sources:
← Back to all posts