01 · Support the existing habit
Remembered recharges and contact-first entry reduce repeated setup. Plan discovery remains available when the customer’s need has changed.
Entry 04 · PhonePe · Consumer · Tenure 2019—2025
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.
PhonePe ConsumerConsumer UXAndroid & iOSHigh Frequency
500M+
Total Platform Users
99%
India’s Postal Codes
40M+
Merchants
Leadership brief
Protect a familiar task when the service underneath is unreliable.
- My remit
- Product Design Manager for PhonePe recharge and bill-payment experiences.
- Product scope
- Repeat entry, contact and operator selection, plan discovery, payment and recovery from unavailable or stale plan information.
- Leadership contribution
- Treat the happy path and operator-dependent failure states as one experience, balancing speed for repeat users with clarity at the point of commitment.
Recharge is a repeat task, but the information behind it can change or fail to load. Faster entry only solves part of the problem. The product also needs an honest response when it cannot reliably identify a valid plan.
Decision in practice · Product experience
From the problem to the screen.
02 · Separate a recommendation from certainty
A plan can become stale after it is listed. The interface needs to explain that state before the customer mistakes an available card for a guaranteed offer.
03 · Treat fallback as a trade-off
The manual-amount screen allows continuation when a plan cannot be fetched, with a risk warning. Availability is preserved, but the information gap remains and needs to be visible.
Strategic decisions & trade-offs
What the direction needed to balance.
01Accelerate repetition without locking it in
Use last-recharge context and detected operator details to reduce effort, while keeping the plan and amount open to review.
02Organise choice around the decision
Show validity, data and price in scannable plans, with benefits available in detail. A large plan catalogue needs structure more than additional promotional emphasis.
03Make degraded service an explicit state
Design retries, stale-plan warnings and manual-amount fallback as distinct situations. A fallback is not equivalent to confirmed plan information, even when it allows the journey to continue.
01 — Overview
India’s highest-frequency payment surface.
01
Plan discovery
Operators offered 100+ plans. Users had no way to quickly find the right recharge for their needs and budget.
02
Multi-operator complexity
Different UI logic for DTH, broadband, electricity, gas, and water — no unified mental model across bill types.
03
Failure recovery
Payment failures were opaque — users didn't know if their money was deducted or what to do next.
04
Repeat-user friction
No smart defaults. Repeat rechargers re-entered operator, number, and plan every single time.
02 — Research
Understanding high-frequency behaviour.
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.
Key Insight
For most users, the ideal recharge is remembering what they did last time and doing it again in three taps.
01 · Nudge
Contextual prompt —
last recharge, one tap
02 · Pick
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.
03 · Browse
Recommender — 100+ plans,
ranked & filterable
04 · Detail
Benefits unpacked —
OTT, courses, cashback
05 · Pay
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 time to activate a recharge. Pending states distinguish processing from failure and explain what the user should expect next.
Transaction Receipt
A shareable digital receipt for every payment — amount, operator, account, timestamp, downloadable.
E1 · Fail
Circle load failed —
a clear retry, no dead end
E2 · Stale
Stale plan caught —
honest, immediate message
E3 · Degrade
Plans down — manual
amount still works
E4 · Empty
Null search —
designed, not defaulted
04 — Design Principles
Principles for utility-first design.
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.
Outcomes & learning
What the results establish.
Reported results include a 62% increase in repeat recharge rate, 71% successful retry-and-completion after failure and an 85% improvement in search-to-payment completion. The 71% figure is a completion level; the other two are reported changes. Platform reach is context, not a result of this redesign.
The leadership lesson is to define quality under imperfect conditions. A frequent financial task needs an understandable response when a dependency fails, as well as an efficient happy path.
05 — Outcomes
Impact across the highest-volume surface.
Repeat Rate
Failure Recovery
Task Completion
62%
Increase in same-user repeat recharge rate
71%
Users successfully retrying and completing payment after a failure
85%
Improvement in search-to-payment completion
Daily Active Users
Feature Discovery
+15%
Growth in daily active users across the recharge & bill-pay surface
+37%
Lift in users discovering plan browsing and bill-pay features
Reported outcomes across the redesigned recharge and bill-payment experience. Percentage changes and completion levels are different measures; these results do not isolate an individual component’s effect.
06 — Reflections
What I learned.
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 explain clearly what remains outside the app’s control.