India’s financial inclusion strategy set out to close the access deficit – and by most administrative measures, it has delivered. Public transfers now move at a historic scale, and account ownership is approaching saturation. Yet the architecture of inclusion has been optimised for delivery, not retention.
What remains under-designed is what happens after the credit arrives. The system moves money efficiently, but does little to help it stay. If inclusion is to translate into resilience, the system must be designed not only to move money efficiently, but to help it stay.
An Architecture Calibrated for Delivery
This calibration toward delivery is visible in the architecture itself. More than 400 direct benefit transfer programmes operate nationwide, with 327 centrally reported schemes on the government dashboard. In FY 2025–26 alone, ₹5.82 lakh crore flowed through 552 crore Direct Benefit Transfer (DBT) transactions; cumulatively, transfers have exceeded ₹49 lakh crore. Digital identity, interoperable payments, and near-universal account ownership have produced one of the world’s largest state-led payment systems.
At this scale, public transfers have become a regular feature of household financial flows. For millions of low-income households, public transfers are now the most predictable inflow in the liquidity cycle. The more consequential question is what happens once the credit lands. Field studies show that beneficiaries often withdraw DBT funds in full or near-full amounts shortly after credit, particularly where Aadhaar Enabled Payment System (AePS) cash-out is readily accessible.
The persistence of cash reinforces this pattern. Even as UPI volumes surge, ATM withdrawals remain steady at roughly ₹33 trillion annually. Digital adoption has expanded, yet the preference for holding cash persists.
These patterns reflect the incentives embedded in the architecture. A system calibrated to move funds efficiently will naturally produce high circulation, not accumulation. Delivery is maximised; resilience is incidental.
Resilience Requires Design
Can the same system that performs delivery with precision embed resilience with equal intent? Only if retention is designed with the same discipline as credit.
Financial inclusion policy has long assumed that access leads to usage, and literacy to prudent behaviour. Behavioural evidence suggests otherwise. Habit often precedes understanding, and structure precedes habit.
Evidence from savings programmes that introduced default enrolment and automatic contribution increases shows that modest adjustments in choice architecture can materially raise participation, even when individuals remain free to opt out. When prudent behaviour is embedded rather than optional, outcomes shift.
For public transfers, the implication is direct. If balances must be actively preserved while withdrawal is effortless, funds will pass through. Embedding even small default allocations toward savings would align the architecture with resilience rather than relying on individual deliberation. Delivery is engineered; retention must be engineered as well.
Even under conditions of income volatility and frequent shocks – where immediate liquidity is rational – small precautionary buffers matter. Transparent default allocations would not dictate behaviour; recipients remain free to opt out. The design question is whether the architecture makes resilience easier, or leaves it entirely to deliberation under stress.
Retention Requires Trust
Retention presumes confidence. Even a well-calibrated savings default cannot deepen resilience if users doubt that balances are secure or reversible. Trust is not an adjunct to inclusion; it is a precondition for durability.
Survey evidence shows that past experiences of online fraud significantly reduce continued digital payment usage. One failed transaction without visible recourse can outweigh dozens of seamless ones. For households operating at tight margins, small losses loom large – not merely financially, but psychologically.
Governance architecture must therefore ensure two things: that balances left in digital accounts remain secure, and that errors or fraud can be reversed quickly. Clear liability norms, time-bound grievance resolution, transparent fee disclosure, and accessible escalation pathways are structural supports for retention.
People will keep money in digital accounts only if they know problems can be corrected quickly and predictably.
When recourse is slow or opaque, precaution will default to cash. Behavioural design can encourage retention, but without trust in the system, money will not stay.
From Reach to Resilience
What gets measured determines what the system is built to optimise. The next phase of financial inclusion requires metrics that capture durability.
One simple indicator could reveal more than aggregate transfer volumes: how much of a transfer remains in the account seven days after credit. Retention after transfer would signal whether the architecture is shaping behaviour rather than merely moving money through the system.
The first phase of financial inclusion proved that reach can be scaled. The next phase will depend on whether that same architecture can also sustain resilience.
