How SaaS Companies Can Accept UPI Payments in India Without a Local Entity

India has become one of the fastest-growing markets for global software and UPI is no longer just another payment method. It has become the default way millions of Indian consumers expect to pay for digital services. Yet many SaaS companies hit the same friction the moment they try to charge Indian customers: their checkout supports cards and wallets from everywhere else, but not UPI.

The standard fix – "just set up an Indian entity" – is exactly the six-month, lawyer-heavy detour a growing SaaS business wants to avoid. The good news is that accepting UPI payments in India no longer requires a local subsidiary. The regulatory and operational plumbing now exists for a foreign SaaS company to collect UPI, stay compliant with Indian tax law, and settle funds abroad without incorporating in India at all. Here's how it works.

Why UPI is different from a card

UPI (Unified Payments Interface) is built and governed by the National Payments Corporation of India (NPCI). Unlike an international card network, UPI is a domestic real-time rails system: money moves in rupees, from an Indian bank account to an Indian bank account, instantly.

That last point is the sticking point for foreign SaaS. To receive UPI directly, a merchant generally needs an Indian bank account and a relationship with an Indian acquiring bank or aggregator. A foreign company accepting UPI with no Indian entity, no local bank account, and no local banking relationship simply cannot plug into the network on its own. The technology is open; the settlement layer is not.

So the real question isn't "can my checkout show a UPI button?" It's "who legally collects the rupees, and how do they reach me overseas?"

Two compliance layers, not one

Founders often treat UPI payments for SaaS as a single problem. It's actually two, governed by two different regulators.

1. The payment layer – RBI. Collecting money from Indian customers and moving it out of the country is regulated by the Reserve Bank of India. For years this was a grey area for cross-border UPI payments. The RBI closed the gap with its Payment Aggregator – Cross Border (PA-CB) framework, introduced in an October 2023 circular and since consolidated into the RBI's Master Direction on Payment Aggregators issued in September 2025. Under this framework, RBI-authorised PA-CB entities can onboard overseas merchants, collect domestic payments including UPI from Indian buyers, and settle the proceeds to the merchant abroad in foreign currency. The merchant does not need an Indian entity – the licensed aggregator carries the local regulatory relationship. By early 2026, the RBI had authorised only a small set of entities to operate this way.

2. The tax layer – GST / OIDAR. Selling software to Indian users is a taxable event. Foreign digital services fall under India's OIDAR rules (Online Information Database Access and Retrieval), which classify most SaaS as taxable at 18% IGST. 

Since October 2023, the exemptions that once shielded foreign providers are gone: a foreign SaaS company selling to individual (B2C) customers in India must register for GST, charge 18%, and file returns – regardless of turnover, from the very first customer. 

When the customer is a GST-registered business (B2B), the reverse-charge mechanism usually shifts that liability to the buyer, but the classification and invoicing still have to be handled correctly.

Get the payment layer right and ignore the tax layer, and you have a compliance problem waiting to surface. This is why "just add a UPI button" is never the whole story.

Option A: Build it yourself

You can solve both layers directly. In practice, going it alone means you'll likely need to:

• Establish an Indian entity or appoint a local authorised representative
• Open local banking relationships
• Register for GST as an OIDAR supplier
• Integrate with a domestic payment provider
• Manage recurring tax filings such as GSTR-5A
• Stay current with evolving RBI and GST rules

It's a legitimate path and the right one for companies with serious India headcount or long-term local ambitions. For most SaaS teams, though, it's a disproportionate amount of overhead to unlock one payment method in one market. The entity setup alone can take months, and the compliance obligations never really end.

Option B: The Merchant of Record model

The faster path is to not be the legal seller at all.

Under a Merchant of Record (MoR) model, a third party becomes the entity that officially sells your subscription to the Indian customer. The MoR is the name on the invoice, the party responsible for collecting and remitting local tax, and the entity that holds the local payment relationships. You remain the software provider; the MoR is the seller of record.

Because the MoR is already established in India –with the banking relationships, the aggregator integrations, and the tax registrations – it can offer UPI at checkout on your behalf, collect the rupees domestically, handle the 18% GST, and settle your revenue to you abroad. Your customer taps a UPI app and pays in seconds. You receive clean, converted funds and never touch an Indian bank account or a GST portal.

A quick example

Picture a US-based AI writing platform with paying customers in Bengaluru and Mumbai. Instead of forcing them onto an international card – which many will abandon – it shows UPI at checkout. The customer pays instantly with Google Pay or PhonePe, in rupees, while the Merchant of Record collects the payment, applies the 18% GST, and settles the revenue to the platform's US account. The SaaS company never opens an Indian entity, and the customer never sees the machinery.

Build yourself vs. Merchant of Record

How Merchant of Record providers simplify UPI acceptance

For a foreign company accepting UPI, an MoR turns the India question from a legal project into a configuration step. Merchant of Record providers such as Transact Bridge enable SaaS companies to accept UPI without establishing an Indian entity – handling payment collection, GST compliance, invoicing, and settlement abroad through a single integration that also supports payments across India, US and global markets. Readers who want the product detail can follow through from there; the point for this article is that the capability now exists off the shelf.

What to check before you choose a partner

Not every provider handles Merchant of Record India obligations the way a SaaS subscription business needs. Before committing, confirm the partner:

• Supports UPI and domestic Indian payment methods
• Takes on Merchant of Record responsibilities (GST liability sits with them, not you)
• Manages GST registration and filings
•  Supports recurring billing, including UPI Autopay mandates
• Handles both B2C and B2B invoicing, including reverse charge
• Settles funds to you internationally

The takeaway

For most SaaS companies, expanding into India is no longer limited by payments. UPI has become the way millions of Indian consumers expect to pay, and the infrastructure to accept it from abroad is already in place. The real decision is whether to build local infrastructure yourself or use a Merchant of Record that already has it – the RBI relationships, the GST registrations, and the settlement rails included.

FAQ

Can a foreign SaaS company accept UPI without an Indian entity? Yes. Foreign SaaS companies can accept UPI without incorporating in India by working with a Merchant of Record or another RBI-compliant cross-border payment partner that handles local collection and settlement. Platforms such as Transact Bridge provide this capability.

Who pays the 18% GST on Indian SaaS sales? For B2C sales, the foreign provider – or its Merchant of Record – is responsible for charging and remitting 18% IGST under India's OIDAR rules. For GST-registered business buyers, the reverse-charge mechanism shifts that liability to the customer.

Does UPI for international businesses only work for India? UPI itself is India-specific, but the Merchant of Record model isn't. The same partner that unlocks UPI can typically consolidate your international card and local-method acceptance elsewhere under a single integration.