What it is
UPI is a payment rail, not a wallet and not a payment provider. It moves money from one Indian bank account to another using a mobile number or a virtual payment address instead of card or account numbers. NPCI, the National Payments Corporation of India, operates the rail and sets its rules. The apps shoppers know, such as Google Pay, PhonePe and Paytm, are front ends that ride on top of it. That distinction matters for merchants. You cannot open a UPI merchant account with NPCI the way you open a gateway account. You get access through an Indian bank, a licensed payment aggregator, or a cross-border PSP that already holds that access. Once connected, you collect through a UPI ID or a dynamic QR code, and the buyer approves the debit inside their own app with a PIN.
- UPI is an account-to-account rail operated by NPCI, not a wallet that stores customer balances.
- Google Pay, PhonePe and Paytm are apps that use UPI rather than separate payment rails.
- Merchants connect through a bank, payment aggregator or PSP, not directly through NPCI.
- UPI payments use VPAs, mobile numbers, QR codes and app approval rather than card numbers.
Where it is used
UPI is an India-only rail and it settles in Indian rupees. There is no cross-border version of the scheme that a foreign merchant can join for domestic Indian collections, so every UPI payment you take is a domestic INR transaction that happens inside India. On the buyer side, reach is the whole point. Hundreds of millions of Indians with a bank account and a smartphone can pay this way, and most of them already use it for groceries, transport, bills and online orders. For a merchant, UPI is the default expectation at Indian checkout, not a nice-to-have alternative to cards. When Indian customers reach a checkout page without it, a large share of them simply leave and buy somewhere else.
- UPI operates only in India and settles only in Indian rupees.
- Reach extends well beyond cardholders, because a bank account and a phone number are enough to pay.
- Indian shoppers treat UPI as the default checkout option across e-commerce, bills and in-store QR codes.
- Adding UPI is usually about avoiding abandonment rather than opening a brand new customer segment.
Which businesses it suits
UPI fits merchants selling to Indian consumers at low to medium ticket sizes, where app-based bank payment matters more than credit. E-commerce, app stores and digital content, subscription services, food delivery, gaming, travel bookings and repeat bill-style payments can all work when provider access is approved. It also suits businesses that need quick provider confirmation before releasing a digital good, but the exact paid-state timing must be tested with the PSP. It suits you less if your model depends on instalments, since that is a card feature rather than a UPI one. It is also a poor fit when you need funds to arrive directly in a foreign bank account in your own currency, or when your average order value runs above the per-transaction limits that NPCI and the banks apply.
- UPI suits consumer e-commerce, digital goods, subscriptions, gaming and delivery at low to medium ticket sizes.
- Instant confirmation makes it practical for pay-and-unlock digital delivery.
- It does not support instalments, so card rails remain necessary for that use case.
- Per-transaction limits make UPI awkward for very large single payments.
How merchants usually connect
There are two broad routes to evaluate. Indian-registered businesses may be able to work with a bank or licensed payment aggregator that handles onboarding, UPI IDs or QR codes, settlement reporting, and risk review. Foreign-registered businesses should not assume direct UPI access; they usually need to verify whether a cross-border PSP, receivables provider, or Indian partner can support their entity, vertical, documentation, settlement currency, and repatriation needs. Ask who is merchant of record, who owns disputes, which account receives settlement, and which UPI flows are actually enabled before integration.
- Indian entities may be able to use banks or licensed payment aggregators, subject to approval and documentation.
- Foreign entities should verify cross-border PSP, receivables, or partner routes rather than assuming direct UPI access.
- Confirm entity, bank-account, settlement, repatriation, and merchant-of-record responsibilities in writing.
- Ask which UPI flows are enabled for your industry and what transaction limits apply.
- Separate generic UPI support from approval for your specific account.
Cross-border merchant notes
Selling into India without an Indian entity changes three things. First, UPI funds land in rupees in an Indian account held by your partner, not in your home bank, so somebody has to convert and move them out. That repatriation runs through Reserve Bank of India regulated channels, and it carries FX cost, documentation and timing you should model before launch. Second, the contracting party is usually the local aggregator or PSP, so your commercial terms, refund duties and data handling follow their framework rather than yours. Third, UPI acceptance abroad for Indian travellers is a separate and narrow programme, and it does not give a foreign merchant the right to collect from Indian residents. Check the current RBI position with your partner before you commit.
- UPI funds settle in rupees inside India, and moving them out runs through RBI-regulated repatriation with FX cost.
- Your contract, refund duties and data handling usually follow the local partner's framework.
- UPI acceptance abroad for Indian travellers is a narrow programme, not a route to collect from Indian residents.
- Confirm the current RBI position with your partner before signing anything long term.
Fees, settlement and refunds
Public pricing is only a first filter. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live. Do not treat rail-level payment confirmation as your payout calendar: your bank, aggregator, PSP, or cross-border receivables provider controls settlement schedule, payout currency, reserves, FX, failed-payout handling, refunds, disputes, and reconciliation files. UPI does not follow card chargeback mechanics, but complaints, reversals, and fraud processes still need operating rules.
- Treat published pricing as screening information only.
- Ask for payout timing, settlement currency, reserves, FX, and failed-payout rules in writing.
- Confirm refund and complaint handling before launch.
- Keep order records and delivery evidence even when the flow is not card-based.
- Model provider fees and operational handling rather than assuming UPI is cheapest for your account.
Alternatives and complements
Most merchants should treat UPI as the base layer and add around it. PhonePe and Paytm are worth naming in your own planning because they are the apps a large share of your buyers will open, and coverage through your PSP should include them by default. Cards still matter for instalments, for higher ticket sizes and for buyers who prefer credit, so a local card acquiring option complements UPI rather than competing with it. Netbanking and direct bank transfer remain useful for corporate and high-value orders that sit above UPI limits. If you sell in several markets, a PSP with regional coverage lets you keep one integration while UPI handles the Indian leg of the business.
- Keep UPI as the base rail and confirm your PSP also covers the PhonePe and Paytm app flows.
- Add local card acquiring for instalments, credit-preferring buyers and higher ticket sizes.
- Offer netbanking or bank transfer for corporate orders and amounts above UPI limits.
- A multi-market PSP lets you run one integration while UPI handles India.
Questions to ask before you integrate
The questions that change your economics are rarely in the sales deck. Ask whether you will be onboarded as a direct merchant or as a sub-merchant, and who holds the merchant category and the dispute liability. Ask for the exact settlement currency, the settlement cut-off times, and how many days sit between capture and funds being available to you. Ask how refunds are initiated, what they cost, and how long the customer waits. Ask about per-transaction and daily limits, and what the buyer experience is when they are exceeded. Ask what happens to your funds if your industry is reclassified as higher risk. Finally, ask whether the integration supports mandates or auto-pay if you run subscriptions, because that is a separate capability.
- Will you onboard as a direct merchant or a sub-merchant, and who carries dispute liability?
- What is the settlement currency, the cut-off time, and the real delay before funds are usable?
- How are refunds initiated, what do they cost, and how long does the customer wait?
- What per-transaction and daily limits apply, and what happens when a buyer hits them?
- Does the integration support UPI AutoPay mandates for recurring billing?
Questions merchants ask
Is UPI free for merchants?
Any figure you see online is a first filter, not a quote. Final pricing depends on country, industry, volume, settlement currency, integration method, provider model, and contract terms. Ask for a written quote that includes transaction fees, settlement, payout, FX, refunds, disputes, reserves, and reconciliation costs before launch.
Can a foreign company accept UPI payments from Indian customers?
Possibly, but do not assume direct access. A foreign entity needs a provider route that can support the merchant entity, product category, documentation, settlement, payout currency, foreign-exchange requirements, refunds, disputes, and risk review. Confirm the exact route and obligations with the PSP or receivables provider before committing to a launch date.
How fast does UPI settlement reach my account?
UPI can confirm the customer payment quickly inside the rail, but settlement into your merchant account follows the schedule set by your bank, aggregator or PSP. Weekends, bank holidays, risk checks, reserves and your contracting route can shift timing, so get cut-off times and payout cadence in writing before you launch.
Does UPI have chargebacks like cards do?
UPI has no card-style chargeback, because the buyer authorises and pushes the payment with a PIN. It does run a fraud and grievance process through NPCI and the banks, so disputed transactions still need attention. Keep order records, delivery proof and refund logs, and agree with your provider who handles customer complaints and how quickly they must respond.
What do I need to start accepting UPI?
You need a route to the rail, which means an Indian bank, a licensed payment aggregator, or a cross-border PSP that onboards you as a sub-merchant. Expect company registration documents, beneficial owner identification, a review of your website and product, and an Indian bank account or partner account for settlement. Sandbox testing comes before go-live.
Do I need separate integrations for PhonePe, Google Pay and Paytm?
Usually not. Those are apps that run on the UPI rail, so a single UPI integration through your bank, aggregator or PSP generally covers all of them, and the buyer picks their own app to authorise the payment. Ask your provider to confirm which app flows are tested and live, and whether both dynamic QR codes and collect requests are supported.