Yes, a small business in India can accept UPI on its own website in 2026 without paying any UPI charge, because merchant UPI transactions are still inside the government's zero-charge framework. What you do pay is your payment gateway's fee, usually about 2% plus 18% GST on that fee, and a one-time build cost if someone has to integrate the checkout. The MDR noise you saw in August did not change any of this yet.

UPI QR code on a phone at a shop counter

The cost, before the explanation

Three separate bills land on you, and people mix them up constantly.

The UPI rail itself: zero. Free now, and free for the foreseeable future for normal transactions.

The gateway: about 1.75% to 2.5% per transaction plus 18% GST, depending on volume and payment method. Razorpay's pricing page still leads with 2%, with no platform fee for the first 90 days and custom pricing for anyone above ₹5 lakh a month. Cashfree positions itself at the cheaper end for high volumes. PayU and Paytm sit in the same band.

Your developer: anything from zero, if your site already has a checkout and the gateway has a plugin for it, to a few days of work if you want proper order reconciliation, invoices and failure handling on a custom stack.

If you sell ₹80,000 online in a month, budget roughly ₹1,600 in gateway fees plus GST. That is the entire cost until the government actually notifies an MDR.

Why everyone started asking this in August

On 8 August 2026 the Finance Ministry put out a statement clarifying that consumers will not pay UPI charges, all person-to-person UPI transfers stay free, and the vast majority of merchant transactions stay free too. Any MDR, if introduced, would be threshold-based, would apply only to a limited set of merchant transactions, and would be nominal and lower than card MDR.

That statement came after an amendment to the Payment and Settlement Systems Act, 2007, and an RBI governor comment a few days earlier that someone will have to pay the cost of UPI, because banks and NPCI currently carry it. Once Parliament passes the Taxation and Other Laws (Amendment) Bill, 2026, the UPI and Services Steering Committee under NPCI decides whether an MDR happens at all. Reported proposals have been around 0.3% on transactions above ₹2,000.

Two numbers worth keeping in your head when you read the panic posts. UPI processed 24.51 billion transactions worth ₹29.82 lakh crore in August 2026, an all-time volume record according to NPCI data. And per a Jefferies estimate quoted by the BBC, transactions above ₹2,000 account for about 4% of merchant payment volumes but around 67% of their value. So a threshold MDR at ₹2,000 mostly touches high-ticket sellers, not a ₹300 order from your salon booking page.

A LocalCircles survey published in early September, with 32,796 responses, found 41% of merchants unwilling to bear any MDR above ₹2,000, and only 17% willing to absorb 0.3% or more. Merchants are not quietly assuming they will pay. Nobody knows the final design yet, and anyone telling you the rate is finalised is guessing.

Four ways to take UPI on a website, ranked by effort

A gateway checkout. Razorpay, Cashfree, PayU, PhonePe or Paytm hosted checkout, dropped into your site via plugin or API. Customer picks UPI, opens their app, pays, comes back to your order confirmation. This is what you want once you have real order volume, refunds or invoices.

A static UPI QR on the page. Costs nothing beyond a bank QR. Works for a single-price product, a deposit, a booking fee. You get zero automation: someone has to check the bank statement and mark the order paid. I have seen shops run this for two or three orders a day and it is fine. Past that, it breaks.

Payment links. Your gateway or a link tool generates a payment link, you send it on WhatsApp. No website needed. Genuinely useful for quotes, advances and one-off jobs.

UPI intent inside a custom checkout. This needs real engineering and, if you are collecting money on behalf of other sellers, a payment aggregator licence from RBI. Do not build your own pooling flow and hope nobody notices.

Do you need GST to switch payments on?

Usually no. If your turnover is under ₹20 lakh for services or ₹40 lakh for goods in most states, you are not required to register, and gateways accept a self-declaration or non-enrolment declaration instead of a GST certificate. Freelancers and sole proprietors routinely onboard with a PAN, an Aadhaar, business proof like an Udyam registration, and a cancelled cheque.

The exception catches a lot of small sellers: supply through an e-commerce operator, and Section 24 of the CGST Act makes registration mandatory regardless of turnover. So if you sell on Amazon or Flipkart, GST is not optional.

There is a second thing gateways check that has nothing to do with tax. Under RBI's payment aggregator guidelines, they must review your website before approving you. Product or service details, pricing, a refund and cancellation policy, and a working contact page. I have watched a perfectly good business sit in onboarding limbo for a week because the site had a contact form that silently failed and no refund page. Fix that before you apply, not after.

Shop owner checking payments on a laptop

What the setup looks like when I build it

Whatever gateway you pick, the website side is roughly the same shape, and it is where most DIY integrations quietly fail.

The order is created first, with a unique reference you control, not the gateway's. Then the checkout opens against that reference. Then the gateway sends a webhook to your server, and you verify the signature before marking anything paid. Then your confirmation page reads the order status from your own database, never from a URL parameter.

That last point matters more than it sounds. If your confirmation page says "payment successful" because a query string said so, someone will eventually edit that string and get a free order. I have seen it on a client's WooCommerce add-on, and the fix took twenty minutes. The failure was a year of not checking.

Two more things I set up as standard now: a failed-payment path that actually tells the customer their money was not deducted, and settlement reports mapped to orders so the business owner can reconcile without calling me every Monday.

Mistakes I see on small business sites

Settling into a personal savings account. Fine for a freelancer taking three payments a month. Bad once your volumes climb, because your bank sees business inflows into a savings account, and your accounting gets messy at exactly the wrong time of year.

Treating the gateway fee as invisible. Add a small "convenience fee" only if your gateway's agreement allows it and the rules in your jurisdiction permit it. Some do, some do not, and quietly adding one can get your account flagged.

Ignoring refunds until the first one happens. Set up a refund flow before you need it. Refunds through the gateway take a few working days to reach the customer, and if you have no process, you will promise timelines you cannot keep.

Assuming settlement is instant. T+2 is normal, T+1 usually costs extra or needs volume. Plan cash flow around it, especially if you also pay suppliers quickly.

What I would do if I were starting today

Under ₹50,000 a month in online sales: your bank's UPI QR and payment links. Skip the gateway, keep the money, do the reconciliation manually.

Between ₹50,000 and ₹5 lakh a month: one gateway, UPI enabled by default, T+2 settlement, integrated properly with webhook verification. Razorpay or Cashfree both do this well. The 2% is the cost of not chasing payments on WhatsApp at 11pm.

Above ₹5 lakh a month: talk to two or three providers, ask for volume pricing in writing, and ask what your effective rate is after a year of refunds and chargebacks. The headline rate is rarely the final number.

And whatever you choose, keep a customer-facing payment page that loads fast on a phone. Indian customers pay on phones, often on patchy 4G. A checkout that takes more than a few seconds to open loses orders that UPI itself was never the problem with. That is the part most businesses underinvest in, and it is fixable.

If you want the checkout built properly on a Next.js or React site, or you want someone to audit the payment flow you already have, see what I do or start a project. You can also look at recent client work to see how these builds actually land. If you are still deciding whether the website is worth the spend at all, my breakdown of what website maintenance should cost in India and this piece on why a site does not show up on Google are worth ten minutes.

Customer paying with UPI on a phone at a market

Questions I get from clients

Is UPI free for merchants right now?

Yes, for practically all of you. The zero-charge framework has been in place since January 2020. The gateway fee is a different charge, paid to a private company for the checkout, the settlement and the reconciliation, not to NPCI for using UPI.

Will my gateway pass on an MDR if the government introduces one?

Possibly, and the honest answer is that nobody can tell you the rate yet. What the government has committed to is that it will be threshold-based rather than blanket, that P2P stays free, and that everyday small merchant transactions stay free. Watch your gateway's emails rather than news headlines.

Is a UPI QR code on my site enough?

For low volumes, yes. Once you are doing more than a handful of orders a day, the manual matching will cost you more time than the gateway fee costs money.

How long does gateway onboarding take?

One to three working days with clean documents. Name mismatches between your PAN, bank account and business proof are the single most common delay, and a weak website is the second.

What documents will the gateway ask for?

Expect PAN, a government ID of the signatory, business registration proof such as Udyam or a Shop and Establishment certificate, a cancelled cheque, and either a GST certificate or a non-enrolment declaration. Keep the name on all of them identical.