PayPal in India for Foreign Merchants: What Works, What’s Restricted, and Better Alternatives
Learn what PayPal works for in India, what it restricts, and when global companies should use PA-CB rails instead.
Listen to article
Audio version (0% complete)
If you treat India as “just another card market”, you will systematically underestimate how much revenue you can unlock here.
UPI has become India’s default way to pay, with reports showing around 500 million users and tens of millions of merchants using it daily. At the same time, India’s cross‑border commerce is growing across SaaS, e‑commerce, digital content and B2B services, which makes “accept payments from India” a real product requirement for global companies, PSPs and fintechs.
PayPal is naturally one of the first tools founders think of. But PayPal’s India footprint has changed, it shut down its domestic payment gateway business in 2021 and now focuses only on cross‑border flows for Indian customers paying international merchants. That means “PayPal in India for foreign merchants” works well for a narrow slice of card‑using customers, but misses the UPI‑first majority and the RBI PA‑CB framework that now governs cross‑border aggregators.
This article walks through what PayPal can and can’t do for India inflows, where it is still “good enough”, and when you should add a PA‑CB‑licensed partner like EximPe alongside PayPal to build a serious India strategy.
How PayPal actually works for India today
In early 2021, PayPal announced that it would stop offering domestic payment services in India and instead focus entirely on enabling cross‑border payments. Practically, that means PayPal no longer acts as a local India payment gateway for Indian merchants collecting from Indian customers.
What remains is the cross‑border inbound flow: an Indian customer uses an international card to pay a foreign PayPal business account, typically in a foreign currency like USD, EUR or GBP. For you as a foreign merchant, money lands first in your PayPal balance, and then you withdraw it to your bank account at PayPal’s FX rate and fee schedule.
On the Indian side, this is still just a card transaction routed out of India, so it inherits all the RBI rules around two‑factor authentication, tokenisation and issuer risk checks that apply to other international card payments.
What PayPal can and can’t do for India inflows
At a high level, PayPal is a card‑only cross‑border channel for India, not a full India payments stack.
PayPal vs PA‑CB vs domestic India gateways (for India inflows)
PayPal can accept international cards from India and settle to you, but it cannot natively show UPI, netbanking or Indian wallets.
Conversion and compliance reality: card‑only vs UPI‑first India
The first big gap is coverage.
India has a relatively small base of active credit card users compared to its population, while UPI has grown to over 500 million users and processes the majority of retail digital transactions. If you rely on PayPal’s card‑only flow, you are only addressing customers who (a) have an international‑capable card and (b) are willing to use it for cross‑border online payments rather than UPI.
The second gap is friction and decline rates.
International card transactions routed from India go through 3‑D Secure, tokenisation and risk rules at issuing banks, which tends to increase declines and step‑up challenges compared to domestic UPI or domestic card flows. This isn’t a PayPal glitch, it is simply how India treats cross‑border card payments for consumer protection and risk control.
The third gap is compliance and documentation.
Cross‑border collections for export of goods and services fall under India’s foreign‑exchange law (FEMA) and related RBI regulations, which require proper purpose‑code tagging and export documentation like e‑FIRA/FIRC. RBI’s PA‑CB circular specifically brings entities that aggregate cross‑border import/export transactions under direct regulation, with net‑worth, reporting and operational standards similar to domestic payment aggregators. A PA‑CB‑licensed provider is designed to solve this documentation and routing problem.
When a PayPal‑only stack is still “good enough”
There are cases where you can reasonably stick to PayPal alone for India inflows.
If India is currently less than 1-2% of your revenue and you are not actively investing in the market, it may be rational to accept lower coverage in exchange for simplicity. For example, a US‑based niche SaaS tool that accidentally gets a handful of Indian customers each month might not justify a parallel PA‑CB integration yet.
PayPal‑only can also be acceptable when your specific buyers strongly prefer PayPal as a wallet, such as in certain cross‑border B2C marketplaces where PayPal is the primary trust layer. In those cases, even Indian customers who could pay via UPI may choose PayPal because of buyer protection and existing balances, so you’re not giving up as much coverage.
The trade‑off you should make explicit to your team is:
- Pros: One provider, familiar ops, no extra integration, globally consistent reporting.
- Cons: You systematically under‑serve UPI‑first Indian customers, accept higher friction on international cards, and don’t benefit from PA‑CB‑level documentation and rails.
Once India moves from the “nice to have” bucket to a strategic market, that trade‑off usually flips.
Why PA‑CB rails exist – and what they unlock
In 2023, RBI issued a circular that formally created the Payment Aggregator – Cross Border (PA‑CB) category and brought all cross‑border aggregators for import and export of goods and services under direct regulation. The idea was to replace a patchwork of older models (collection agents, OPGSPs) with a consistent framework that covers authorisation, net worth, KYC, settlement rules and reporting.
In simple terms, a PA‑CB is a regulated intermediary that:
- Collects money from Indian customers in INR through local payment methods like UPI, domestic cards and netbanking.
- Converts and settles export proceeds to the foreign merchant’s bank account in a permitted foreign currency, without the merchant needing an Indian legal entity for those collections.
- Tags each transaction with the correct purpose code under FEMA and generates the export documentation (e‑FIRA/FIRC) that Indian banks and regulators expect.
For a foreign merchant, this unlocks a few things that PayPal alone cannot:
- UPI payments from India for international merchants, plus netbanking and domestic card routing, all exposed at checkout in INR.
- No‑local‑entity India collections for eligible use cases, because the PA‑CB is the regulated entity facing Indian customers and banks.
- Cleaner FX and compliance flows, because PA‑CB rules are written with FEMA, LRS and export reporting in mind.
When to add a PA‑CB partner like EximPe alongside PayPal
For most serious India strategies, the right answer is not “PayPal vs PA‑CB” but “PayPal plus PA‑CB”.
The recommended pattern is:
- Keep PayPal (and any other global PSPs like Stripe or Adyen) for non‑Indian buyers, where PayPal’s wallet and card coverage are strong.
- Add a PA‑CB‑licensed partner such as EximPe specifically for Indian buyers, so they see UPI, netbanking and domestic cards in INR, while you still receive funds in your foreign bank account.
From a checkout point of view, you can:
- Detect India using the customer’s billing country or BIN country on the card, and route those sessions to the PA‑CB‑powered local checkout.
- Leave everyone else on your existing PayPal / global PSP flow so operations and reporting do not break.
In practice, this gives you PayPal’s strengths where they matter (trust and coverage in core markets) and PA‑CB’s advantages where India’s local rails and FEMA rules dominate.
Implementation patterns for global companies, PSPs and fintechs
1. Direct merchants (SaaS, e‑commerce, digital goods)
A US‑based design‑tools company selling subscriptions and templates globally might already use PayPal and another PSP for cards. To accept payments from India more effectively, they can:
- Implement country‑based routing: if billing country = India, send the customer to a PA‑CB‑powered checkout showing UPI, netbanking and domestic cards in INR, everyone else sees the existing PayPal/card flow.
- Receive settlements from the PA‑CB in USD or EUR into their existing bank, with e‑FIRA/FIRC handled by the PA‑CB and shared for their records.
For a EU‑based Shopify store shipping to Indian consumers, the pattern is similar but implemented at the storefront and payment app level: connect a PA‑CB‑integrated provider that can expose UPI to Indian customers while still settling cross‑border to the EU entity.
2. Global SaaS and subscriptions
A global CRM SaaS with customers in 50+ countries often wants to offer INR pricing and local payment methods while still billing and settling offshore. With a PA‑CB partner, the SaaS can:
- Offer UPI AutoPay and domestic card subscriptions to Indian customers, with mandates managed on India’s local rails but settlement flowing in foreign currency to their overseas account.
- Stay compliant with FEMA by ensuring each recurring payment carries the right purpose code and export documentation through the PA‑CB framework.
In parallel, the same SaaS can keep PayPal available globally for customers who prefer wallet‑based billing, especially in markets where PayPal adoption is high.
3. PSPs and fintech platforms
For PSPs, orchestration platforms or vertical fintechs, India is often a missing rail that their merchants request.
Instead of applying individually for PA‑CB authorisation, they can embed a PA‑CB partner and expose “accept payments from India” as a feature to their own merchants.
A European PSP, for instance, might:
- Use EximPe as its India PA‑CB partner behind the scenes, integrating once at the API level.
- Offer UPI, domestic cards and netbanking from India to its existing merchants, with settlements and reporting delivered through the PSP’s usual dashboard, while EximPe handles FEMA and PA‑CB compliance in the background.
This lets the PSP compete in RFPs where “India local methods” and “no local entity India collections” are check‑box requirements, without building local infrastructure itself.
Step‑by‑step migration blueprint: PayPal + EximPe stack
Here’s a simple 5‑step playbook you can discuss with your team.
- Scope your India use‑cases and volumes
- Segment India revenue (current and forecast) by product line: SaaS, e‑commerce, marketplaces, etc., and identify the payment methods your customers are asking for (UPI, local cards, netbanking).
- Select and onboard a PA‑CB partner
- Shortlist RBI‑authorised PA‑CB providers and confirm they are permitted for your type of exports (digital goods, SaaS, services).
- Complete KYC on your foreign entity and agree the settlement currency, payout schedule and documentation flows.
- Integrate and run sandbox tests
- Integrate the PA‑CB APIs or plugins and test UPI, domestic card and netbanking flows in INR from Indian test users.
- Validate end‑to‑end settlement into your foreign bank account and confirm how e‑FIRA/FIRC and purpose‑code reports are delivered.
- Implement smart routing between PayPal and PA‑CB
- Add a simple rule in your checkout or orchestration layer: if billing country (or BIN country) is India, route to PA‑CB checkout, otherwise, keep using PayPal/global PSP as before.
- Make sure price presentation and currencies are aligned (e.g., show INR for India and your base currency elsewhere).
- Go live and optimise
- Launch the dual setup and track India‑specific metrics: success rates, payment method mix, refund flows, chargebacks and operational overhead.
- Use this data to decide whether to expand PA‑CB coverage (more products, more India‑facing brands) and where PayPal‑only is still acceptable.
FAQs
Frequently Asked Questions
No. PayPal does not expose UPI, Indian netbanking or local wallets like PhonePe or Paytm at checkout for foreign merchants, it only supports international card payments from Indian customers into foreign PayPal accounts. To accept UPI payments from India for international merchants, you need a PA‑CB‑licensed provider or another gateway integrated with UPI rails.
If you use a domestic India gateway, you typically need an Indian entity and a local INR bank account, because settlement happens to that domestic account. Under RBI’s PA‑CB framework, however, authorised cross‑border aggregators can collect from Indian customers in INR and settle export proceeds in foreign currency to eligible foreign entities without those entities incorporating in India, for permitted transactions. PayPal also settles cross‑border proceeds to foreign accounts, but it does so as a card‑only wallet rather than as a PA‑CB that exposes UPI and netbanking.
PayPal acts as a global wallet and card processor: Indian customers use international cards, money lands in your PayPal balance, and you withdraw it at PayPal’s FX rate. A PA‑CB‑licensed provider is a regulated India‑facing aggregator that can accept UPI, domestic cards and netbanking in INR, tag transactions with FEMA purpose codes, generate e‑FIRA/FIRC, and settle export proceeds directly to your foreign bank account. In practice, most serious India strategies combine both: PayPal for global wallet‑driven flows, PA‑CB for UPI‑first India collections.
When Indian customers pay foreign merchants, banks and regulators expect evidence that export proceeds were received in line with FEMA rules, which is documented via instruments like e‑FIRA/FIRC. PA‑CB‑licensed providers are designed to integrate this documentation into their flows, so your finance team gets export proof along with settlements, rather than having to chase individual banks and intermediaries.