Equitystack Pro.
Implementation Guide

Switching Payment Gateways Without Losing Revenue: A 12-Step Migration Checklist

Most gateway switches lose revenue during the cutover, not in the contract. This 12-step checklist gives every step an owner and an exit criterion. It covers token export, parallel routing, recurring billing and local payment methods.

Equitystack Pro editorial team · November 2026 · 10 min read

Where Gateway Switches Lose Revenue

You've signed with a new processor or you're about to. The commercial case is usually sound: lower blended fees, better approval rates in a growth market, or one provider where you had four. Business cases fail at the cutover. A payment gateway migration can leave a few percent of stored cards behind. It can strip recurring charges of their stored-credential history, or leave Pix on the old acquirer for weeks longer than planned. Any one of these can cancel a year of fee savings.

The losses usually come from four places:

  • Stored credentials that don't arrive. Every active card that fails to match in the token migration becomes a failed renewal.
  • Recurring charges that lose their history. If the original scheme transaction references are missing, issuers may decline merchant-initiated transactions or send them to step-up authentication. The risk is highest where strong customer authentication applies, as in the EEA and UK.
  • Disputes and reserves stuck at the old processor. Close that account too early and you lose chargebacks by default.
  • Local payment methods that fail without anyone noticing. Each method in each market has its own onboarding, certification and refund flow.

Hypothetical example: a subscription software company holds 180,000 stored cards across the UK, Germany, Brazil and India and earns $30 per card per month. At a 97% match rate, 5,400 cards are left behind. That's about $162,000 a month at risk until those customers re-enter their details, and many won't. That's why every step below has a named owner and an exit criterion. The project doesn't move on until the criterion is met.

Advertisement

The 12 Steps With Owners, Exit Criteria and Timing

StepOwnerExit criterionTypical duration
1. Inventory flows and stored credentialsPayments product leadSigned-off list of every flow, method, market and stored-credential count1–2 weeks
2. Confirm exit terms and request token exportProcurement and legalWritten confirmation of export format, timeline and fee; notice dates set2–4 weeks
3. Decide target architecturePayments engineering leadDirect integration or orchestration chosen; network token plan agreed1–3 weeks
4. Onboard new provider per entity and marketFinance and complianceKYB approved, merchant IDs live, settlement accounts tested3–10 weeks
5. Build and certify integrationEngineeringFull sandbox suite passes, including 3DS, refunds and webhooks4–12 weeks
6. Execute PCI-compliant token exportSecurity and complianceMapping file received; internal match-rate target met (we suggest 99% of active cards)2–8 weeks
7. Migrate recurring billing dataBilling ownerTransaction references, mandates and schedules mapped; sample charges approved2–4 weeks
8. Re-certify local payment methodsRegional operations leadsLive payment, refund and settlement completed per method per market2–8 weeks per market
9. Rebuild reconciliationFinance operationsTwo settlement cycles reconcile with no unexplained variance2–4 weeks
10. Ramp parallel routingPayments operationsApproval rate within agreed tolerance for every segment at each ramp stage3–8 weeks
11. Cut overProgram managerAll new traffic on new provider; legacy limited to refunds and disputesAbout 1 week
12. Wind down legacyRisk and financeDispute windows closed, reserve released, data archived6–9 months

The durations are planning ranges, not guarantees. Many steps run in parallel. A mid-sized, multi-market project typically takes four to nine months from contract to cutover, followed by a long wind-down of the old account.

Scoping the Move: Inventory, Exit Terms and Routing Design

Step 1: inventory. List every payment flow: one-off checkout, subscriptions, saved-card checkout, marketplace payouts, refunds, partial captures and manual back-office charges. For each flow, record the payment methods, markets, currencies and acquiring entity. Then count stored credentials by type: processor tokens, network tokens, SEPA or Bacs mandates, and local e-mandates. If you skip this step, you'll find the forgotten flows, such as finance's manual refund tool, in the middle of the cutover.

Step 2: exit terms. You generally can't download the card data your processor stores for you. Most large processors will send it encrypted directly to another PCI DSS Level 1 service provider. Check the contract for an explicit export commitment, file format, turnaround time and fee. Also check notice periods, early termination fees and minimum volume commitments. If the current contract doesn't mention exports, add an export clause to the new contract now so your next exit is cheaper.

Step 3: architecture. You can integrate directly with the new provider. You can also put an orchestration layer or independent vault in front of it, such as Spreedly, Primer or Gr4vy. If you operate in three or more regions or expect to use several acquirers, take the independent vault. The platform fee is usually worth it, because your next switch becomes a routing change instead of another migration. A single-region business with modest volume should integrate directly, which is simpler and cheaper. Check network tokens too. Scheme tokens are generally tied to the token requestor, so the new provider usually has to provision new ones from the underlying card number. Get written confirmation of how and when that will happen.

Onboarding, Certification and the Card Token Migration

Step 4: onboarding. Business verification (KYB) runs separately for each legal entity. Many providers also issue separate merchant IDs by country, currency or merchant category. Agree reserve terms before go-live, not after the first risk review. Data-protection rules apply to the transfer as well. Under GDPR in the EU and UK, you need a data processing agreement and a valid mechanism for any cross-border transfer. India requires payment system data to be stored locally. Several Middle Eastern and Southeast Asian markets have their own localization or outsourcing rules. Have local counsel confirm which rules apply to each entity.

Step 5: build and certify. The sandbox suite should cover:

  • 3DS challenge and frictionless flows
  • Stored-credential flags on initial and subsequent charges
  • Partial and full refunds, and voids
  • Webhook retries and idempotency

Don't sign off until every flow from Step 1 has a passing test.

Step 6: token export. The usual sequence:

  1. The new provider gives the old processor its public encryption key, typically PGP.
  2. The old processor encrypts card numbers and expiry dates and sends them over a secure channel such as SFTP.
  3. The new provider imports the data and returns a mapping file that links each old token to a new one.

Your systems never handle a full card number, which keeps your PCI scope small. Exchange Attestations of Compliance with both providers before any data moves. CVVs can't be migrated, because PCI DSS prohibits storing them after authorization. Plan a final delta export to pick up cards added after the first snapshot. Set the match-rate target in advance; 99% of active, unexpired cards is a sensible bar. Investigate every unmatched record.

Keeping Recurring Billing and Local Payment Methods Intact

Step 7: recurring billing. Card schemes expect each merchant-initiated charge to reference the network transaction ID from the customer's original authenticated payment. Ask the old processor to include those IDs in the export. Confirm that the new provider can pass them on subsequent charges. Otherwise issuers may treat renewals as unauthenticated. Mandate rules differ by market, so confirm the details with both providers:

  • SEPA Direct Debit: mandates can generally carry over when you change provider, provided your creditor identifier and mandate references stay the same.
  • UK Bacs: moving to a new service user number or bureau follows a defined bulk-change process with its own lead times. Agree the timing with both sides early.
  • India card e-mandates: RBI tokenization and recurring-payment rules often require mandates to be re-registered with customer authentication. Budget for re-consent campaigns.

Enroll in the new provider's account updater before cutover. Then run a small batch of real renewals and confirm they're approved.

Step 8: local payment methods. Treat each local method as its own integration. Examples include Pix and boleto in Brazil, UPI in India, iDEAL in the Netherlands (now being folded into Wero), BLIK in Poland, M-Pesa in Kenya, mada in Saudi Arabia, PayNow in Singapore and OXXO in Mexico. Some require a local entity or a licensed local partner. Some don't support refunds to the original method. Settlement can arrive the same day or weeks later. Move markets in order of revenue at risk, never all in one release.

Reconciliation, Parallel Routing and the Cutover Itself

Step 9: reconciliation. Map the new provider's settlement reports, fee lines and reference IDs to your ledger before real volume arrives. Until finance has reconciled two full settlement cycles, nobody can tell a pricing error from a routing bug.

Step 10: parallel routing. Ramp traffic in stages, such as 1%, 10%, 50% and then 100%. At each stage, compare approval rates by issuer country, card brand, debit versus credit, and top issuers. Track 3DS challenge rates and fraud as well. Our recommended tolerance is 50–100 basis points from the incumbent in each segment. Tighten it if your margins are thin. Agree the tolerance and rollback trigger in advance so nobody has to decide at 2 a.m. Keep the statement descriptor identical or close to it. Customers dispute charges they don't recognize.

Step 11: cutover. Stop creating tokens in the legacy vault. Run the final delta export, load the mapping and switch default routing. From then on, the legacy account handles only refunds on old transactions and dispute responses.

Winding Down the Old Processor and Budgeting the Project

Step 12: wind-down. Card scheme dispute windows often run around 120 days, and some reason codes and timing rules allow longer. Keep the legacy account open for six to nine months, keep someone responsible for submitting evidence, and track the rolling reserve until it's released. Export your chargeback and fraud history so the new provider's risk team and your own fraud models keep that context. Scheme monitoring programs generally measure dispute and fraud ratios per merchant account. Low early volume on the new account can distort them, so brief the new provider before go-live. Archive transaction data for as long as each jurisdiction where you operate requires.

Cost drivers

The figures below are typical 2026 market ranges. They vary by contract and region, so confirm them with each vendor.

  • Token export fees: often zero at large processors; some charge a one-off fee, occasionally in the low thousands of dollars or more
  • Orchestration or vault platform: roughly $2,000–$25,000 a month, plus per-transaction fees at volume
  • Engineering: commonly two to six people for three to six months
  • Dual running: minimum-volume shortfalls and monthly fees on the legacy account
  • Exit costs: early termination fees and reserves held during wind-down

Red flags

  • The outgoing processor won't put an export timeline in writing.
  • The plan routes card numbers through your own systems.
  • The new provider can't report approval rates by segment.
  • A local method is listed as "supported" but isn't available to your entity in that country.

Decision rule: if Step 2 hasn't produced a written export commitment within four weeks, don't set a cutover date. Escalate commercially, or put an independent vault in place first so your stored cards move only once.

Common questions

How long does a payment gateway migration usually take?

A mid-sized business operating in several markets typically needs four to nine months from signing to full cutover. Onboarding, token export and local-method certification partly overlap. Plan to keep the legacy account open for another six to nine months to handle disputes and reserve release.

Can we export card data from our current processor ourselves?

Generally, no. Under PCI DSS, card numbers move encrypted directly from one Level 1 service provider to another, and your own systems never see them. You authorize the transfer and receive a mapping file that links old tokens to new ones.

Will customers have to re-enter their card details after switching payment processors?

Most won't, provided the token export matches nearly all active cards and you enroll in the new provider's account updater. CVVs can't be migrated, and some markets require customers to authenticate again. Card e-mandates in India are a common example. Plan targeted re-consent campaigns for those customers.

What happens to open chargebacks after we switch?

Disputes on transactions processed by the old acquirer stay with that acquirer. Keep the account active and keep someone submitting evidence until the scheme dispute windows close. That's often around 120 days and longer for some reason codes. Export your dispute history so the new provider and your fraud models keep that context.

Should we use a payment orchestration platform for the migration?

If you operate in three or more regions or plan to use several acquirers, an independent vault or orchestration layer usually pays for itself, because later switches become routing changes. A single-market business with modest volume is usually better off integrating directly. Either way, confirm the platform's own data export terms before you sign.

What approval-rate drop should trigger a rollback during parallel routing?

Agree on a number before the ramp starts. A common working tolerance is 50–100 basis points below the incumbent in any major segment, such as issuer country, card brand or debit versus credit. If a segment falls outside that range at any stage, pause the ramp for that segment and investigate before adding traffic.

Written by the Equitystack Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.