Stories

Some Thoughts on the Economics of UPI and MDR

Article news.ycombinator.com

Some Thoughts on the Economics of UPI and MDR

The announcement of MDR charges for certain UPI transactions from 15th October has created a fair amount of panic and controversy, as one might expect.

One side of the debate is arguing that this is “only for merchants, not consumers”, that the system cannot run for free forever, and that most UPI transactions will remain unaffected. On the other side, ordinary citizens and merchants are understandably concerned. UPI was deliberately built around a zero-MDR model and was subsequently supported by government incentives. So the shift towards a transaction-funded model naturally raises the question: why now, and who exactly is going to benefit from it?

UPI was designed to make digital payments almost invisible: instant, ubiquitous and free. The difficult question was always who pays for the machinery underneath it. The decision presents an interesting economic dilemma. On one hand, there is some precedence for ‘upkeep charges’ here. I tried to research many digital payment systems across the world including credit and debit cards, Brazil’s Pix (similar to India’s UPI), wallet systems like PayPal and Webmoney, etc. and couldn’t find a major payment ecosystem that’s fully free or govt subsidized.

But on the other hand, the govt wastes thousands of crores in useless things like election freebies, care funds, etc. Subsidizing Rs. 2K crores for a UPI system that forms the payment backbone of the country should be a pittance comparatively. Apart from arbitrary thresholds proposed in this framework (like who decided on Rs. 2000 as limit for MDR?), I wanted to understand where this demand is coming from and who in the UPI ecosystem is facing losses that now need to be covered.

The podcast The new UPI equation by The Ken is highly informative in this regard and recommended watch if you’re interested in this topic.

https://www.youtube.com/watch?v=KX5dEhO09xA

The question isn’t really whether UPI costs money. It obviously does. The interesting question is who should pay for it, and who should capture the resulting revenue.

The UPI infrastructure cost is presently borne by both Banks and UPI app developers like GPay and Phonepe. The UPI apps apparently operate on a ‘break even’ model, they don’t earn any revenue from the payment transfers itself but by providing other value added services through their apps like credit and insurance products, travel booking, etc. In the early days of UPI, this model was probably sustainable but overtime it has saturated a lot, perhaps due to too much competetion and UPI coverage approaching its growth limit in the country.

The demand for MDR appears to have come primarily from these app developers as they’re the ones losing the most in this payment cycle. Another interesting aspect is the subsidy received from govt. As mentioned by one of the podcast hosts, the banks take away most of that Rs. 2k crore subsidy received (about ~80%) and very little is left for these app developers. The app developers aren’t happy about it considering they do most of the front facing work like UX development, and banks themselves benefit the most from a cashless ecosystem.

The podcast also talks about how a lot of new players who didn’t enter payment app space earlier may now want to enter. Apps like Zomato and Swiggy will want to become UPI payment providers themselves as it will help them recover the MDR incurred on the transactions. On the other hand, will some merchants and customers go back to hard cash again? In any case, there could be several ripple effects and unknown variables to this move which will come out only on 15th October - if this MDR framework gets implemented.

Discussion 0 comments · 6 points · pyeri · 2026-09-20
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.