Product
India Solved Payments. America Still Waits Days for ACH.
In India I can pay a merchant or a friend across different apps in real time. In the US, a bank transfer over ACH can take days. I think the gap says more about choices than technology.
UPI vs ACHACH vs RTPUPI vs RTP
A US bank transfer over ACH can take days to clear. In India, UPI moves money in real time between bank accounts, merchants, and even across different UPI apps. Same century, same kind of phones, very different experience.
I have worked on banking products in more than one country, and this is the contrast that keeps coming back in product reviews. This post is my take as of 2024, so read the claims as a snapshot. Here is the argument I want to defend: the gap between the two systems says more about decisions and adoption than about engineering. I will say where I am guessing.
What is ACH, and why is it so slow?
ACH (the Automated Clearing House) is the workhorse of electronic payments in the US. It is reliable and cost-effective. It is also notoriously slow, and transfers can take days to clear.
That tradeoff is the whole story of ACH. If you are a product manager picking a rail, ACH gives you dependability and low cost, and you pay for it with the user’s patience. Anyone who has waited for money to arrive knows the feeling.
What is RTP, and why isn’t it everywhere?
Real-Time Payments (RTP) is the modern US alternative, and it offers instant transactions. As of 2024 it is still gaining traction and has not reached universal adoption.
That last part matters more than the technology. A fast rail that not everyone can use does not fix the experience for the person on the other end. So the PM’s job in the US becomes a balancing act: reliability of ACH on one side, speed of RTP on the other, and a decision about which one suits your use case and your audience.
What does India run on instead?
India has several rails, and they do different jobs:
| System | What it does |
|---|---|
| IMPS | Instant transfers, similar to RTP in the US |
| NEFT | Larger transactions, varying speeds and processing times |
| RTGS | Larger transactions, varying speeds and processing times |
| UPI | Mobile-first, real-time transfers between bank accounts, merchants, and across different UPI apps |
UPI is the one that changed daily behaviour. Its strengths are interoperability, ease of use, and wide adoption. I keep coming back to the interoperability point. Being able to pay across different apps is a design decision about how the system is shared, and I think it matters as much as the speed.
So is it a code problem or a policy problem?
This is where I take a side, and where I want to be careful about what I can prove.
The technology for fast payments exists on both sides. The US has RTP and it is instant. What the US does not yet have, in my reading, is the broad adoption that makes instant the default. The source of that, I would guess, is how the market is organised: a fragmented set of payment systems where no single choice reaches everyone. India’s experience points the other way. A mobile-first system that works across apps and reaches many users became the common path.
I cannot tell you from my own experience exactly which regulatory or commercial decisions made the difference, and I do not want to pretend I can. My claim is smaller. If the same speed is available in both countries and only one has made it normal, the bottleneck is not the code. Engineers can build a real-time rail. Someone else has to get everyone onto it.
How does this change the product work?
The user experience gap is stark. In the US, the choice between ACH and RTP often comes down to speed against cost. Indian users have many options, and UPI leads on convenience and speed.
That produces very different product priorities:
- In the US: educate users about RTP, or offer faster payment options at a premium. Decide per use case, because the default rail is slow.
- In India: UPI integration is a must-have. Differentiation moves to additional features and value-added services built on top of UPI.
I find the second one more interesting to work on. When the rail is a given, you compete on what you build on it. When the rail is the problem, you spend your roadmap explaining and routing around it.
What problems remain on each side?
Neither system is solved. In the US, fragmentation across payment systems and slow adoption are hurdles. In India, UPI is dominant, but security and serving the unbanked population remain critical challenges.
Those gaps are where the product opportunities sit. Solutions that bridge the holes in existing systems, improve user experience, and meet the demand for faster, more convenient payments have room to grow. I expect more real-time and mobile-first work, with security getting more attention, though that is a forecast and not a fact.
What should a payments PM take from this?
- Ask which rail your users are actually on before you design the flow. A fast option nobody has is not an option.
- Treat interoperability as a feature. It may be the thing that decides adoption.
- In a market with a slow default, price speed honestly and tell users what they are buying.
- In a market with a fast default, put your effort into what sits on top of the rail.
- Hold your claims about why systems differ loosely. I do.
One thing I still have not resolved: how much of the US gap closes by itself as RTP spreads, and how much needs a push from outside any single product team. I do not know yet.