Learn · Change processorsChange processors
Change processors
without losing customers.
Moving to a new gateway should not mean asking every customer for their card again.
Move volume at your pace
CARDS TO RE-ENTER0saved cards keep working
DOWNTIME0add before you remove
YOUR100%control over the pace
Why switching usually hurts
Changing processors often means asking every customer for their card again, and watching renewals fail in the meantime.
When cards live in your own vault and routing is in your hands, a switch becomes a gradual move you control, week by week.
Keep the cardsSaved cards live in a vault outside your old processor, so they keep working.
Add before you removeConnect the new gateway first, send it part of your volume, then move the rest.
Split trafficSpread payments across gateways by country, card brand, amount, store or product.
Keep a backupLeave the old gateway in your cascade as a fallback while the new one ramps up.
Nothing changes for buyersSame checkout, same domain, same design. Buyers never notice the switch.
Subscriptions followChoose the gateway renewals run on, and keep your recurring revenue flowing.
A safe switch, step by step
- Connect your new merchant account.
- Test it on one store or one product.
- Route more volume to it with your rules.
- Keep the old one as a backup in your cascade, or turn it off.
Who it’s for
Merchants unhappy with fees or approval ratesMerchants adding a regional gatewayMerchants preparing for a possible closure
Questions merchants ask
Can I keep the old gateway?
Yes. Leave it in your cascade as a backup for as long as you want.
Do subscriptions follow?
You choose which gateway renewals run on.