UPI's Zero-MDR Rule Just Changed: What the 2026 MDR Bill Means for Your Payment Gateway API

UPI has been free for merchants since January 2020, when the government banned banks and payment providers from charging a Merchant Discount Rate on UPI and RuPay debit card transactions. That changed, at least on paper, this August. Parliament has now passed the Taxation and Other Laws (Amendment) Bill, 2026, which amends Section 10A of the Payment and Settlement Systems Act, 2007 and hands the central government the power to decide, by notification, which payment modes keep zero MDR and which don't. I run UroPay, a UPI payment infrastructure company, and I spent the past couple of weeks reading the actual bill text and the reporting around it instead of the headlines, because the headlines have been more dramatic than the bill itself. Here's what I found, and what it should change about how you pick a payment gateway API right now.

What just changed: the 2026 bill that reopens UPI's zero-MDR rule

Finance Minister Nirmala Sitharaman introduced the Taxation and Other Laws (Amendment) Bill, 2026 in the Lok Sabha on August 4, 2026. It cleared both the Lok Sabha and the Rajya Sabha within the following two weeks. The part that matters for anyone accepting UPI payments is a change to Section 10A of the Payment and Settlement Systems Act, 2007. That's the exact clause that has kept UPI and RuPay debit card transactions free of MDR since January 2020.

Before this bill, Section 10A named specific electronic payment modes (the ones notified under the Income-tax Act) and simply barred any bank or system provider from charging on them. The amendment swaps that fixed list for a rule letting the central government notify, whenever it wants, which payment modes stay MDR-free and which don't. In plain terms, the blanket, permanent zero-MDR guarantee on UPI is gone from the law itself. What replaces it is government discretion, exercised through future notifications rather than the Act.

That distinction got lost in a lot of the early coverage. The bill itself does not introduce any charge. Sitharaman said as much on the floor of the Rajya Sabha: "No MDR framework has yet been finalised." Nobody is paying anything new today. What changed is that the government now has a legal switch it can flip later, and it didn't have that switch before.

If you run a business that takes UPI payments, through a hosted button, a payment link, or your own checkout built on an API, none of your current costs moved this week. But the ground under "UPI will always be free to accept" just shifted. If you're evaluating a payment gateway API right now, that shift is worth factoring in rather than finding out about it later from a rate change notice.

Why zero-MDR existed since 2020, and why the government wants a way out

The zero-MDR mandate wasn't an accident. In January 2020, the government barred MDR on UPI and RuPay debit transactions specifically to get merchants, especially small ones who'd resisted digital payments because of card-machine fees, onto UPI fast. It worked about as well as a policy can work. UPI now accounts for roughly 88% of India's digital transactions, processing more than 23 billion transactions worth close to ₹30 lakh crore every month, according to industry estimates reported by Business Today. NPCI put the number of UPI users at 55.49 crore as of June 2026.

That scale is also the problem. A Parliamentary Standing Committee has warned that the zero-MDR regime made the UPI ecosystem financially difficult to sustain. Banks and payment service providers process an enormous volume of transactions for a fee of exactly zero, while still carrying the cost of fraud prevention, uptime, dispute handling, and infrastructure that scales with every new user. The same committee projected UPI could add 600 million more users and handle 100 to 150 billion transactions a month in the years ahead, which only makes the "who pays for this" question louder.

Industry estimates cited by Business Today put a possible MDR of 25 to 30 basis points, roughly ₹2.50 to ₹3 per ₹1,000, on eligible merchant transactions at around ₹13,000 crore a year in potential revenue for the ecosystem. Other estimates, reported separately by Business Standard, put the number closer to ₹5,000-10,000 crore by FY28. The gap between those two figures tells you how unsettled the actual number still is. Either way, the payments industry has argued fairly consistently that sustained investment in fraud prevention and infrastructure needs a revenue line somewhere, and zero has stopped working as that number at UPI's current scale.

None of that changes what the government has publicly committed to protecting. Every statement from the Finance Ministry on this bill has repeated that consumer UPI payments and person-to-person transfers stay free. Whatever MDR eventually looks like, it's aimed at a slice of merchant transactions, not the UPI app on your phone.

Six questions the new MDR framework still has to answer

I'd stop short of telling you exactly what to plan for, because the bill doesn't say. Business Standard laid out six operational questions that remain open before any actual charge could take effect, and it's the clearest framing I've come across.

Who counts as a chargeable merchant? The government has said MDR would apply only to merchant transactions "above a specified threshold," without saying whether that threshold is based on annual turnover, per-transaction value, transaction volume, or some mix. Sources cited by Business Today point to a possible ₹2,000 per-transaction threshold, but that's reporting on internal discussions, not a finalised rule.

What actually triggers the charge? Crossing a turnover threshold and crossing a per-transaction value threshold are two different tests, and the framework hasn't picked one yet.

Is it a percentage or a flat cap? The government has only said any MDR would be "nominal" and lower than card MDRs. No number, no formula.

Who gets paid? MDR revenue would presumably be split between the issuing bank, acquiring bank, UPI app, payment service provider, aggregator, and NPCI, but the bill doesn't set out a revenue-sharing mechanism.

Can merchants pass the cost to customers? Unclear. The bill's language is about charges on the person "making or receiving" a payment, which leaves open whether a merchant-side MDR could show up as a customer-facing surcharge.

What happens on refunds and failed payments? Also unaddressed, which is a real gap for any business with a meaningful return rate.

The government has said the UPI and Services Steering Committee, headed by NPCI, will work out these details once the bill takes full effect. That means a gazette notification, RBI guidelines, and realistically months before there's an actual number to plan around. I'd treat any "UPI transactions now cost X%" claim you see online right now with some skepticism until that committee publishes something.

MDR is not the same charge as your payment gateway's commission

Here's where I think a lot of confusion is going to happen over the next few months, so it's worth clearing up now rather than after someone's made a bad decision because of it.

MDR is a charge on the underlying UPI payment rail itself, something a bank, NPCI, or the payment network could levy regardless of who's facilitating the transaction. It has nothing to do with which payment gateway, aggregator, or API you use. If an MDR framework lands, it would sit underneath whichever tool you've built your checkout on.

A payment gateway's or facilitator's commission is a separate charge. It's what you pay a company like Razorpay, Cashfree, PayU, CCAvenue, or the UroPay API for the actual service: an API, a checkout, settlement to your bank, dispute handling, support. That commission exists today, has always existed for aggregator-model products, and isn't affected either way by whatever MDR framework the government eventually settles on. The UroPay API, for instance, already charges 5% + ₹5 per transaction with KYC or 10% + ₹5 without. That's a facilitator commission for the infrastructure, not an MDR, and it wouldn't automatically change if MDR gets switched on for large merchants next year.

Where it gets murkier is UroRelay, our zero-commission product where a customer pays directly into a merchant's own UPI account and the credit SMS confirms the order. There's no aggregator sitting in the middle at all. Whether a future MDR framework would apply to that kind of direct peer-to-peer flow the same way it applies to aggregator-routed payments is one of the six open questions above, specifically how "chargeable merchant" gets defined. I'm not going to pretend I know the answer, because nobody does yet, including the people writing the framework.

The practical takeaway: don't assume your payment gateway's fees are somehow included in, or excluded from, a future MDR. They're a separate layer, and they'll stay separate no matter what the steering committee decides.

What this means if you're choosing a payment gateway API right now

If you're building a checkout today, inside a SaaS product, a marketplace, an app, or a website that needs to move past a hosted payment link, this bill doesn't change the mechanics of that decision much. You still need an API that returns an order, redirects to a UPI intent, and tells you reliably when the money landed. What it should change is how you weigh the providers on offer, in a couple of specific ways.

First, transparency about how commission is actually structured matters more than it did a month ago. A provider whose pricing page buries the real commission behind a "starting from" number, or that requires a sales call to find your actual rate, is going to be a worse partner when an MDR framework eventually needs explaining. You want to be able to read your rate on a page, not extract it from a PDF proposal.

Second, who you can actually reach when the rules change matters more than usual. When NPCI's steering committee eventually publishes an MDR framework, every payment provider in India will have to explain to its merchants how that framework interacts with their existing commission, and whether anything on the invoice changes. At a large aggregator, that explanation arrives as a mass email or an FAQ update. On the UroPay API, it's something you can ask me directly, at gaurav@uropay.me, and get an answer specific to your setup rather than a template written for the median merchant.

Third, and this is less about the MDR bill and more a general point worth making while it's on your mind: pick your provider based on your actual constraints, not just the headline commission rate. If you're KYC-ready, a mainstream aggregator's roughly 2% + GST beats the UroPay API's 5% + ₹5 on pure cost, and I'd tell anyone that directly if they asked. Where the calculus flips is if your KYC paperwork isn't ready yet, or your category is one that bigger, stricter aggregators are slow to approve or decline outright. That's where the UroPay API earns its higher price. Not by being cheap.

UroPay API vs traditional payment gateway APIs: a side-by-side look

UroPay APITypical aggregator API (Razorpay / Cashfree / PayU / CCAvenue)
Commission5% + ₹5 with KYC, or 10% + ₹5 without KYCRoughly 2% + GST, broadly similar across providers
KYC requirementOptional. Start on the non-KYC tier, upgrade any timeMandatory before go-live in almost all cases
Settlement timeT+3 working days with KYC, T+5 withoutTypically T+1 to T+2 working days
Onboarding timeAbout 5 working days, after a website/app audit and signed contractOften longer for full KYC review; near-instant for pre-approved categories
Who owns the checkoutYou do. Your own domain, your own brand, two REST endpoints and a webhookYou do, on their SDK or checkout components
Restricted or edge-case categoriesConsidered case by case, subject to a published 44-category prohibited listFrequently placed on hold, slow-walked, or declined outright
Support modelDirect contact with the founder, gaurav@uropay.meTicket queues; dedicated human support usually gated behind account size or plan tier

That commission gap is real. If your business is fully KYC-compliant, sells nothing on the prohibited list, and just needs the cheapest rail, a mainstream aggregator's API is the better deal on paper. The UroPay API is built for the businesses that don't fit that description as cleanly: the ones still assembling paperwork, or operating in a category a bigger platform's risk team would rather not touch.

A worked cost example, today and under a possible MDR tomorrow

Take a ₹50,000 month in sales, sold in individual transactions averaging ₹2,500 each: 20 transactions.

On a typical aggregator API at roughly 2% + GST, you'd pay around ₹1,180 in fees (2% of ₹50,000, plus 18% GST on that commission), landing about ₹48,820 net, usually within a day or two.

On the UroPay API with KYC completed, at 5% + ₹5 per transaction, you'd pay ₹2,500 in commission plus ₹100 in flat fees (₹5 × 20 transactions): ₹2,600 total, landing ₹47,400 net, on a T+3 cycle.

Without KYC, at 10% + ₹5, that's ₹5,000 in commission plus ₹100 in flat fees: ₹5,100 total, landing ₹44,900 net, on T+5.

That's not a close race on price, and I'd rather show you the actual gap than dress it up as competitive, because it isn't. Anyone who's shopped around would spot the spin immediately.

Now add a hypothetical MDR, say the 25-30 basis point range that's been floated in reporting, applied only if your business crosses whatever threshold the eventual framework sets. On the same ₹50,000, that's roughly ₹125-150 more, regardless of which gateway sits on top of the transaction, because MDR is a separate charge on the rail itself, not a markup on your gateway's commission. It moves every provider's net figure down by roughly the same small amount. It doesn't close the gap between a 2% aggregator and a 5-10% facilitator commission, because that gap was never about MDR to begin with.

So what does the higher UroPay API commission actually buy, if not a lower bill? Three things, stated plainly: direct founder-level support instead of a ticket queue, a real non-KYC path to going live rather than a paperwork wall, and a real shot at approval for restricted or edge-case categories that bigger platforms turn away. Whether that trade is worth ₹1,000-3,000 more per ₹50,000 in sales depends entirely on whether those three things solve a problem you actually have.

Getting your UPI checkout ready before the rules land

I'd rather you build on something you understand than rush a decision because a bill made headlines. Here's the actual path if you want to move to the UroPay API:

  1. Apply from the dashboard. Head to dashboard.uropai.in and tell me about the business, the site or app taking payments, and expected volumes.
  2. Website or app audit. I review the product against the 44-category prohibited list: what you sell, your policies, your pages.
  3. Decide on KYC now or later. Submit documents for the 5% + ₹5, T+3 rate, or skip that step and start on the 10% + ₹5, T+5 non-KYC tier. Upgrade whenever you're ready.
  4. Sign the merchant contract. Every merchant signs one covering commission, settlement, refunds, and chargeback liability before going live.
  5. Get your live keys. You'll also have a TEST key pair from day one, so you can build and check your webhook handling before any real money moves.
  6. Integrate two endpoints and a webhook.POST /v1/orders to create an order, a GET to check status, plus a signed webhook for PAID, FAILED, and EXPIRED notifications. The API reference has copy-paste samples in Node, Python, PHP, and cURL.

Live in about 5 working days from application to first transaction. If you'd rather not write any integration code at all, and a payment link or button covers your use case, UroRelay gets you live in minutes at zero commission. You can always move to the API later once you need your own checkout.

Quick takeaways

  • Parliament passed the Taxation and Other Laws (Amendment) Bill, 2026, amending Section 10A of the Payment and Settlement Systems Act, 2007, the law that has kept UPI MDR-free since January 2020.
  • The bill itself sets no MDR rate. It only gives the central government the power to notify future changes; the actual framework is still pending an NPCI-led steering committee.
  • Consumer UPI payments and P2P transfers are explicitly protected and will stay free regardless of what the merchant framework eventually looks like.
  • MDR (a charge on the payment rail) and a payment gateway's commission (a charge for the service around it) are two separate things. Don't assume one absorbs or replaces the other.
  • The UroPay API's commission, 5% + ₹5 with KYC or 10% + ₹5 without, is higher than mainstream aggregators' roughly 2% + GST, and that gap has nothing to do with MDR either way.
  • What the higher commission buys: direct founder-level support at gaurav@uropay.me, a real non-KYC path to going live, and a genuine shot at onboarding for restricted or edge-case categories other aggregators decline.
  • If you're fully KYC-ready and selling nothing on the prohibited list, a mainstream aggregator is the cheaper choice today, MDR bill or not.

Where this leaves your payment stack

None of this is a reason to panic about your checkout, and I'd be doing you a disservice if I dressed it up as one. Nothing has gotten more expensive this week. What's changed is that the government now has the legal room to introduce a merchant-side UPI charge, on terms nobody, including the ministry itself by its own admission, has finalised yet. Consumers and P2P transfers stay free either way.

If you're picking a payment gateway API in the meantime, I'd weigh it on things that were already true before this bill existed: whether the provider is upfront about what you'll actually pay, whether you can get a real answer from a real person when something changes, and whether they're willing to work with your business as it actually is rather than as their risk model prefers it. That's the case I'd make for the UroPay API regardless of what NPCI's committee eventually decides on MDR. Not because it's the cheapest option, because it isn't, but because it's upfront about the trade you're making. Get your test keys and see whether that trade makes sense for your business, or read the full pricing and audit details first if you'd rather look before you apply.

FAQ

Does the 2026 MDR bill mean I have to pay extra for UPI payments now?No. The Taxation and Other Laws (Amendment) Bill, 2026 gives the government the power to introduce MDR on UPI in the future, but it doesn't set a rate or start any charge itself. No MDR framework has been finalised, and the government has said any future charge would apply only to specific merchant transactions above a threshold that hasn't been announced yet.

Will small businesses have to pay MDR on UPI transactions?It's not decided. The government has said any future MDR would apply only to a limited category of merchant transactions above a specified threshold, reported discussions mention a possible ₹2,000 per-transaction level, but the criteria (turnover, transaction value, category, or some combination) haven't been finalised.

Is MDR the same as the commission I pay my payment gateway?No. MDR is a potential charge on the UPI payment rail itself, separate from whichever gateway or facilitator you use. Your payment gateway's commission, like the UroPay API's 5% + ₹5 with KYC or 10% + ₹5 without, is a service fee for the checkout, settlement, and support infrastructure, and it exists independently of MDR either way.

When will the UPI MDR framework actually take effect?There's no confirmed date. After the bill's presidential assent and gazette notification, the UPI and Services Steering Committee, headed by NPCI, still has to work out the rate, eligible merchants, and revenue-sharing before RBI can issue implementing guidelines. That process typically takes months, not weeks.

Should I wait to pick a payment gateway API until the MDR rules are finalized?Probably not. MDR would sit on top of whichever gateway you're using, and would apply the same way regardless of which provider processes the transaction. Waiting only delays getting your checkout live. Pick based on today's known factors: KYC readiness, your category, and how much support you'll need, and revisit if and when an actual MDR framework is published.

Have you already factored a possible UPI MDR into your pricing or margins, or is this the first you're hearing that the zero-MDR guarantee isn't permanent? I'd like to know how businesses are actually thinking about this. Reply to this post or write to me at gaurav@uropay.me, and pass it along to anyone else running an online business who's going to be affected by whatever the steering committee decides.

References