Skip to content

Teardown · UPI payments apps

First-run onboarding in UPI payments apps

Linking a bank account is a high-stakes moment. How payments apps build enough trust to get through it — and where new users stall.

Last reviewed

  • Trust and risk
  • Activation
  • HEART

Context

UPI payments apps share the same rails, so differentiation often comes down to experience. Onboarding is where that matters most: a new user must hand over a phone number, verify it, link a bank account and set or confirm a UPI PIN before they can do anything useful.

User and job-to-be-done

Primary user: someone installing the app because they need to pay or receive money now — at a shop counter, splitting a bill, or paying a friend.

Job: "Help me make this payment quickly, without risking my money."

The urgency matters. Many first sessions start under time pressure, with someone waiting.

Flow walkthrough

  1. Language selection and permissions (SMS, contacts, location may be requested).
  2. Phone number verification, often through device SMS.
  3. Bank selection and account discovery.
  4. UPI PIN setup or confirmation, which may require debit-card details.
  5. Home screen with scan-and-pay, contacts and bills.

What works

  • Automatic SMS-based verification removes typing for most users.
  • Bank discovery lists accounts linked to the number, avoiding manual entry.
  • Scan-and-pay on the home screen gets straight to the most common first job.

Friction and hypotheses

Friction Hypothesis
Several permission prompts before value is shown Some users decline or abandon when they cannot see why a permission is needed
Debit-card details needed for PIN setup Users without their card to hand stall at this step — likely a major drop-off for first-time UPI users
Generic error messages from banks Users cannot tell whether to retry, switch bank or wait
SIM/phone-number mismatch on dual-SIM phones Verification fails without a clear explanation

Metrics we'd watch

  • Activation: share of installs that complete a first successful transaction within the first session and within seven days.
  • Step-level completion through verification, bank linking and PIN setup.
  • Error-recovery rate: users who hit an error and still complete onboarding.
  • HEART lens: Happiness (post-onboarding rating), Engagement (second transaction), Adoption, Retention, Task success.

If we were the PM

  1. Ask for permissions just in time — contacts when the user first pays a contact, not at install. Trade-off: slightly lower contact-permission rates.
  2. Let users receive before they link fully. Receiving money needs less setup than paying; a "receive first" path could activate users who lack their card. Trade-off: regulatory and fraud constraints must be checked carefully.
  3. Translate bank errors into next steps — "Your bank's server is slow; try again in a few minutes" instead of an error code. Trade-off: needs mapping and maintenance for each bank's responses.