Improving WhatsApp Pay Adoption in India: Part One
- Tarun Rai
- 2 days ago
- 4 min read
Overview
WhatsApp Pay sits on top of one of the stickiest habits in India; opening WhatsApp. However, it's still a secondary feature tucked behind an icon. This case study lays out observations, over which three testable hypotheses are formed. The goal is to improve P2P (peer-to-peer) payment adoption on WhatsApp Pay. Each hypothesis comes with a concrete feature suggestion and a mockup.
What is WhatsApp Pay
WhatsApp Pay is WhatsApp's built-in UPI (Unified Payments Interface) feature that lets users send and receive money directly from a chat, without switching to a separate banking or payments app. It launched in India in 2020 after regulatory approval from the NPCI, riding on the same UPI rails as Google Pay, PhonePe, and Paytm.
Peer-to-peer messaging and payments
There are two reasons why targeting WhatsApp’s core chat feature makes sense as the lever for P2P adoption.
1. Habit - People are already opening WhatsApp for communication multiple times a day. Anything that piggybacks on an existing habit has a lower activation barrier than something asking users to form a brand-new one. 90% of India's mobile internet users use WhatsApp frequently. That's an enormous surface area of daily attention already captured by the app.
2. Familiarity - Users already know WhatsApp's layout, its color language, its icons, and its interaction patterns. A payment experience that borrows this visual vocabulary has less to teach the user than one built from scratch.
Together, habit and familiarity mean the fastest path to P2P payment adoption isn't a better payments app, it's making payments feel like a natural extension of WhatsApp’s messaging feature.
User Problem & Assumptions
User Problem: Users don't consistently think of WhatsApp as a payment platform when they have a need to send or receive money.
Observations/ Assumptions:
WhatsApp currently surfaces the pay feature passively, through an icon inside the attachment menu. This is probably deliberate. The app's primary job is chat, and WhatsApp may not want payments to compete with that for attention.
The payments dashboard is minimal and does not add much benefit to the user.
Currently the payments feature is more about waiting for users to organically notice and make use of it. A strong value-add is missing that could drive payments on WhatsApp.
We're going to use the above observations to further investigate how these may be adding friction for users to make payments via WhatsApp pay.
Hypotheses
Based on the above observations, we were able to frame the hypotheses to test our assumptions.
Hypothesis 1: Visibility drives recall
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.
The current design underplays the payment feature. We will try to improve the visibility of the WhatsApp pay feature without hampering the flow of the messaging functionality of the app.
Two feature suggestions follow from this:
A long-press shortcut on the WhatsApp app icon that surfaces a "Quick pay" option, so a user can jump straight to sending money without opening a chat first. The same pattern people already use to access frequent chats on WhatsApp.
A more prominent, labelled payments entry point in the main navigation, so the feature reads as a first-class part of WhatsApp (like Chats or Calls), not a hidden utility.
Hypothesis 2 — A meaningful payment dashboard
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.
Right now the Payments page with a ₹ icon has minimal features attached to it. A transaction log, access to limited payment services, not adding enough value. The idea here is to give people a reason to open it even when they're not actively paying someone. Concretely, the dashboard could include:
Transaction history with weekly / monthly / yearly filters.
Comparisons to previous months, so spending trends are visible at a glance.
Shared payments pending receipt of money others owe the user
Upcoming payments pulled from chats of things like insurance premiums, internet bills, or rent that are already discussed in conversations, surfaced as reminders before they're due.
Hypothesis 3 — Split expense, built into the thread
If we introduce a "Split expense" feature, then users will use WhatsApp Pay to share expenses, which will lead to increased adoption.
This targets a very specific, very common moment: a group chat after a trip, a dinner, or a shared bill, where someone has to do the calculation and go through the awkwardness of asking each one to pay. Today, that math and that follow-up happens outside WhatsApp. Usually on a separate splitting app, even though the conversation itself is happening on WhatsApp. Making Split expense a prominent, tightly-integrated chat feature closes that gap and gets users familiar with the pay feature.
Part Two: Validating the hypotheses
Everything above is a hypothesis, not a conclusion. The next step is testing it against real behavior and not just intuition. The plan is to run a survey with real WhatsApp + UPI payment users to:
Answer the underlying assumption directly — do people genuinely forget WhatsApp Pay exists because of low visibility, or is the barrier trust, habit with another UPI app, or something else entirely?
Pressure-test each hypothesis independently, since they're not mutually exclusive and probably don't have equal impact.
Gather clarity on what people actually want — which of the proposed dashboard elements (comparisons, pending dues, upcoming bills) people would actually use versus which sound nice in theory but wouldn't change behavior.
To do this we’ll be running a survey to test out the three hypotheses stated in this case study. The responses should make it possible to rank the three hypotheses by expected impact, rather than pursuing all three with equal investment.