Redesigning Google Pay’s
Onboarding
Identifying friction in Google Pay's first-time setup flow and proposing a redesign that improves completion rates by reducing steps, front-loading value, and eliminating context switching.
01 — Current state
The existing
onboarding flow
Google Pay's current first-time setup spans 8 steps from app launch to first payment. Friction tags highlight where users tend to drop off.
App download & launch
User installs from the Play Store or App Store. No feature preview before the commitment to download.
No value previewGoogle account sign-in
Sign in or select an existing Google account. Smooth for returning users, a full flow for new Google users.
Low frictionTerms & privacy wall
A full-screen legal text block. No plain-language summary. Users must agree without context or clarity.
Cognitive overloadManual card entry
Card number, expiry, CVV, billing address — all typed in. Camera scan exists but is not the default CTA.
High input frictionBank SMS verification
User must leave the app to retrieve an OTP from their SMS inbox. No auto-read in all regions.
Context switchingScreen lock setup
Users without a device PIN or biometric hit an unexpected gate mid-flow before they can continue.
Unexpected gateNFC & default payment prompt
Two consecutive system dialogs: enable NFC, then set Google Pay as default. Back-to-back permission fatigue.
Permission fatigueHome screen — no guidance
User lands on the app with their card visible but no tutorial, no nearby stores, no "aha moment".
Empty arrival02 — Problem analysis
Six pain points
causing drop-off
Severity rated 1–3 dots. Three critical issues account for the majority of onboarding abandonment: manual input, context switching, and empty arrival.
No value hook at launch
Users commit to downloading without seeing what they get. There's no "here's why this is useful" moment — the flow jumps straight to setup.
Full T&C wall
Dense legal text with no plain-language summary. Users either abandon or skip-read — neither outcome builds trust or informed consent.
Manual card entry as default
Typing a 16-digit card number on mobile is error-prone and slow. Camera scan exists but is buried as a secondary option — a critical UX inversion.
SMS context switching
OTP verification forces users to leave Google Pay, open their SMS app, memorise the code, and return. Every app switch is a drop-off risk.
Unexpected security gate
Requiring a screen lock mid-flow — without prior warning — surprises users and feels like a trap. It breaks the setup momentum at a critical moment.
Empty arrival state
After all that setup, users land on a home screen with a card but zero guidance. The "aha moment" — the payoff for the effort — never arrives.
03 — Redesign
A leaner,
smarter flow
6 steps instead of 8. Every pain point addressed. Value is front-loaded, inputs are minimised, and the flow ends with a moment users actually feel.
Value splash (3 screens)
A swipeable 3-screen intro — "Pay in-store", "Send to friends", "Stay secure" — before any commitment. Skippable at any point.
Fixes: no value hookGoogle sign-in (unchanged)
The existing sign-in is already smooth for Google users. One-tap account selection retained as-is — no change needed here.
No change neededBiometric + T&C combined
A 3-bullet plain-language summary of key terms, plus face/fingerprint setup — in one screen. Security setup is no longer a surprise.
Fixes: T&C wall + security gateScan-first card add
Camera scan is the primary CTA — not a footnote. It auto-fills card number, expiry, and name instantly. Manual entry remains as a fallback.
Fixes: manual card entryAuto-read OTP
The SMS Retriever API reads the bank OTP automatically — no app switching. A live progress indicator shows verification in progress.
Fixes: context switching"You're ready" arrival
An animated success state shows the card, highlights nearby NFC stores on a mini map, and prompts the first use: "Find a place to pay."
Fixes: empty arrivalDesign principles applied
Progressive disclosure
Reveal complexity only when the user is ready for it — not all at once at the start.
Scan before keyboard
Default to the fastest, least error-prone input method. Make the right thing the easy thing.
Celebrate completion
The end of onboarding is a moment of earned trust — design it to feel like a payoff, not a stop.
04 — Results
Before vs after
Projected improvements based on mobile payment onboarding benchmarks and published research on friction reduction in fintech apps.
8 → 6
Steps to complete onboarding
~40%
Reduction in taps required
0
App-switching events (was 1+)
+20pp
Projected completion rate lift
| Dimension | Current experience | Proposed experience |
|---|---|---|
| Value intro | None — jumps straight to account sign-in | 3-screen swipeable splash, fully skippable |
| Terms presentation | Full legal text, full screen, no summary or hierarchy | 3-bullet plain-language summary with link to full text |
| Card input | Manual 16-digit entry as primary; scan is secondary | Camera scan as primary CTA; manual entry as fallback |
| OTP verification | Manual copy-paste from SMS inbox; requires app switch | Auto-read via SMS Retriever API; no app switching |
| Security setup | Mid-flow surprise gate with no prior warning | Integrated into step 3, explained with context upfront |
| Permission dialogs | 2 consecutive system dialogs (NFC + default app) | 1 contextual prompt, shown post-success when relevant |
| Completion state | Home screen with no guidance, tutorial, or next step | Celebration screen + nearby store discovery + first-use prompt |
| Est. completion rate | ~55–65% (industry avg for payment apps) | ~75–82% projected (scan + auto-OTP + value hook) |
05 — Interactive prototype
Click through
the redesign
A clickable simulation of all 6 screens in the proposed onboarding flow. Use the screen list or navigation buttons to step through.
Pay anywhere, instantly
Tap your phone at millions of stores, apps, and websites. No card needed — your phone is your wallet.
Send money in seconds
Split bills, pay back friends, or send cash to family — all without leaving the app. Free, instant transfers.
Bank-level security
Your card number is never shared with merchants. Every transaction uses a unique token. Your data stays yours.
Quick setup
What you're agreeing to
· Card data is encrypted and stored on-device
· Google never sells your payment info
· You can delete everything at any time
Uses your existing device security
Add your card
Scan to fill all details automatically — takes about 2 seconds. CVV can be added after scanning.
You're ready to pay!
Hold your phone near any contactless terminal to pay in stores. Or tap the Google Pay button online.
Nearby stores accepting Google Pay
Pret a Manger · Boots · Tesco Express · Caffè Nero
Proposed 6-screen flow
Each screen reflects a specific design decision from the analysis above. Click any screen in the list to jump directly to it.