Improving WhatsApp Pay Adoption in India: Part Two
RECAP - PART ONE Part One framed the problem: 90% of India's mobile internet users are on WhatsApp daily, yet WhatsApp Pay holds a negligible share of the UPI market. It proposed three testable hypotheses - a. a more visible entry point (Quick Pay + a Payments tab), b. a personalised payments dashboard, and c. an in-thread Split Expense feature. Read Part One here for the full problem framing and mockups. |
Introduction
Everything in Part One was a hypothesis, not a conclusion. In there, I've listed informed assumptions about why WhatsApp pay has underperformed despite having a strong user base.
Part Two puts those assumptions in front of real people. I ran a survey with 40 WhatsApp and UPI users to pressure-test all three hypotheses independently, ranked them by expected impact, and found out which of the proposed features are worth taking forward.
The three hypotheses under test:
H1 - Visibility drives recall: improving the visibility of payments option and its dashboard will improve top-of-mind recall and adoption.
H2 - A meaningful payment dashboard: in-depth spending data in one place will motivate users to route payments through WhatsApp Pay.
H3 - Split expense, built into the thread: a native split-expense feature will get users paying through WhatsApp.
Who we surveyed
40 WhatsApp and UPI users completed the survey. A quick profile of the sample:
90% were between 25 and 44 years old (25–34 years: 40%, 35–44 years: 50%)
92.5% make peer-to-peer UPI payments daily, weekly, or monthly. This is a habitual behaviour for almost everyone surveyed, not an occasional one.
With multi-select enabled, 37 of the 40 participants currently use Google Pay as their only or one of their payment apps; only 3 chose WhatsApp payments among the UPI apps they actively use. A small, real-world echo of the market-share gap Part One opened with.
Hypothesis 1 — Visibility Drives Recall
HYPOTHESIS If we improve the visibility of Pay and the payments dashboard, then users will have better top-of-mind recall, which will lead to improved WhatsApp Pay adoption. |
Expected outcome & threshold |
Expected outcome: 60% of participants are unaware of, or want better visibility of the payments feature; 50% would be inclined to pay via the proposed Quick Pay shortcut or a prominent entry point. |
Success: >60% want better visibility AND >50% want either proposed feature |
Iterate feature: >60% want better visibility AND >30% want either proposed feature |
Below that: major rethink |
What we found
95% are aware WhatsApp Pay exists, but only 28% have ever actually used it. That's a wide awareness-to-usage gap.
68% rate finding the Pay option as easy (4 or 5 out of 5); only 6% call it hard to find (1 or 2 out of 5).
43% show interest in the "Quick Pay" shortcut and 38% in a dedicated Payments tab. This is below the 50% success bar, though above the 30% iterate line.
Outcome
The premise doesn't hold up. People already know WhatsApp Pay exists and can find it without much trouble. Nowhere near 60% are asking for better visibility, so the hypothesis fails its own threshold before the feature-interest numbers even come into play. The real gap seems to be after discovery: 95% are aware but only 28% ever transacted.
VERDICT - DISPROVED Visibility is not the bottleneck. At this stage I’d deprioritize Quick Pay and the Payments tab. |
Hypothesis 2 — A Meaningful Payment Dashboard
HYPOTHESIS If we provide in-depth UPI expense data in one unified location (the WhatsApp Pay dashboard), then users will be motivated to route all their UPI payments through WhatsApp Pay to get the benefit of tracking everything in one place, which will lead to increased adoption. |
Expected outcome & threshold |
Expected outcome: 60% of participants would be more likely to use WhatsApp Pay if one or more of the four proposed dashboard elements existed. |
Success: >60% want a personalised dashboard |
Partial success: >40% want a personalised dashboard |
Below that: rework the assumption |
What we found
Across 99 total selections on the multi-select question, Spend Summary took the largest share (30%), followed by Upcoming Bills and Recent Transactions (24% each) and Pending Dues (21%).
When forced to pick just one must-have element, Spend Summary was again the clear favourite (38% of the 37 who answered), followed by Upcoming Bills (32%), Recent Transactions (22%), and Pending Dues (8%).
46% rated their likelihood of using WhatsApp Pay 4 or 5 out of 5 if the dashboard shipped with these features. Just short of a majority, but well past the partial-success line.
Outcome
Against the pre-registered threshold, this clears partial success(46% versus a 40% bar). Spend Summary is the standout element on both the multi-select and forced-choice questions, while the other three elements split the remaining preference fairly evenly. This gives a meaningful signal to explore further, just not a decisive one.
VERDICT - PARTIAL SUCCESS Worth validating further, scoped down. Starting with Spend Summary, the single highest-conviction element before investing in the full dashboard. |
Hypothesis 3 — The Split Expense Feature
HYPOTHESIS If we introduce a "Split expense" feature, then users will use WhatsApp Pay to share expenses, which will lead to increased adoption. |
Expected outcome & threshold |
Expected outcome: 60% of participants would be more likely to make WhatsApp payments if it had a "Split Expense" feature. |
Success: >60% want the split expense feature |
Partial success: >40% want the split expense feature |
Below that: rework the assumption |
What we found
Splitting group expenses is a recurring moment, not an edge case. 33% do it weekly or monthly, and another 55% do it occasionally. That's 88% of respondents combined.
28% participants said they manually track the splitting, while another 28% use an app called Splitwise to manage and split group expenses.
22% participants do not track group expense splits at all.
11% track these splits on WhatsApp messages itself.
Outcome
Hypothesis 3 clears the success bar with 68% participants saying they'd actually be likely to use WhatsApp Pay for group splits if it existed. The pain points give us added context going ahead defining the feature.
VERDICT - VALIDATED The strongest result of the three. Move Split Expense into prototyping and a real-user beta test. |
Ranking the Three Hypotheses
The survey doesn't just validate each hypothesis, but also ranks them by expected impact. This helps me prioritize my next steps towards the goal.
Hypothesis | Verdict | Headline metric | Recommendation |
H1 - Visibility drives recall | Disproved | Only 28% have ever used WhatsApp Pay despite 95% awareness and 68% rating it easy to find. | Deprioritize. Visibility isn't the blocker. |
H2 - Meaningful dashboard | Partial support | 46% say they'd be more likely to pay via WhatsApp with a personalised dashboard; Spend Summary is the standout element. | Validate Spend Summary first. |
H3 - Split expense feature | Validated | 78% want the feature; 68% say they'd likely use WhatsApp Pay for group splits because of it. | Move straight to prototyping and a beta test. |
Next Steps
With Hypothesis 3 validated, the next step is testing the Split Expense feature with real users. A beta test is the most practical option. WhatsApp's user base makes it possible to reach a meaningful slice of real users quickly. During the beta, I'd verify:
Whether the success metrics defined for H3 are actually being met in live usage.
How people interact with the new workflow. Where they hesitate, and where it feels obvious.
Edge cases: uneven splits, someone not on WhatsApp, disputed amounts, partial payments.