Stripe for India: What Works, What Doesn’t, and Where Global Merchants Lose Indian Customers

If you already run your global stack on Stripe, India looks deceptively simple: turn on international cards, maybe UPI, and you’re done.

In reality, India is now a UPI‑first market running on RBI‑specific rules and a new cross‑border regime (PA‑CB) that Stripe was never designed around.

This article is for teams who trust Stripe globally, but are now looking at India seriously - SaaS founders, marketplaces, PSPs, and fintech infrastructure players who want to accept payments from India without setting up an Indian entity.

India’s payment reality: UPI‑first, cards‑second

Over the last five years, UPI has become the default way India pays.
RBI data shows UPI now handles roughly 80-84% of all retail digital payment transactions by volume, with more than 180+ billion transactions processed in FY25 alone.

UPI’s rise is staggering: RBI reports its share of total digital payments jumped from about one‑third in 2019 to more than 80% by 2024-25, with transaction volumes and values compounding at over 80% annually.
As UPI’s share has exploded, the relative share of cards and other instruments in India’s retail digital payments has steadily shrunk.

For a foreign merchant, the punchline is simple: a card‑only checkout speaks to a shrinking slice of how Indians actually pay, even if card numbers themselves are growing.

How Stripe handles Indian customers today

Stripe still plays a very important role in this picture.
Stripe lets many non‑Indian entities accept payments from Indian customers using international cards, and in some configurations UPI, through primitives like Checkout and Elements.

From a foreign merchant’s perspective:

• Your Stripe account location (US, EU, SG, etc.) determines what payment methods you can enable.
• Indian customers can often pay you with international Visa, Mastercard and Amex cards issued in India, charged in the currency of your Stripe account.
• Stripe’s UPI docs focus on merchant support and UPI terms, but Stripe is not described as a Payment Aggregator - Cross Border (PA‑CB) and does not claim to automate e‑FIRA or FEMA export documentation.

So Stripe is still your global “card + wallet + some local methods” backbone, great for consistency, fraud tooling, and reporting across markets.

The hidden friction: RBI 2FA, tokenisation and cross‑border risk

Now to the part that most dashboards don’t tell you: why Indian card payments quietly underperform.

RBI’s 2‑factor rules

RBI mandates two‑factor authentication for digital payments, and regulators have been tightening rules to ensure strong customer authentication across cards and other instruments.

For international card transactions, this often means extra OTP steps, issuer risk checks, and stricter fraud controls, which introduce friction into checkout flows that look “simple” from your Stripe logs.

Card tokenisation

In parallel, RBI’s card‑on‑file tokenisation framework prohibits merchants and gateways from storing full card numbers, requiring tokenised credentials for each merchant-card combination.

Banks and payment gateways like Razorpay highlight that this is essential for security, but it complicates one‑click experiences and recurring billing unless the whole stack is tuned to India’s rules.

What this means for you

Put together, Indian‑issued cards on international rails tend to see higher decline rates and more drop‑offs than domestic UPI or card transactions routed on Indian infrastructure.

If you are only watching top‑line “card success” globally, it’s easy to miss how much India‑specific revenue dies in 2FA loops and issuer declines.

RBI’s PA‑CB framework in plain English

To bring order to cross‑border collections, RBI created a specific category: Payment Aggregator - Cross Border (PA‑CB).

In simple terms:

• PA‑CB rules apply to entities that aggregate cross‑border payments for import and export of goods and services, exactly what you do when you sell from abroad into India.
• The 2023 circular formalises this activity and replaces older patchwork regimes like OPGSP (online payment gateway service providers) and “collection agents,” forcing anyone doing this at scale into the PA‑CB framework.
• PA‑CB licensees must meet net‑worth thresholds, AML and KYC obligations, FIU‑IND registration, reporting, and purpose‑code classification, and are capped on transaction sizes per unit sale.

What this means for you as a foreign merchant:

• There is now a clear RBI‑recognised category of aggregators who can collect from Indian customers and settle abroad.
• Working with a PA‑CB‑licensed provider gives your finance and compliance teams a clean story: this is regulated cross‑border collection, not a grey‑area workaround.

EximPe’s role: UPI‑first, PA‑CB‑licensed, no Indian entity

EximPe sits squarely in this new category.
In early 2026, EximPe received final RBI authorisation as a Payment Aggregator - Cross Border, allowing it to directly operate under the PA‑CB framework.

Practically, that means EximPe can:

• Let global merchants, PSPs and fintechs accept UPI, NetBanking, wallets, cards and bank transfers from Indian customers under RBI’s PA‑CB rules.
• Settle funds to offshore accounts in 30+ currencies within roughly 24-48 hours, much faster than typical SWIFT collections.
• Do all this with no Indian company, bank account or GST registration required for the foreign merchant.
• Automatically generate FEMA‑compliant e‑FIRA and purpose‑code documentation for every eligible export-import transaction, keeping your finance and compliance teams audit‑ready.

EximPe’s own PA‑CB explainer frames it as “India’s gateway for cross‑border payments,” emphasising that it is built for international businesses who want to accept INR from India without going local first.

Stripe‑only vs Stripe + EximPe: what actually changes?

Here’s the core strategic choice.
You don’t have to replace Stripe; the winning pattern for serious India GMV is Stripe for global, EximPe for India‑local rails under PA‑CB.

High‑level comparison

The operational feel is:

• Stripe remains your global orchestration layer.
• EximPe becomes your India‑specific rail that speaks the language of UPI, PA‑CB and FEMA to RBI and to your finance team.

When Stripe alone is actually enough

Stripe‑only is a rational choice when:

• India is <5% of GMV and you’re still validating market fit rather than optimising payments.
• Your Indian customers already pay fairly reliably with international cards or wallet‑backed cards, and support tickets about “UPI / NetBanking not available” are rare.
• Your finance team doesn’t yet need fine‑grained FEMA documentation because India is not a material export corridor.

In that phase, over‑engineering India, adding a new PSP, integration, and dashboards - can distract the team from core product work.
Treat Stripe as your MVP rail for India, accept its limitations, and revisit once the numbers justify it.

When you should add EximPe alongside Stripe

At some point, India stops being “nice‑to‑have” and becomes a serious line on the P&L.

Typical trigger conditions:

• India crosses 5-10% of global GMV or is clearly strategic for the next growth phase.
• Sales and support keep hearing the same questions: “Do you support UPI?” or “Can I pay via NetBanking?”
• Your data shows materially higher decline or drop‑off rates for Indian cardholders versus domestic benchmarks or other regions.
• Your bank, auditors or investors start asking: “Are these India collections FEMA‑compliant, and do we have e‑FIRA and purpose codes in place?”

The pattern that works in practice:

• Keep Stripe as your primary PSP for cards, wallets, SEPA, ACH and non‑India markets.
• Add EximPe as the India rail: route Indian buyers to UPI, NetBanking, wallets and domestically routed cards, with settlement to your offshore account and full PA‑CB compliance.

The customer still sees one checkout.
Under the hood, you’re running two PSPs behind a single abstraction, chosen by billing country or payment method.

Integration walkthrough: how Stripe teams plug in EximPe

Here’s how this usually looks from an engineering and ops perspective.

1. KYC and onboarding (foreign entity)
   EximPe onboards your non‑resident company under RBI PA‑CB rules; no Indian company or bank account is required.
2. Sandbox keys and test flows
   You receive sandbox credentials and run test UPI, NetBanking and card flows in INR, confirming callback and webhook behaviour with your existing systems.
3. Wiring EximPe into your checkout
   Your team integrates EximPe’s SDK or REST API alongside Stripe: either
   • route based on billing country = IN, or
   • show EximPe methods when a buyer selects UPI / NetBanking / wallets at checkout.
4. Live low‑value transactions
   You process small real transactions (often ₹1-₹100 equivalent) to:
   • confirm T+0, T+1/T+2 settlements landing in your offshore bank account, and
   • Verify that e‑FIRA and purpose‑code documentation are generated correctly.
5. Go‑live and steady‑state operations
   Once flows are stable, you:
   • keep using your Stripe dashboard for global reporting, and
   • use the EximPe dashboard for India‑specific settlements, UPI performance and FEMA documentation.

From a developer’s perspective, this is one more PSP integration.
From a CFO’s perspective, it’s the difference between “India revenue” and “India‑compliant, audit‑ready revenue.”

Use cases: SaaS, marketplaces and PSPs

Let’s make this concrete with two scenarios that will feel familiar.

Global SaaS selling into India

A US‑based SaaS sells subscriptions to Indian SMEs.
On Stripe‑only, Indian card payments work but show noticeably higher declines and churn, and customers keep asking for UPI.

After plugging in EximPe:

• New sign‑ups from India default to UPI and NetBanking, with cards as a fallback.
• Recurring collections can move to UPI mandates or domestic card routes where applicable.
• Finance gets automatic e‑FIRA for export receipts, making India revenue easier to explain to auditors.

Marketplaces and PSPs

A global marketplace or PSP already relies on Stripe Connect for most countries.
India, however, sits in a grey zone between local payment expectations and cross‑border regulation.

By adding EximPe under PA‑CB:

• The marketplace can offer its sellers UPI and other local payment options for Indian buyers.
• Collections are settled offshore in the marketplace’s chosen currency, while still staying within RBI’s PA‑CB norms.

B2B exporters

A European manufacturer exporting to Indian distributors previously relied on slow SWIFT transfers.

With EximPe:

• Buyers can pay using UPI or NetBanking in INR.
• The exporter receives funds in EUR with T+0, T+1/T+2 settlement and full FEMA documentation per transaction.

In all three cases, Stripe remains intact for the rest of the world; EximPe just unlocks India properly.

FAQs