Google Pay
A Case Study on the Google Pay "Money Tracker" Concept
Focus: FinTech, Micro-interactions, Cognitive load
Every month, millions of users open their bank statements only to find a digital graveyard of cryptic merchant names. "Paid ₹450 to Zomato_Vendor_99." Was that a business lunch? A late-night snack? Or a grocery run?
As a UX Lead, I realised that while UPI made paying instant, it made remembering impossible. We had solved for transaction speed, but we had accidentally created a "Cognitive Debt" for the user.
I began by observing users in their natural habitat. I saw people taking screenshots of their payment success screens. When I asked why, the answer was always the same: "If I don't snap this now, I'll forget what it was for by tomorrow."
Users didn't want a new "Expense App." They wanted Google Pay to have a memory.
I audited the current Payment Success screen and found a "Gold Mine" - The Opportunity Area. A large section of unused white space sat right between the transaction details and the "Done" button. This was the quiet moment where the user's attention was already captured.
The challenge was to add utility without adding friction. If I added a text box, users would ignore it. If I added too many buttons, I would violate Hick's Law and slow down the checkout line.
So I designed a set of "Intelligent Pills" instead. Using Google's Material 3 design language, three context-aware tags, Food, Shopping, Trip, sit directly in the thumb zone.
The AI twist came next: a predictive engine that does the thinking before the user has to. If someone's at a Starbucks at 8:00 AM, the "Food" tag is already highlighted. They just have to confirm it.
The design didn't end at the payment. I created a Spending Summary dashboard, tucked neatly into the Profile Menu. This transformed raw data into a visual narrative of the user's life.
Now, instead of a wall of text, the user sees: "You spent 40% of your budget on Food & Restaurants this month." Clarity achieved.
As a leader, I didn't just design screens; I designed a Product Roadmap.
This project reinforced my belief that the best design is often invisible. By utilising existing "empty spaces" and respecting the user's time, we can turn a simple payment app into a powerful financial ally.
Small changes. Big clarity.
"I want to master my money, not spend my life tracking it."
Rohan's days are a blur of back-to-back meetings, quick coffees, and Uber rides. He is financially conscious and tech-savvy, but he values his "mental bandwidth" above all else. He uses UPI for everything from a ₹20 chai to a ₹5,000 team dinner but his bank statement has become an unreadable mess of merchant codes that he no longer recognises by the weekend.
Goal: 25% of all transactions tagged within the first release cycle - the primary signal that users find the tap-to-tag worth the effort.
Reduction in time users spend digging through history to recall what a past payment was for - the secondary, supporting metric.
Phase 2 target: 90% of spends correctly categorized automatically via Merchant Category Codes, with zero manual tagging required.
"I tried manual expense trackers, but I always forget to log the data after the third day. It needs to happen at the moment of payment."
"Seeing 'Paid ₹450 to Merchant X' means nothing to me three days later. Was that my breakfast or a grocery run?"
"I take screenshots of successful payments to remind myself to log them later, but then my gallery just gets cluttered."
My approach followed a non-linear Double Diamond methodology, focusing heavily on the "Discover" and "Define" phases to ensure the solution was rooted in actual human behaviour.
I started by watching 10 power users move through their daily routines, and noticed a shadow behaviour: they weren't just paying, they were screenshotting the success screen afterward. Not for proof of payment. They were digital post-it notes, a way to remember what the expense was for later.
A look at PhonePe and Paytm explained why that habit existed. Both apps handle the transaction well, then leave the user with nothing for what comes after.
Mapping the user journey pointed to one clear friction point: every traditional expense app forces a context switch, leaving GPay to open something else entirely.
The fix didn't need a new screen. The Payment Success screen already had an "Opportunity Area", 300px of unused vertical space, and putting the solution there turned a passive screen into an active one.
This phase came down to Hick's Law: fewer choices, faster decisions. I wireframed three versions, a text input, a dropdown, and category pills, and the pills won outright. A single tap matched the "quick-tagging" habit people already have from Gmail or Instagram.
Tap targets stayed at a minimum of 48x48px, sized for one-handed use in transit, like tagging a cab fare while stepping out of the car.
The final output wasn't just a screen. It was a system, built entirely in Google's Material 3 Design System so Money Tracker feels like it grew out of the app rather than got bolted on.
A small "Micro-Confirmation" popup closes the loop: a quick dopamine hit of organisation that reinforces the habit of tagging.
A design is only as good as its impact, so the hand-off came with two numbers to track. Tagging Adoption Rate, with a goal of 25% of all transactions tagged, mattered most. Reduction in "Transaction Search" time within the app's history came second.
(The Friction)
(No Extra Steps)
My solution keeps the user within a single, continuous loop.
To help developers understand the "behind-the-scenes" logic, I mapped out the decision tree for the Smart Suggestion Engine.
The engine uses contextual signals (MCC codes, time, merchant) to intelligently suggest categories, reducing manual input while preserving user control.
I analyzed the top three players in the Indian UPI market to see how they handle post-payment context. While most focus on the transaction, Google Pay "Money Tracker" focuses on the user's financial life.
| Feature | Google Pay (Proposed) | PhonePe | Paytm |
|---|---|---|---|
| Primary Goal | Transaction + Context Remembers context, not just amounts |
Transaction Speed Fast payments only |
Ecosystem / Services Multi-service platform |
| Post-Payment Action | One-tap Tagging Instant categorization |
Ad banners / Scratch cards Distracting |
Rewards / Cross-selling Promotional focus |
| Expense Recall | High Categorized & searchable |
Low Merchant name only |
Moderate History search required |
| User Effort | Zero Friction One tap, done |
High Requires manual note |
High Requires external app |
| Design Approach | Minimalist / Integrated Clean, focused UX |
High-density / Busy Many options & promotions |
Super-App / Complex Multiple services integrated |
PhonePe and Paytm treat payments as isolated transactions. Google Pay's Money Tracker turns each one into a memorable, categorized event, building a financial narrative that grows over time instead of a pile of receipts.
This project was a study in intentional restraint. In a world where product teams are often pressured to add "more," I chose to focus on "better."
By identifying the Opportunity Area in the existing Google Pay flow, I demonstrated that we could solve a massive user pain point, Transaction Amnesia, without adding a single extra screen or a second of friction. That's Product-Led Design in practice: finding the path of least resistance to deliver the highest possible value.
Thank you for taking the time to walk through my design journey. As a designer who thrives at the intersection of Enterprise Strategy and Human-Centric UI, I am always looking for the next complex challenge to simplify.