The birthday dinner
One friend paid the restaurant bill, calculated everyone’s share and posted the amounts and UPI details in the group. Some paid at once, others forgot. The organiser kept checking payments and reminding people.
A personal concept project for WhatsApp UPI
Groups already talk about money in WhatsApp, then settle it in other apps, because paying faster was never the problem. Organisers still work out shares, match screenshots and chase people one by one. This concept brings that coordination into the chat.
Someone I spoke to had money outstanding for two months. Not because they didn’t know how to send a payment request, but because asking again felt awkward. Eventually, they stopped following up.



The hero
Who is this project for?
Every group has one. After the dinner, the farewell or the trip, one person pays up front and then becomes the group’s accountant: working out shares, posting UPI details, checking bank notifications and reminding people. I started by asking friends to walk me through the last time they collected money from a group.
One friend paid the restaurant bill, calculated everyone’s share and posted the amounts and UPI details in the group. Some paid at once, others forgot. The organiser kept checking payments and reminding people.
A UPI ID shared in the group, bank notifications checked one by one, payments matched against screenshots and a manual list of contributors, all while the chat filled up with confirmations.
Money stayed outstanding for two months. Sending a request wasn’t the hard part. Asking again was. In the end, they stopped following up.
The second person in this story is the contributor: someone who already has a UPI app they like and no strong reason to change it.
The problem
What was stopping them?
WhatsApp is where groups already talk about money, yet most settle it somewhere else. Everyone has a UPI app, a QR code or a UPI ID, so a faster payment gives them no reason to switch. What breaks is everything around the payment: working out who owes what, collecting it, knowing who has paid and following up without nagging. That work lives in scattered messages and screenshots, and the person who paid ends up doing all of it.
I started with “How can I make WhatsApp UPI easier to use?” and ended up asking “What would actually make someone want to use it?”
The stakes
Why did it matter?
For the people in the group, the cost is money stuck for weeks, awkward follow-ups and a chat full of payment noise. For WhatsApp UPI, it’s whether the feature earns a place in people’s habits at all. I framed success around four goals.
Can people find the feature at the moment they need it?
Can an organiser set up and track a group payment without screenshots?
Is there a reason to come back to WhatsApp for the next payment, not just the first?
Do people understand what WhatsApp handles, and what it doesn’t?
A note on evidence. My research was informal: conversations with a small number of friends. It shows a pattern worth investigating, not a statistic about every WhatsApp user.
The guide
Where do I come in?
This is a personal concept project. I’m Kartik, a UX designer, and I worked on it alone: interviewing friends about their last group collection, mapping the flow, designing the screens in Figma and taking the idea to a senior product designer for critique. I’m not affiliated with WhatsApp or Meta, and the project uses no internal data.
The journey
What did I do?
Two smaller signals stayed with me: some people would rather receive a QR code than go through a request flow, and one person was annoyed when a payment app opened its scanner automatically. Payment screens should help people do what they came to do, without extra steps.
The turning point
What changed the direction?
Why would someone type ₹500 expecting a payment menu to appear? And if every number could trigger it, wouldn’t it become intrusive?
Why would someone trust WhatsApp with payments?
I had been optimising for fewer steps. The critique showed I’d skipped the harder work: getting people to discover the feature, understand it and trust it. A clever shortcut isn’t useful if nobody knows it exists, and an automatic one is annoying when it appears in the wrong place.
I wasn’t designing a payment flow anymore. I was designing a behaviour.
The solution
What did I made?
The main flow, told as one story: an organiser who paid for dinner, and a contributor who receives the request. Each step shows the real screens, what the user is thinking, and the decisions behind them.
Step 1
What they’re thinking
“Wait, I can do this right here?”
Design decisions

Step 2
What they’re thinking
“Do I want to pay, request or split?”
Design decisions

Step 3
What they’re thinking
“I just want to send Rahul his ₹500.”
Design decisions



Step 4
What they’re thinking
“I paid ₹3,000. I don’t want to do the maths or chase six people.”
Design decisions


Step 5
What they’re thinking
“Who still hasn’t paid, and do I really have to ask again?”
Design decisions



Step 6
What they’re thinking
“Karan sent a request. I’ll pay, but I’m not switching apps for ₹500.”
Design decisions



These are the choices where I had real alternatives, and what I weighed before picking one.
Typing ₹500 opened Pay and Request. Hidden, and intrusive if every number triggers it. Replaced by the “/” menu.
Reading the chat to offer a payment would save a tap but add ambiguity. I kept the user in control of when a payment starts.
Replaced by reusing Split Expense, with the new interaction as a more convenient way in.
The resolution
What improved?
This is a concept, so I have no usage numbers and I won’t invent any. What I can show is how the experience changes for the organiser, and how I would find out whether it works.
Share of people who open the “/” menu after seeing the introduction card.
Share of group requests that are fully settled, and how long that takes.
How many manual reminders an organiser still has to send.
Where people drop off between the confirmation card and the PIN screen.
The reflection
What did you learn?
I assumed fewer steps would drive adoption. The conversations pointed to the work around the payment: organising, tracking and following up.
Finding Split Expense made me ask whether I needed to build anything new, or just connect existing pieces so people can discover them.
Two questions from a senior designer exposed the gaps I hadn’t looked at: discoverability and trust.
I learned to separate what people told me from what I assumed, and a business goal from a user problem.