Same amount, same QR code but....
Only one makes you feel fully in control.
I tried sending ₹1,000 by scanning a QR code.
The QR was the same. But when the payment screen popped up, the design differences made me pause and write this post.
Here’s a quick UX teardown of the payment screen — Google Pay vs. Navi:
1) GPay displays the profile picture, name, banking name, and UPI ID across multiple lines. Navi simplifies it to one bold name and a clean UPI ID beneath. This clean hierarchy makes it easier to read and confirm details.
2) GPay shows the “Add note” field by default adds visual noise even when unused. Navi keeps it inactive until tapped, reducing clutter and helping users stay focused.
3) Navi shows the selected bank account with the last four digits.
GPay doesn’t, which can be confusing for users with multiple linked accounts.
4) Navi offers a “Check now” option to view your balance before paying. GPay skips this, leaving you to find out only after the transaction fails (or succeeds).
5) Navi uses a direct call to action: “Pay ₹1,000.” GPay shows a blue arrow icon is minimal, but less descriptive and not always intuitive.
When it comes to money, clarity builds confidence.
Minimalism is great until it makes users guess.
Kudos to the Navi team Ashutosh Banpal, Nitin Bramhankar, Deeksha Srivastava, Adhya Ayushi, Shristi Joshi, Aviral Garg, Laura Rejo, Shrayanth SS, Akshat Srivastava, Gangadhar Koppula and all for designing a payment screen that respects attention and earns trust.
ux userexperience navi gpay
This post was originally shared by on Linkedin.