Switch payment processors
Switching payment processors means moving checkout, subscriptions and saved cards, then keeping the old account for refunds and disputes. Plan the overlap first.
Official sources last reviewed · How we review
Build your personalized plan
A few questions, revealed as they become relevant. Your answers stay in this browser.
Start with the basics
We never ask for phone numbers, card numbers, passwords or codes. Names of providers or nicknames are enough.
Your plan so far
11things this change touches
- critical2
- high6
- moderate3
- low0
Updates as you answer. Every item will explain why it’s there.
What could break
In a typical payment processor plan, these are the most serious things to get right.
Run both processors side by side
Critical · Business operations
If the old account closes early, you may be unable to refund customers or respond to disputes on old payments.
Coordinate a card data migration between processors
Critical · Business operations
Without a plan, every renewal and saved-card purchase after the switch fails until customers re-enter their card.
Custom checkout: update your integration
Critical · Website & DNS
A broken checkout loses sales until someone notices.
Subscriptions: move them without double charges
Critical · Business operations
Renewals stop, or customers are charged twice or on the wrong date.
Payouts: verify the bank account and plan cash flow
High · Business operations
Cash flow tightens if payouts pause while the new account is reviewed.
Export transaction history and reports
High · Data & files
Records you need later may be harder to get once you stop using the account.
Sales tax and VAT: recreate your settings
High · Business operations
Orders can be charged the wrong tax, which you may owe out of pocket.
Plan for refunds and disputes on past payments
High · Business operations
A missed dispute deadline usually means losing the dispute, and a refund issued the wrong way can charge you twice.
Webhooks: add new endpoints and keep the old one running
High · Integrations & APIs
Payments succeed but orders aren't fulfilled or accounts aren't unlocked.
Apple Pay and Google Pay: register your website domains
High · Website & DNS
Apple Pay or Google Pay quietly disappears from checkout, and wallet shoppers may abandon their carts.
Before and after the change
Before you change it
- Run both processors side by side
- Coordinate a card data migration between processors
- Payouts: verify the bank account and plan cash flow
- Export transaction history and reports
- Sales tax and VAT: recreate your settings
- Plan for refunds and disputes on past payments
After the change
- Custom checkout: update your integration
- Webhooks: add new endpoints and keep the old one running
- Apple Pay and Google Pay: register your website domains
- Fraud rules and 3D Secure: recreate your settings
- Subscriptions: move them without double charges
- Statement descriptor: use a name customers recognize
- Open invoices and payment links: reissue or replace them
- Accounting: connect the new processor and reconcile payouts
- Connected apps: reconnect them to the new processor
- PCI compliance: check what applies to your new setup
- Test live payments end to end
- Revoke old API keys
Your own plan adds or removes items based on your answers, and explains why each one is there.
The safe order
Doing things in the right sequence is what keeps you from getting locked out halfway through.
Before the change
Step 1: Plan the overlap and what can move
Saved cards, payouts, tax and exports need lead time.
- Run both processors side by side (critical risk)
- Coordinate a card data migration between processors (critical risk)
- Payouts: verify the bank account and plan cash flow (high risk)
- Export transaction history and reports (high risk)
- and 1 more
Step 2: Handle disputes and refunds on past payments
These stay with the old processor.
- Plan for refunds and disputes on past payments (high risk)
During the change
Step 3: Set up and test the new processor
Checkout, hardware, webhooks and fraud rules, tested before live payments move.
- Custom checkout: update your integration (critical risk)
- Webhooks: add new endpoints and keep the old one running (high risk)
- Apple Pay and Google Pay: register your website domains (high risk)
- Fraud rules and 3D Secure: recreate your settings (moderate risk)
Step 4: Move subscriptions without double charges
Each customer's next charge should fall on the date they expect.
- Subscriptions: move them without double charges (critical risk)
Step 5: Tell customers and replace payment links
A recognizable statement name prevents disputes.
- Statement descriptor: use a name customers recognize (high risk)
- Open invoices and payment links: reissue or replace them (high risk)
Immediately after
Step 6: Reconnect reporting, integrations and compliance
So your books and tools keep up.
- Accounting: connect the new processor and reconcile payouts (moderate risk)
- Connected apps: reconnect them to the new processor (moderate risk)
- PCI compliance: check what applies to your new setup (moderate risk)
Verify
Step 7: Test live payments end to end
Real cards, real receipts, real payouts.
- Test live payments end to end (high risk)
Clean up
Step 8: Shut down the old processor safely
Only after the dispute window has passed and the final payout has arrived.
- Revoke old API keys (moderate risk)
- Close the old processor account last (high risk)
Why this change needs a plan
A processor switch is mostly invisible to customers when it goes well, and very visible when it doesn't: failed renewals, a missing Apple Pay button, or a wave of “I don't recognize this charge” disputes.
The hardest part is usually saved cards. They're stored as tokens by the old processor, and moving them needs a PCI-compliant migration between processors, which takes coordination and time. Without one, customers have to re-enter their cards.
The old processor doesn't go away on switch day. Refunds, disputes and chargebacks for past payments stay with it, so keep it open, connected and monitored until the dispute window has passed.
Why it matters
Payments are where revenue comes in. A broken checkout, a lapsed subscription batch or a missed dispute deadline costs money directly.
What makes it risky
Risk is highest when you store customer cards for subscriptions or repeat purchases, when checkout is custom-built, and when there are open disputes. Closing the old processor too early is the mistake that's hardest to undo.
Common mistakes
- Closing the old processor account while refunds and disputes for past payments can still arrive.
- Switching checkout before saved cards and subscriptions have a plan, so renewals fail.
- Forgetting to register website domains for Apple Pay and Google Pay with the new processor.
- Changing the name on customers' statements without telling them, which leads to “unrecognized charge” disputes.
- Turning off the old webhook endpoint while the old processor is still sending refund and dispute events.
Frequently asked questions
Can I move saved customer cards to a new processor?
Often, but not always. Some processors support a secure, PCI-compliant migration of card data from or to another processor on request. It involves both processors and takes time, so ask early. If it isn't possible, customers will need to re-enter their cards.
What happens to refunds and chargebacks for old payments?
They stay with the processor that took the payment. Refund those payments from the old processor's dashboard and respond to disputes there, which is why the old account stays open after the switch.
How long should I keep the old processor account?
At least as long as customers can dispute charges taken through it. Ask the old processor how long that is for your business, and wait for the final payout and any reserves to be released.
Will customers notice the switch?
They might. Checkout may look a little different, and the name on their card statement may change. Set a clear statement descriptor and tell subscribers before their next charge.
Do I need to redo PCI compliance?
Probably. Which PCI self-assessment applies depends on how you take card payments, which can change with a new processor. Ask the new processor which applies to your setup.