What UPI Teaches the World About Human-Centred Design at Population Scale

When international agencies discuss financial inclusion, the conversation usually starts with a familiar toolkit: microcredit schemes, banking correspondents, subsidised accounts. India tried all of these. What finally moved a nation of over a billion people — a majority of them operating in the informal economy — onto real-time digital payments was not a banking product at all. It was a piece of design.

The Unified Payments Interface now processes billions of transactions every month, from vegetable carts to venture-funded startups, and has become the reference model for digital public infrastructure worldwide. Understanding why it worked is one of the most valuable design lessons available to anyone building systems for emerging markets.

Lesson One: Design for the Actual Economy, Not the Documented One

Traditional financial products assume a formal user: salaried, documented, bank-literate. UPI's designers assumed the opposite — a chaiwala with a smartphone but no card machine, a customer with money but no patience for two-factor card flows. The interface collapsed the transaction to its human essence: scan, amount, PIN, done. No card networks, no merchant onboarding fees, no minimum infrastructure beyond a printed QR code.

This is the informal economy designed for, not designed around. The QR code taped to a fruit cart is arguably the most successful piece of service design of the last decade.

Lesson Two: Interoperability Is a Human-Centred Decision

The single most consequential design choice in UPI was invisible to users: any app could talk to any bank. This was not a technical inevitability — it was a deliberate rejection of the walled-garden model that dominates Western fintech. The user's mental model ("I send money to a person") was allowed to override every institution's preference for lock-in.

For development agencies designing national systems — identity, health records, benefit transfers — this is the deepest lesson. Human-centred design at population scale is mostly about the architecture users never see.

Lesson Three: Zero Cost Is a Feature, Not a Subsidy

Keeping person-to-merchant transactions free was treated by critics as economically naive. In design terms, it was the adoption mechanism. For a vendor earning a few hundred rupees a day, even a one per cent fee is a reason to stay with cash. Removing friction for the most constrained user — rather than the most profitable one — is precisely the inversion that Western frameworks, built around monetisable user segments, struggle to make.

Lesson Four: Trust Travels Through People, Not Brochures

UPI's adoption curve was carried by observation and mimicry within dense social networks — the shopkeeper who saw the neighbouring shop get paid instantly, the family member who taught three others. Systems designed for informal economies must be legible enough to be taught peer-to-peer, because that is how trust actually propagates where institutions are weak. Simplicity is not a UX nicety in these contexts; it is the distribution strategy.

The Transferable Pattern

Strip away the specifics and a pattern emerges that applies from Nairobi to Jakarta to São Paulo: design for the most constrained real user, not the average documented one. Make interoperability a first principle so the system serves people rather than institutions. Remove cost friction where adoption matters most. And make the system simple enough that users become its trainers.

This is the design tradition India's institutions have been refining for decades — a tradition rooted in the NID legacy of designing for scarcity and social complexity, which HCD Institute carries forward in its education, research, and advisory work. UPI is not an anomaly. It is what happens when that tradition is applied with state-level ambition.

For governments, multilateral agencies, and NGOs building the next generation of public systems in emerging markets, the question is no longer whether human-centred design works at this scale. UPI settled that. The question is whether you are learning it from the contexts where it was proven.

This article is part of HCD Institute's global case study series on designing for complexity, constraints, and emerging markets.

Mathew Sebastian

Mathew is a mentor at HCD Institute, where he has led the movement to democratise design thinking in India since 2011. An alumnus of NID Ahmedabad and a Fellow at IIT Hyderabad's Design Innovation Centre, he brings over 18 years of experience across design strategy, education, and public policy.
He has advised governments and institutions including the Government of Kerala, Bihar's Ministry of Industries, the Andaman & Nicobar Administration, and Nordic diplomatic missions — with a curriculum formally adopted by Mahatma Gandhi University.