Recharge & Bill Payments for Half a Billion Users
A complete overhaul of PhonePe’s highest-frequency product surface — making utility payments faster, clearer, and more reliable for users across India.
Plan discovery
Operators offered 100+ plans. Users had no way to quickly find the right recharge for their needs and budget.
Multi-operator complexity
Different UI logic for DTH, broadband, electricity, gas, and water — no unified mental model across bill types.
Failure recovery
Payment failures were opaque — users didn't know if their money was deducted or what to do next.
Repeat-user friction
No smart defaults. Repeat rechargers re-entered operator, number, and plan every single time.
Recharge is habitual — users do it the same way every time. The challenge is reducing the cost of that habit, not reinventing it. Research spanned diary studies, analytics, support-ticket analysis, and interviews from power users to first-time digital bill payers.
For most users, the ideal recharge is remembering what they did last time and doing it again in three taps.
Contextual prompt —
last recharge, one tap
Contact-first entry —
operator auto-detected
Clarity
Make 100+ plans navigable without overwhelming the user.
Plan Recommender
Surfaces "Best Value", "Popular", and "Unlimited" plans; filters by validity, data, price.
Plan Detail View
An expandable card showing OTT benefits, data quota, SMS, validity, and total cost.
Bill Amount Clarity
Outstanding amount, due date, and last payment shown clearly before any action.
Recommender — 100+ plans,
ranked & filterable
Benefits unpacked —
OTT, courses, cashback
Plan + payment —
one screen, one tap
Trust
Design the failure and edge-case states that make users feel safe.
Clear Failure States
Failures tell users immediately whether money was deducted, when a refund arrives, and what to do.
Pending State Design
Operators can take minutes to activate. Pending states with estimated times cut repeat support calls.
Transaction Receipt
A shareable digital receipt for every payment — amount, operator, account, timestamp, downloadable.
Circle load failed —
a clear retry, no dead end
Stale plan caught —
honest, immediate message
Plans down — manual
amount still works
Null search —
designed, not defaulted
Respect the habit
Habitual users have a set pattern. The design should accelerate it, not disrupt it.
Fail gracefully
Utility payments fail. Design the failure state as carefully as the success state.
Smart defaults over effort
Every input that can be remembered should be. Cognitive load is the enemy of conversion.
Unify without homogenising
Mobile, DTH, electricity, and gas have different flows — but one mental model.
Frequency demands efficiency
When users do something every month, one extra tap costs real time over a year. The math on removing a tap from a 100M-user flow is staggering.
India’s diversity is a constraint
A first-time bill-payer in rural Bihar and a power user in Bengaluru share the same screen. That tension forces the truly universal pattern.
Operators are unpredictable partners
Design must absorb operator delays, API timeouts, and activation windows outside PhonePe’s control — and never let the user feel it.