UPI is Indian commerce's default rail — and integrating it well is the difference between payments that convert and support tickets that multiply. Here is the business-level guide with enough technical honesty to keep vendors straight.
The integration paths
Via payment gateway (Razorpay/Cashfree/PayU-class). One integration, all methods (UPI, cards, netbanking, wallets), webhooks, dashboards, refunds — at ~1.9–2.5% fees (UPI often cheaper or subsidized). The right default for 95% of businesses: integration cost of ₹0.4–1.5L into an existing product, live in days.
Deeper flows worth knowing: UPI intent (app-to-app on mobile — tap, UPI app opens pre-filled, approve; the highest-converting mobile flow and a must for apps and PWAs), dynamic QR for counter/kiosk contexts (POS territory), and payment links pushed via WhatsApp — the receivables workhorse.
UPI Autopay (mandates). Recurring payments for subscriptions — setup once, auto-debit within limits, with mandate management (pause/cancel) you must surface in-product. For Indian SaaS and memberships this is the churn-reduction rail: card-on-file failure rates that plague Indian subscriptions largely vanish.
The part everyone underestimates: reconciliation
Payments mostly succeed cleanly; the edge cases eat ops time — pending-then-success after timeout, success-at-bank but webhook missed, refunds in flight, duplicate attempts. Production-grade integration means webhook-driven status as truth (never the redirect page), idempotent order handling (the same payment credited once no matter how many callbacks), a daily auto-reconciliation of gateway settlements against orders (the restaurant-aggregator lesson generalized), and clear user messaging for the pending state. Ask any vendor how they handle "payment deducted but order not created" — the answer grades the integration.
Compliance notes
Keep card data out of your systems entirely (gateway-hosted fields); UPI itself spares you PCI scope for that rail. Transaction data is personal data under DPDP — retention and access rules apply.
Costs summary
Gateway integration into existing product: ₹0.4–1.5L. Autopay/mandate flows: +₹0.5–1.5L. Reconciliation automation: +₹0.5–2L — the piece that pays for itself in ops hours forever. All standard scope in our builds; ask us to review an existing integration and we will find the reconciliation gaps in a day.
Frequently asked questions
How much does UPI integration cost?
Gateway-based integration into an existing product runs ₹0.4–1.5 lakh and goes live in days. UPI Autopay mandate flows add ₹0.5–1.5 lakh, and automated reconciliation — the piece that saves ops hours forever — adds ₹0.5–2 lakh.
Should I integrate UPI directly or through a gateway?
Gateway (Razorpay/Cashfree-class) for 95% of businesses: one integration covers UPI, cards, and netbanking with webhooks and refunds at ~2% fees. Direct integrations belong to volume tiers where fee savings fund the engineering.
What is UPI Autopay and who needs it?
Recurring mandates — customers approve once, auto-debits follow within limits. For Indian SaaS, memberships, and subscriptions it's the churn-reduction rail, replacing the card-on-file failure rates that plague Indian recurring billing.
What payment edge cases must my integration handle?
Pending-then-success after timeouts, bank success with missed webhooks, in-flight refunds, and duplicate attempts. Production grade means webhook-driven truth, idempotent order handling, daily settlement reconciliation, and honest pending-state messaging.