Google Pay's contactless core mirrors the category: unlock, hold the phone to the terminal, get a confirmation. What distinguishes it, and unsettles it, is the app wrapped around that gesture. Google has repeatedly restructured the home surface, swinging between a clean wallet of cards and passes and a busier feed of offers, transactions, and people you have paid. The result is muscle memory that keeps getting disrupted across redesigns. At its best the transaction history is searchable and richly itemized, and storing boarding passes or loyalty cards beside payment cards is genuinely useful. The recurring complaint is identity confusion: overlapping payment products and rebrands leave users unsure which app does what. The tap works; the container around it has never settled into one idea.
Notable UX patterns
Flows
Flows for Google Pay are being captured
We haven't taken Google Pay apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.
Request a UX auditTeardowns
Teardowns of Google Pay are coming
We haven't published a written teardown of Google Pay yet. Explore related topics, or request an audit.
Request a UX audit