India's Unified Payments Interface has become one of the most-discussed payment rail stories in global fintech — with good reason. NPCI reported UPI transaction volumes exceeding 13 billion transactions per month in the second half of 2024, making it by transaction count the world's most active real-time retail payment network. But understanding UPI's relevance for cross-border B2B operators requires separating the domestic retail story from the more specific and technically constrained question of international settlement.
This article is written for cross-border payment infrastructure operators and treasury teams — not consumer payment enthusiasts. The question we are addressing is operational: how does UPI function as a B2B settlement rail for inbound cross-border payments, where are its genuine capabilities, and where does correspondent banking remain the more appropriate path?
UPI's Domestic Architecture
UPI operates as an overlay on India's Immediate Payment Service (IMPS) infrastructure, itself built on the National Financial Switch managed by NPCI. Every UPI transaction is ultimately settled across participants' accounts held at the RBI — each UPI member bank maintains a settlement account, and net positions are cleared in the RBI's National Electronic Clearing Service (NECS) overnight, with intraday positions settled via RTGS.
The UPI address layer — VPAs like example@okicici or name@ybl — is a directory abstraction. A VPA maps to an underlying bank account at a UPI-member bank. When a payment is initiated to a VPA, the UPI platform resolves the VPA to the underlying account details, issues an inter-bank credit instruction via IMPS, and the credit appears in the beneficiary's account within seconds.
Transaction limits as of late 2024: standard UPI transactions are capped at INR 1 lakh (approximately SGD 1,600) per transaction. UPI 123PAY and UPI Lite have different limits. UPI for business payments (B2B UPI) operates under separate limit configurations that allow higher per-transaction amounts for approved merchant categories — in practice, this is most relevant for the UPI AutoPay and UPI for recurring B2B collections use cases.
Cross-Border UPI: The International Settlement Framework
NPCI International Payments Limited (NIPL) was established to manage UPI's international expansion. The framework for inbound international payments using UPI works through bilateral arrangements between NPCI International and payment operators in originating countries.
Singapore is one of the most advanced integration points: MAS and NPCI signed a real-time payment linkage enabling Singapore PayNow transfers to credit Indian UPI VPAs directly, and vice versa. This PayNow-UPI linkage is operational for person-to-person transfers with transaction limits currently set at SGD 1,000 per transfer (SGD 3,000 per day).
For B2B operators, the relevant capability is slightly different. A cross-border payment service provider with bilateral settlement arrangements with an Indian Authorized Dealer bank can route inbound SGD (or USD) to credit a UPI-linked bank account in India via IMPS. The flow: originating currency arrives at the AD bank's settlement account → AD bank converts to INR at its transactional rate → IMPS or UPI credit is issued to the beneficiary VPA or bank account. This works today, it is compliant under the RBI's current framework, and it produces credits within the same business day in most cases.
What this is not: a direct SWIFT-to-UPI translation where international wire messages automatically route to UPI addresses. The AD bank intermediary step is required by RBI regulation and cannot be bypassed. Any operator claiming to offer direct international-to-UPI settlement without an AD bank in the chain is either misstating the architecture or operating outside the RBI framework.
UPI Limitations for Large B2B Transactions
The per-transaction limits on standard UPI make it unsuitable as a standalone settlement rail for large B2B invoice payments. A INR 25 lakh supplier payment, for example, cannot be settled via a single UPI transaction — it either requires batch UPI credits (operational overhead, higher error risk) or routing via NEFT (same-day batch clearing, no cap) or RTGS (real-time, above INR 2 lakh, no cap).
For cross-border B2B operators, the practical segmentation is roughly this: payments below INR 1 lakh can route via UPI/IMPS for maximum speed; payments between INR 1–5 lakh are better served by IMPS (which has higher per-transaction limits than UPI in B2B configurations); and payments above INR 5 lakh should route via NEFT or RTGS depending on whether same-day finality within RBI operating hours is required.
A Singapore-based digital agency with 12 freelance developers in Bengaluru and Hyderabad found that monthly developer payments in the INR 40,000–80,000 range settled via UPI/IMPS in 15–45 minutes after instruction, compared to 2–3 day SWIFT settlement previously. For the agency's payroll cycle, which required all 12 payments to settle before month-end without ambiguity on settlement date, the predictability improvement was the key benefit — not just the speed.
UPI Merchant Payments and the B2B Receivables Use Case
UPI is not only a disbursement rail — it is increasingly relevant as a collections rail for B2B receivables. Indian businesses accepting payment from Indian counterparties routinely use UPI QR codes and VPA-based payment requests. The question for a Singapore-incorporated company with Indian business clients is whether UPI-based collections — where the Indian client pays via UPI to a VPA that ultimately settles to the Singapore entity — are operationally feasible.
The answer is technically yes, with structure. The Singapore entity would need to open an Indian bank account (as a foreign-owned entity, this requires compliance with RBI guidelines on bank account types for non-resident entities) and designate a VPA for that account. Alternatively, a payment service provider can hold a pooled merchant settlement account in India and remit net collections outward to Singapore on a periodic basis, compliant with RBI's master circular on export of services.
We are not saying this is simple to set up — the regulatory structure for a foreign company collecting INR in India is genuinely more complex than purely outbound disbursement. But for Singapore companies with recurring INR receivables, the UPI collections route eliminates the UPI-user friction of asking Indian clients to initiate international wire transfers, which many smaller Indian businesses find burdensome.
What Cross-Border UPI Cannot Replace
RTGS settlement finality, RBI-regulated FEMA purpose coding, the Authorized Dealer bank's documentary compliance role, and the correspondent banking relationships required for very large transactions (above INR 2 crore, approximately USD 240,000) remain part of the India corridor infrastructure regardless of UPI's growth. UPI extends accessibility and reduces latency for the high-volume, lower-value portion of the B2B transaction spectrum. It does not replace the regulatory and settlement architecture for high-value, documentation-intensive transactions.
Cross-border payment operators building on the India corridor need both a fast rail for smaller recurring transactions (where UPI/IMPS is the right tool) and a RTGS/NEFT path for large batch and high-value flows. A single-rail strategy on either side — all SWIFT, or all UPI — is operationally suboptimal for the full range of B2B use cases the India corridor presents.
NPCI's international expansion continues: as of 2024, UPI cross-border payments are available in multiple markets including the UAE, France, and Singapore. The trajectory points toward broader international settlement reach, but each country integration involves bilateral regulatory arrangements that take time. For treasury teams building India payment strategies today, the framework described above reflects the operational reality on the corridor and will remain accurate for the foreseeable horizon.