A practical, current guide to accepting UPI payments on your website in India: the three ways to do it, why UPI is nearly free to accept (zero MDR), the Collect vs Intent flow, and how to set it up with a payment gateway.
UPI is how India pays - it is fast, familiar, and for most businesses almost free to accept. If you sell anything on a website, accepting UPI at checkout is no longer optional. The good news: setting it up is simpler and cheaper than most first-time founders expect. Here is the practical, current version.
business@ybl) and let customers scan and pay. Great for invoices, social selling and offline, but clunky for a real website checkout because the customer has to leave the page, pay, and you have to reconcile manually.For a proper website checkout, go with option 3. The rest of this guide focuses there.
Mostly no - and this surprises people. Standard bank-to-bank UPI runs on a zero-MDR (Merchant Discount Rate) regime in India, in place since January 2020. That means there is no per-transaction merchant fee on normal UPI payments. Small merchants can even earn a government incentive of about 0.15% on transactions up to Rs.2,000.
Two honest caveats:
When you accept UPI online, the payment happens one of two ways:
This is now more than a UX choice. NPCI guidelines effective February 2026 restrict manual VPA entry on mobile and push the industry toward Intent flow, so a good gateway should default to Intent on mobile. When you compare gateways, ask how they handle Intent.
Short version: Razorpay is the default all-rounder for startups, Cashfree is strong on payouts and cross-border, and Instamojo is the fastest start for freelancers and small sellers who want payments plus a simple store. We compare them properly in the best payment gateway for startups in India guide, and you can browse every option in the Payments category.
UPI rules and gateway pricing change. Confirm current MDR, fees and flow support on the provider's own site before going live.
Turn this research into a workflow with apps, stages, caveats, and next actions.
Start with the product itself: a place to write and ship code, host it reliably, and catch errors in production, because nothing else matters until customers can actually use what you built. Next, get the team coordinated with project management and a shared knowledge base so work and decisions are not lost in chat. Then put customer acquisition on a real CRM so leads, demos, and deals are tracked rather than living in inboxes. Add billing and accounting once you have paying users, choosing payment rails that fit whether you sell to India, abroad, or both, and keep GST-clean books from day one. Finish with customer support, product analytics, and access security so you can keep users happy, see what they actually do, and not get breached. Do not buy enterprise sales, analytics, and security suites before you have product-market signal; sequence around shipping and getting your first paying customers.
View stack
Start by choosing the right no-code platform for what you are building, because a customer-facing web app, a mobile app, and an internal portal each suit different tools. Next, model your data cleanly in a database or spreadsheet backend, since a messy data model is the most common reason no-code projects collapse later. Then build the interface and logic so users have real screens and workflows, not just a database. Add payments, forms, and automations to connect your app to the outside world and remove manual work. Finish by launching, securing team access, and measuring usage so you know the app works and is safe. Do not expect no-code to scale infinitely; it is excellent for validating and running real workflows, but be honest about its ceilings and plan to move to custom code if you outgrow it.
View stack
Start by choosing a website builder that matches your skill and needs, because the builder decides how fast you launch and what you can do later. Sort your domain and hosting next, remembering that most builders bundle hosting while self-hosted WordPress needs its own, so you do not pay twice. Then design and write the site so it looks credible and explains clearly what you offer, since a confusing site loses visitors in seconds. Add lead capture, booking, and payment tools so the site actually does something, whether that is collecting enquiries, taking appointments, or selling. Finish by getting found and measuring, with basic SEO, a Google presence, and analytics so you know what is working. Do not over-build a complex site before you have visitors; launch a clear, fast site and improve it with real data.
View stack
Describe your actual business goal and FindThatSoftware will map the apps, trade-offs, setup stages, and buying caveats.
Build a pipeline