Switching Payment Processors: A Checklist That Prevents Downtime

Switching processors is not risky because the technology is hard. It is risky because a service business has money in flight, cards on file, recurring plans running, and an accounting system that expects deposits to look a certain way. Every horror story is the same story: somebody flipped the switch before the new account was ready, and a week of payments went sideways.

Run it as a migration with an overlap period and none of that happens.

Before you sign anything

Two things to establish, in writing, while you still have leverage.

• The complete fee list from the new processor, discount rate, per-item, monthly service, PCI, gateway, batch, annual, minimums, chargeback and retrieval fees. Not the headline rate.
• Your exit terms with the current processor, term length, early termination fee, notice period, and what happens to equipment you are leasing. Equipment leases in this industry are frequently separate contracts with their own terms and they do not cancel because you left.

Also ask the new processor one specific question: can stored card tokens be migrated, or will customers need to re-enter their cards? For a business with recurring plans this is the single most consequential answer in the whole process.

The card-on-file question

If you run subscriptions, memberships or maintenance plans, your stored cards are the business. Losing them means asking hundreds of customers to re-enter payment details, and you will not get all of them back.

Token migration between processors is sometimes possible and always requires planning between both parties. Where it is not possible, plan a re-authorisation campaign properly: text a secure update link, give a real deadline, follow up twice, and have technicians capture cards on site during scheduled visits in the migration window. Expect this to take a full service cycle, which for a quarterly business means a quarter.

Run both accounts in parallel

The overlap is what makes a migration safe. Keep the old account open and funded while the new one comes up, and move volume deliberately rather than all at once.

A two-week overlap works for most service businesses. Take a handful of real transactions on the new account on day one, different amounts, different card brands, one refund, and confirm the deposit lands in the right bank account on the expected day. Only then start moving real volume.

The migration checklist

• Confirm the deposit bank account, including the descriptor that will appear on customer statements.
• Test a sale, a refund and a partial refund. Confirm each one appears correctly in reporting and settles as expected.
• Verify the statement descriptor with a real card. A wrong descriptor is the fastest way to generate disputes.
• Move recurring plans in batches, not all at once, and reconcile each batch before moving the next.
• Re-point any integrations, accounting sync, scheduling software, e-commerce, and test each one end to end.
• Retrain the field team on the new flow before go-live, not during it.
• Complete PCI validation on the new account so you never pay a non-validation fee.
• Keep the old account open for at least one full settlement cycle after the last transaction, so refunds on old sales can still process.

Refunds are the trap

A refund generally has to be processed against the original transaction, on the processor that took it. If you close the old account the day you go live, you lose the clean path to refunding sales taken the week before, and you end up sending cheques.

Keep the old account open, with a small float if the processor requires one, until the refund window on your last transactions has passed, typically thirty to ninety days depending on your business.

Tell your customers only what they need

Most customers do not need to know you changed processors. What they need to know is what will appear on their statement if the descriptor changes, and what to do if you are asking them to re-enter a card.

Keep the message short, send it in the channel they already use with you, and give it a deadline. Long explanations invite questions; a clear instruction gets action.

Reconcile the first month deliberately

At the end of the first full month, do a real reconciliation: total collected, total fees, total deposited, and the effective rate. Compare it to the same figures from your last month on the old processor.

This is the step that tells you whether the switch achieved anything. Merchants who skip it end up two years later unsure whether the change helped, which is how they become receptive to the next pitch and start the cycle again.

What to take away

Get the full fee list and your exit terms in writing, settle the card-on-file question before you sign, run both accounts in parallel for two weeks, test sale-refund-descriptor with real transactions, migrate recurring plans in reconciled batches, keep the old account open through the refund window, and reconcile the first full month against your last one. Done that way, switching is administrative rather than dramatic.