The trigger is almost always a number you did not expect. Maybe your quarter-end reconciliation surfaced a silent FX leak. Maybe your CA flagged missing FIRC documentation days before a GST deadline. Or maybe a legacy provider’s cross-border licence status looked shaky, and you are no longer sure your payment stack sits inside the RBI framework at all.<\/p>\n
Whatever surfaced the cost of inaction, here is the reassurance you need first: switching your international payment gateway does not require downtime. A phased parallel migration runs the new gateway alongside the old one, and with correct sequencing, no customer ever sees a failed charge.<\/p>\n
This guide gives you the exact steps, the sequencing logic, and the India-specific regulatory checkpoints, from PA-CB verification to FEMA repatriation timing, so you can migrate without breaking live revenue.<\/p>\n
Indian businesses are switching international payment gateways in 2026 for three main reasons: the RBI’s PA-CB licensing framework has made some legacy providers non-compliant, hidden FX markups are costing exporters 2 to 4 percent per transaction beyond the headline MDR, and card-based international payments, which fail at meaningfully higher rates than domestic ones, are silently driving subscriber churn.<\/p>\n
The old logic of “if it works, don’t touch it” no longer holds. A gateway that processed your payments cleanly two years ago may now be leaking margin, sitting outside the current regulatory framework, or bleeding subscribers through failed charges you never see.<\/p>\n
Your true cost is not the number on the rate card. The all-in cost formula is simple: Base MDR + FX markup + 18% GST on gateway fees.<\/strong><\/p>\n The FX markup is the spread between the interbank mid-market rate and the rate your gateway actually gives you. It is almost never disclosed on the rate card, which is exactly why it goes unnoticed for quarters at a time.<\/p>\n Put it in paise-per-dollar terms. At an INR\/USD rate in the mid-80s, a 2 percent FX markup equals roughly 170 paise of silent loss on every dollar you collect. Across a year of receivables, that compounds into a meaningful sum. Traditional cross-border wire methods often cost even more once bank fees and FX spreads stack up.<\/p>\n Traditional international wire transfers can quietly cost far more than the headline suggests once correspondent bank fees and FX spreads stack up, while modern international gateways can bring the effective cost down materially, often with faster settlement.<\/p>\n<\/div>\n The RBI’s PA-CB framework requires non-bank entities to hold a valid PA-CB licence to legally facilitate cross-border payments for Indian merchants. This is not optional.<\/p>\n Here is the part most founders miss: operating through an unlicensed cross-border aggregator creates FEMA exposure for you, the merchant, not just for the aggregator.<\/p>\n We at Razorpay hold a valid PA-CB-E&I licence, secured in December 2025 and publicly announced in January 2026, covering both inward and outward cross-border flows. Before you integrate with any provider, check the RBI-authorised Payment Aggregator list to confirm your current provider’s status.<\/p>\n Card-based international payments can fail at meaningfully higher rates than domestic transactions. For a subscription business, that failure rate is one of the largest sources of involuntary churn.<\/p>\n Intelligent routing addresses this by selecting the highest-probability processing path for each transaction in real time. Razorpay’s Intelligent Routing does exactly this. You can see the difference clearly during a parallel run, when you compare success rates side by side. Learn more about how to boost payments success rates with routing<\/a>.<\/p>\n Failed card payments are a major driver of involuntary churn. Customers stop paying simply because a card expired or was declined, even though they intended to continue.<\/p>\n<\/div>\n Two regulatory shifts should directly shape your 2026 migration timing. First, the FEMA export realisation window moves from 9 months to 15 months (18 for INR-invoiced exports) on October 1, 2026. Second, service exporters face a new monthly Export Declaration Form obligation. Both affect how you time the retirement of your old gateway.<\/p>\n If you plan your migration around a flat 9-month rule alone, you may misjudge the safe window to close your old account.<\/p>\n Under the current framework, export proceeds must be realised and repatriated within 9 months of the export date. From October 1, 2026, the FEMA 2026 Regulations<\/a> extend this window. For exports invoiced in foreign currency, the realisation period becomes 15 months. For exports invoiced in Indian Rupees, it extends to 18 months.<\/p>\n This longer window gives you more breathing room on in-flight receivables during a migration, but only if you know which regime a given receivable falls under.<\/p>\n The 2026 framework introduces a monthly Export Declaration Form (EDF) obligation for service exporters, who are given 30 days from the close of the invoice month to submit the EDF. If your migration disrupts how export data flows into your books, you could miss this monthly cadence. Build EDF submission into your reconciliation routine from day one.<\/p>\n Any unsettled receivable on your old gateway carries a realisation clock. Before you close that account, every balance must be swept to your Indian bank account and documented. Know the export date of each in-flight receivable, confirm which window applies, and never let a migration delay push a receivable past its deadline. See Razorpay’s guide to the RBI circular on export realisation<\/a>.<\/p>\n Before migrating your international payment gateway, audit six areas: all active checkout integrations (website, app, payment links), recurring billing mandates (card-on-file and UPI AutoPay), your FIRC\/e-FIRA documentation trail, your current RBI purpose code mapping, your settlement SLA requirements, and the refund and chargeback exposure window on your old gateway.<\/p>\n Skip the audit, and you will discover a forgotten payment surface only after cutover, when fixing it is expensive.<\/p>\n List every place a customer can pay you. Miss one and it breaks the moment the old gateway retires.<\/p>\n If you are unsure how mature your current setup is, assess your checkout maturity<\/a> before you begin.<\/p>\n Separate your recurring base into two buckets, because they migrate very differently.<\/p>\n Card-on-file recurring:<\/strong> tokens can potentially be migrated via a secure vault-to-vault transfer, covered later.<\/p>\n UPI AutoPay mandates:<\/strong> these cannot be migrated. Each subscriber must re-authorise on the new gateway.<\/p>\n Count your active UPI AutoPay mandates now and plan a re-mandate campaign before you retire the old gateway. Understanding what UPI AutoPay recurring payments<\/a> involve helps you scope this.<\/p>\n Pro Tip:<\/strong> Run a segment analysis on your UPI AutoPay base before migration. Subscribers on mandate for less than 3 months tend to re-authorise without prompting. High-tenure subscribers (12 months or more) should receive a personalised re-authorisation email from the founder or account manager.<\/p><\/blockquote>\n Pull a complete export of all international transaction records from your current gateway. For each transaction, confirm whether an e-FIRA (electronic Foreign Inward Remittance Advice) has been generated and saved.<\/p>\n Physical FIRCs are no longer issued for export receipts. The operative document is now the e-FIRA<\/a>, which carries a unique Inward Remittance number used to settle your export records.<\/p>\n If your current gateway does not auto-generate this documentation, request it in bulk from the gateway’s bank partner before closing the account. These records are required for GST zero-rating on service exports and for FEMA audit. Do not close the old account until every pending certificate is in hand. Finally, confirm your current RBI purpose code mapping and prepare to replicate it correctly.<\/p>\n Standard T+2 settlement is no longer adequate for SMEs managing tight working capital. By 2026, most Indian businesses expect T+1 or same-day settlement as the baseline.<\/p>\n Define your settlement SLA per use case before selecting the new gateway: T+1 for inward export receivables, and Instant Settlement for high-volume domestic collections. Razorpay’s Instant Settlements provide fund access on your schedule, valuable during the overlap period when two gateways run simultaneously.<\/p>\n Switch your international payment gateway in six phases: (1) complete KYC\/KYB on the new gateway, (2) replicate purpose codes and compliance settings, (3) execute card vault transfer under RBI CoFT rules, (4) sandbox test all payment flows, (5) run a phased parallel rollout starting at 10 percent of international traffic, (6) keep the old gateway live for 60 days post-cutover to handle refunds and chargebacks before retiring it.<\/p>\n The sequencing matters more than the speed. Each phase de-risks the next, and the parallel run means live revenue is never exposed to a single point of failure.<\/p>\n You cannot simply copy card numbers. Doing so violates PCI-DSS Level 1 and RBI’s Card-on-File Tokenisation (CoFT) mandate.<\/p>\n The correct procedure is a secure vault-to-vault transfer from your old gateway’s bank partner to the new gateway’s bank partner. Card data travels encrypted and never touches your servers. The new gateway then issues new tokens mapped to your internal customer IDs.<\/p>\n For Shopify or WooCommerce, Razorpay’s plugins handle token migration via the platform’s payment method update flow. For custom API integrations, plan 2 to 3 developer days. Review the new RBI rules for processing auto-debits on cards<\/a> before you begin.<\/p>\n UPI AutoPay mandates are tied to the payment aggregator’s UPI handle and cannot be transferred. Every subscriber must re-authorise on the new gateway.<\/p>\n Do not set the retirement date until at least 90 percent of subscribers have re-authorised. See how e-mandates transform payments in India<\/a>.<\/p>\nDid You Know?<\/h3>\n
The PA-CB Regulatory Filter – Is Your Current Gateway Still Legal?<\/h3>\n
The Success Rate Gap – Failed International Transactions Are Quiet Revenue Bleed<\/h3>\n
Did You Know?<\/h3>\n
The 2026 Compliance Changes That Should Shape Your Migration Plan<\/h2>\n
What Changes on October 1, 2026<\/h3>\n
What Service Exporters Must Do Differently<\/h3>\n
Why Migration Timing Matters for In-Flight Receivables<\/h3>\n
Before You Start – The Pre-Migration Audit Checklist<\/h2>\n
Mapping Every Customer-Facing Payment Surface<\/h3>\n
\n
Auditing Your Recurring Billing Exposure – Cards Versus UPI AutoPay<\/h3>\n
Auditing Your FIRC\/e-FIRA Documentation Trail<\/h3>\n
Defining Your Settlement SLA Requirements Before You Commit<\/h3>\n
How to Switch Your International Payment Gateway Without Losing a Single Transaction – The 6-Phase Migration Plan<\/h2>\n
Phase 1 – KYC, Onboarding, and Compliance Configuration (Days 1 to 7)<\/h3>\n
\n
Phase 2 – Card Data and Tokenisation Migration Under RBI CoFT Rules (Days 5 to 14)<\/h3>\n
Phase 3 – UPI AutoPay Re-Mandate Campaign (Start Day 7, Complete Before Day 30)<\/h3>\n
\n
Phase 4 – Sandbox Testing – What to Test Before Going Live (Days 10 to 18)<\/h3>\n