Turning a compliance-heavy flow into an 82% completion rate

Redesigned Slice's onboarding experience to meet RBI KYC requirements while removing the friction that was causing over half of users to abandon before activation.

Slice onboarding redesign
82%
Completion rate
Up from 45% pre-redesign
20%
Drop-off reduction
Post credit-check abandonment
40%
Under 2 minutes
Users completing sign-up
The problem space

I looked at the existing onboarding and found a clear pattern: over half of people who started never finished. The leaks weren't scattered — they clustered at three steps.

Old onboarding flow — drop-off points

Phone number
OTP
Name
User type
PAN image upload
Company name
Company city
Salary range
PF deducted
Address upload
Selfie
Wait 24–48 hrs
The problem

Over half dropping off

Three steps accounted for majority of abandonment: PAN image upload, address upload, 24–48hr wait.

The opportunity

Automate the hard parts

Replace manual document uploads with automated data fetches, show credit limit at end to remove uncertainty of waiting.

The people we designed for

I grounded the redesign in two user types we kept seeing in interviews — first-timers who needed reassurance, and experienced users who refused to re-enter data Slice already had.

First-time credit card user

Malini, 28

Works in IT, shops online, uses finance apps

  • Wants quick approval and clear next steps
  • Gets anxious when asked for documents without knowing if she qualifies

“If I'm approved, tell me now — then I'll finish the rest.”

Experienced credit card user

Rajesh, 33

Manager in a Tier-2 city, already owns a card

  • Wants a fast process and clear benefits
  • Gets frustrated when asked for info already linked to PAN

“Don't make me enter what you already have from my PAN.”

Research insights

I combined funnel analytics, user interviews, and competitor review. Three insights shaped every decision that followed.

01

Funnel identified three critical leaks

Analytics confirmed biggest exits at PAN image upload, proof of address upload, and 24–48hr activation wait. These became the primary targets.

02

Users resisted giving documents before knowing if they'd be approved

Every interview participant said being asked for documents before any approval signal felt unfair. Validated showing credit score early as a motivation anchor.

03

Competitors had already found a compliant path

CRED and Paytm both deferred some KYC steps until after provisional approval. I used this as evidence to bring to the legal team.

Key design decisions

I explored four directions. Three I rejected. One I took to legal and shipped.

Full KYC upfront

Rejected
Pros

Compliance-safe, no post-approval work

Cons

High drop-offs at doc uploads, long time to value

Why rejected

Doesn't solve the problem, maintains status quo

Shortened upfront form

Rejected
Pros

Easier start, no backend change

Cons

Still front-loads address proof, core friction remains

Why rejected

Addresses symptoms not root cause

Parallel credit check + KYC

Rejected
Pros

Faster total time

Cons

Tech/API complexity; if either fails, user leaves with nothing

Why rejected

Failure mode is worse than current state

Approval-first with automated KYC steps

Accepted
Pros

Early win for user, less early friction, RBI-compliant before card issue

Cons

Needs backend sequencing and compliance sign-off

Why accepted

Removes the three highest drop-off steps while staying fully compliant

Final designs

I redesigned the sequence around motivation: show eligibility early, automate the document steps, and end with something usable — not a wait screen.

Results & impact

The redesign moved the completion rate from 45% to 82%. Document-step drop-off fell 20%. Forty percent of users finished sign-up in under two minutes.

Metric
Baseline / goal
Result
Status
Onboarding completion rate
↑ from 45%
82%
Achieved
Drop-off at document steps
−20%
−20%
Achieved
Users completing in under 2 min
Reduce perceived wait
40%
Achieved
Why it worked
  • Users saw value — credit score and approved limit — before doing the most tedious parts
  • The three highest drop-off steps were automated or eliminated, not just redesigned
  • RBI compliance stayed fully intact — full KYC completed before card issue, just in a better sequence
Key learnings

What I'd carry forward

01
Compliance can be an enabler if you involve the legal team early — they helped find the compliant path, not block it
02
In regulated flows, when you ask for data matters as much as what you ask for
03
Removing or deferring high-friction steps has a much bigger payoff than polishing the steps themselves
04
Showing progress and early wins — like the credit score reveal — keeps users motivated to complete the rest
Other key projects