By Sam Kummary
Tailor in India

Digital public infrastructure (DPI) can connect millions of people to essential services, including digital payments, identity and government programs. But widespread adoption does not necessarily mean everyone can use these services successfully.

What does it take to make DPI genuinely people-centered? Start with the people most likely to be excluded, and design systems that work for them from the beginning.

Scale Does Not Guarantee Access

Digital payment systems have demonstrated that they can operate at enormous scale. India’s Unified Payments Interface (UPI), for example, grew approximately 13,000 times over 10 years. Rwanda’s eKash, a national interoperable payment system built on Mojaloop, grew its active accounts from 2.03 million to 10.3 million in one year.

Other Mojaloop implementations are also demonstrating the potential of interoperable payment infrastructure, including Bantaba 2.0 in The Gambia, and Liberia’s national instant payment system.

These results demonstrate what DPI can achieve. However, scale alone does not establish whether a system works for everyone. A system’s overall success rate can conceal access problems for particular groups.

Meet Asha

Asha is a 38-year-old tailor in rural India. She needs to pay ₹8,000 to a fabric supplier in Hyderabad, who will ship her materials only after receiving payment.

Asha speaks Telugu, shares an entry-level phone with her son, has intermittent mobile data and fingerprints worn down by years of work. Although she theoretically has access to digital services, common design assumptions could prevent her from completing a payment.

Design for Imperfect Conditions from Day One

Let’s follow Asha’s payment through five stages: accessing the system, making the payment, completing the transfer, receiving confirmation and seeking help if something goes wrong.

Each stage presents a potential barrier — and an opportunity to address it through better design.

1. Access: Provide Alternative Ways to Authenticate

If Asha’s fingerprint fails, she needs another way to verify her identity. Options could include a one-time password (OTP), iris or facial recognition, or assistance from an authorized agent.

The principle is to avoid making one form of authentication the only way into an essential service.

2. Pay: Make it Work Without Internet

An application that requires mobile data is not practical for Asha. India’s UPI 123PAY service offers an alternative through missed calls and interactive voice response (IVR) — an automated telephone system that guides users through voice menus.

3. Transit: Protect Payments when Connections Fail

A dropped connection shouldn’t result in money being deducted without reaching the recipient, or the same payment being processed twice.

Asynchronous APIs (application programming interfaces) enable payment systems to handle unreliable networks through retries and synchronization when connectivity returns, preventing failed or duplicate transactions.

4. Confirmation: Communicate in the User’s Language

Payment confirmations and transaction status updates should be available in the user’s preferred language and, where appropriate, through voice as well as text.

For Asha, receiving a Telugu voice confirmation that her supplier has been paid is much more useful than an English-language SMS she may not understand.

5. Getting Help: Resolve Problems Remotely

When a payment fails or a problem arises, users should not have to travel to a distant bank branch to seek assistance. A phone-based support process should provide a named person responsible for the issue and a clear resolution deadline.

Build User Protections into the Payment Infrastructure

Inclusive payment systems need protections built into their underlying infrastructure. The Level One Project Principles provide a foundation for safe, interoperable payment systems through several key requirements:

  • Push-only payments: Transfers require the payer’s explicit authorization; funds cannot be withdrawn without consent.
  • Irrevocable payments: Completed payments are final. Payee details and fees must be clearly disclosed and agreed upon before authorization.
  • Asynchronous APIs: Systems must handle unreliable network connections and complete transactions safely without continuous connectivity.

Other principles include open-loop participation (allowing different financial service providers to connect), same-day settlement, proportional know-your-customer (KYC) requirements, shared fraud protection and keeping digital payment costs at or below the cost of cash.

Together, these principles establish consistent protections at the infrastructure level rather than leaving individual providers to implement them independently.

Treat Exclusion like a System Outage

Even well-designed payment systems experience failures. What matters is how quickly operators identify, address and learn from them.

Rwanda’s eKash has recorded an average transaction success rate of 97.8%. At 28.9 million monthly transactions, that would leave approximately 640,000 transactions incomplete — an illustrative figure that underscores why overall averages can mask exclusion.

Operators should treat exclusion as seriously as a technical outage, with four steps:

  1. Detect: Monitor transaction success rates across different user groups, not just overall averages.
  2. Assign ownership: Give each issue a named owner, a severity level and a resolution deadline.
  3. Fix: Make design changes and test them with affected users.
  4. Publish: Report what failed, who was affected and what changed.

Accountability also requires accessible grievance channels and alternative service options for users, independent data access and audits for civil society and researchers, and inclusion standards established and assessed by regulators and ministries before and after deployment.

What Success Looks like for the Last Person First

People-centered DPI is about more than making digital services available. It means designing systems that people can access, understand and trust, regardless of their circumstances. That requires building inclusion, reliability and accountability into the infrastructure from the outset — and measuring success by whether the services work for everyone, including those most likely to be left out.