To accept UPI payments in your app or website, you integrate a payment aggregator (Razorpay, Cashfree, PhonePe Payment Gateway, or Paytm) that handles UPI collect requests, intent flows, and QR payments through NPCI's network — or, at larger scale, you work with a bank to become a merchant on UPI directly. For most Indian businesses, aggregator integration takes 1–3 weeks of development, costs ₹25,000–₹1,50,000 in engineering effort, and carries transaction fees of 0%–2% depending on instrument. This guide explains the flows, the costs, the compliance, and the engineering details that separate a smooth checkout from a support nightmare.
Why UPI is non-negotiable for Indian businesses in 2026
UPI processes well over 15 billion transactions a month, and for consumer-facing businesses it is now 70–85% of digital payment volume. Cards are a minority instrument outside premium segments; wallets have faded. If your checkout does not lead with UPI, you are adding friction for the majority of your customers — and friction at payment is where conversion dies.
The strategic reason runs deeper: UPI's cost structure. Person-to-merchant UPI transactions below ₹2,000 on basic UPI carry zero MDR under current government policy, and even where charges apply they undercut card fees substantially. For a business doing ₹50 lakh a month in collections, the difference between 2% card MDR and near-zero UPI fees is ₹1 lakh a month straight back into margin.
The four UPI integration flows — and when to use each
1. UPI Intent (mobile apps and mobile web). The user taps "Pay", their installed UPI app (GPay, PhonePe, Paytm, BHIM) opens with amount and merchant pre-filled, they authorise with their PIN, and control returns to your app. Highest success rates on mobile — this should be your default.
2. Collect request. The user enters their UPI ID (VPA), and a payment request appears in their UPI app. Success rates are lower because users mistype VPAs and requests expire unnoticed. Offer it as a fallback, never the primary flow.
3. Dynamic QR (desktop web and in-person). Your checkout renders a QR carrying a unique transaction reference; the customer scans with any UPI app. Essential for desktop checkouts and for counter billing — the same mechanism behind the soundbox on every kirana counter.
4. UPI Autopay (recurring mandates). The customer approves a mandate once; you debit on schedule. This is the rail for subscriptions, SaaS billing, school fees, gym memberships, and EMI collection. Mandates up to ₹15,000 execute without per-debit authentication (limits are higher for specific categories like insurance and mutual funds — verify current NPCI circulars). For lending businesses running on platforms like LoanKard, Autopay mandates alongside eNACH are what make collections predictable.
What does UPI integration cost?
| Item | Typical cost (2026, INR) | Notes |
|---|---|---|
| Aggregator onboarding | ₹0 (KYC + agreement) | 2–7 days with clean documents |
| UPI transaction fees | 0% on basic UPI P2M; 1.5–2% on credit-card-on-UPI | Confirm current slab with your aggregator |
| Basic website checkout integration | ₹25,000–₹60,000 | Hosted checkout, webhooks, receipts |
| Mobile app integration (intent + status handling) | ₹50,000–₹1,20,000 | Android + iOS |
| UPI Autopay / mandate flows | ₹60,000–₹1,50,000 | Mandate lifecycle + retry logic |
| Full billing system with reconciliation | ₹1,50,000–₹5,00,000 | Ledger, settlements, GST invoicing |
These are realistic Indian-market engineering rates; get a tailored estimate from our project cost calculator. The recurring cost to watch is not fees but reconciliation labour — which good engineering eliminates, as covered below.
Aggregator vs direct bank integration: which route should you take?
Choose an aggregator (Razorpay, Cashfree, PhonePe PG, Paytm PG) if you are almost anyone. One API gives you UPI plus cards, netbanking, and EMI; onboarding is days; dashboards, refunds, and settlement reports come built in. Under RBI's payment aggregator licensing regime, stick to licensed PAs — the shakeout of unlicensed players is done, and the survivors are stable.
Consider direct bank/NPCI integration only at serious scale (several crore a month in volume) where basis points matter, or where you need flows aggregators do not expose. It brings bank-grade audits, certification cycles, and months of timeline. Most businesses that ask us for direct integration actually need an aggregator plus better reconciliation.
A pattern we recommend for medium-scale platforms: integrate two aggregators behind a routing layer. When one has an outage (they all do), your checkout fails over automatically instead of losing a day of sales.
The engineering details that make or break UPI checkout
This is where we see most integrations go wrong — and where our development work concentrates:
- Never trust the client. Payment success must be confirmed by server-to-server webhook with signature verification, not by the app saying "payment done." Fraudulent "success" screenshots are a cottage industry.
- Handle the pending state. UPI transactions can sit in
PENDINGfor minutes when a bank's UPI switch is slow. Your UX needs an honest "confirming your payment" state with server-side polling — not a spinner that times out into a false failure while money has actually left the customer's account. - Idempotency everywhere. Retries and duplicate webhooks will happen. Every order gets one unique reference; processing the same webhook twice must not credit twice.
- Automated reconciliation. Every day, your system should match aggregator settlement files against your own ledger — transaction by transaction, fees and refunds included. Businesses doing this manually in Excel burn hours daily and still miss mismatches. We build recon jobs that flag exceptions only.
- Refund flows with state tracking. UPI refunds usually land in minutes but can take days; your support team needs visibility, and your customer needs proactive status updates — ideally over WhatsApp, wired up as described in our WhatsApp Business API guide.
Settlements, soundboxes, and the offline counter
Two practical matters that surprise first-time merchants:
Settlement cycles. UPI money reaches the customer's bank instantly, but reaches you on the aggregator's settlement schedule — typically T+1 working day by default, with same-day or on-demand settlement available for a small fee (often 0.1–0.3%). Plan working capital around T+1, and reconcile settlements (net of fees and refunds) rather than gross collections, or your books will drift from your bank statement within a week.
Physical retail. If you also sell across a counter, the same aggregator account powers a printed static QR (free), a dynamic QR from your billing screen (ties every payment to a bill number — vastly better for reconciliation), and a soundbox (₹125–₹250/month rental) that announces payments so staff stop checking phones. For multi-counter stores, dynamic QR from the POS is the difference between knowing that money came in and knowing which sale it belongs to. Cash-heavy businesses moving to UPI also gain something subtler: a clean digital turnover trail, which strengthens loan eligibility — lenders underwriting on real transaction data is precisely the model platforms like LoanKard support.
UPI beyond India. UPI acceptance is live in markets like Singapore, the UAE, Mauritius, Sri Lanka, France (in phases), and Nepal/Bhutan, and NRIs can link international mobile numbers to UPI on Indian accounts. For most domestic businesses this changes nothing today — but if you serve foreign tourists or NRI customers, ask your aggregator what international UPI acceptance they support before assuming card-only.
Compliance: GST, DPDP, and RBI rules you cannot skip
- GST: every successful payment should generate a GST-compliant invoice with your GSTIN, HSN/SAC codes, and correct tax split (CGST/SGST vs IGST). Wire invoicing into the payment webhook so it is automatic, not a month-end scramble.
- DPDP Act 2023: you are storing payment-adjacent personal data — names, phone numbers, transaction history. That means documented consent, purpose limitation, and deletion capability.
- RBI card tokenisation applies if you also take cards: no raw card storage, ever. Aggregator token vaults handle this.
- No convenience-fee games on UPI: surcharging basic UPI violates the zero-MDR policy's intent and aggregator terms. Price it into your product.
Rollout plan: from zero to live in three weeks
Week 1 — aggregator KYC and sandbox: business proof, bank account, website/app review; integrate test flows. Keep your website's terms, privacy policy, and refund policy pages live before applying — aggregator compliance teams check them, and missing pages are the most common onboarding rejection we see. Week 2 — build the real checkout: intent flow on mobile, dynamic QR on desktop, webhooks, receipts, refunds. Week 3 — hardening: failure-path testing (dropped connections, pending states, duplicate webhooks), reconciliation job, go-live with a soft launch to 10% of traffic. Payment bugs discovered in production cost trust; payment bugs found in week 3 cost nothing. Digitising payments is also usually step one of a larger modernisation — see our digital transformation roadmap for SMBs for how the pieces sequence.
Talk to us
NexaEx builds payment-grade systems — UPI checkouts, Autopay mandates, reconciliation engines, and full billing platforms — from Erode, Tamil Nadu, for clients across India. If your checkout is leaking conversions or your accountant is drowning in settlement files, contact us or WhatsApp +91 97912 97741. We reply within 24 hours with a straight answer, and you can sanity-check budgets first on our project cost calculator.
Frequently asked questions
How much does it cost to integrate UPI payments into a website or app?
Aggregator onboarding is free apart from KYC effort. Engineering costs run Rs 25,000-60,000 for a basic website checkout, Rs 50,000-1,20,000 for mobile app intent flows, and Rs 60,000-1,50,000 for UPI Autopay mandates. Basic UPI person-to-merchant transactions carry zero MDR under current policy.
Should I integrate directly with a bank or use a payment aggregator?
Use a licensed aggregator like Razorpay, Cashfree, PhonePe or Paytm unless you process several crore monthly and basis points matter. One API covers UPI, cards and netbanking with dashboards and refunds built in. Direct bank integration brings certification cycles and months of timeline that rarely pay back at SMB scale.
What is UPI Autopay and when should a business use it?
Autopay lets a customer approve a recurring mandate once, after which you debit automatically on schedule — the rail for subscriptions, SaaS billing, school fees, memberships and EMI collection. Mandates up to Rs 15,000 execute without per-debit authentication, with higher limits for specific categories; verify current NPCI circulars.
Why do UPI payments show as pending, and how should my app handle it?
When a bank UPI switch is slow, transactions can sit in pending for minutes even though money has left the customer account. Your app should show an honest confirming state, poll server-side, and confirm success only via signature-verified webhooks — never from the client — to avoid false failures and fraud.