A product teardown of getting a new user from install to a verified account, by Shivam Bajaj. Built only from public sources; I have no access to slice's internal data.
slice began as a card and UPI app and merged with North East Small Finance Bank, effective 27 October 2024 (YourStory; Entrackr). Since then, a new user has to become a bank customer, and that means identity verification before the app can show its value.
Public information on slice's current flow is thin. Where I describe a step I could not confirm, I label it a hypothesis. Forum posts are individual reports, not measured rates.
Illustrative archetypes I made up, not real people. Hypotheses are labelled.
Who: 23, just started a first salaried job in Bengaluru
Goals: A free, simple savings account with good interest
Pain points: Hypothesis: unsure what documents are needed and drops off to find them
Opportunity: A "keep these ready" checklist with time estimate
Who: Already uses the slice card or UPI app
Goals: Move to the bank account without starting from scratch
Pain points: Post-merger, existing users move to the bank (YourStory); the migration steps are not clearly public
Opportunity: Pre-fill known details and explain what changes
Who: Irregular income, name spelled differently across documents
Goals: Open an account without a branch visit
Pain points: Name errors in CKYC data led to a rejected account in one reported case (DesiDime)
Opportunity: Show fetched name, allow corrections in place
Reported issues come from forum posts and industry studies. Items marked Hypothesis are my guesses, not observed in the app. The deck I took the format from scores each step with a psych score; I leave that out because I have no data to back numbers.
| Download & phone | OTP | Basic details | PAN & CKYC fetch | Video KYC | Activation & first use | |
|---|---|---|---|---|---|---|
| Goal | Understand what slice offers and start | Prove the phone is mine | Get through the easy part quickly | Verify identity without paperwork | Finish verification in one go | See the account working |
| Feeling | Curious | Impatient | Comfortable | Wary of sharing PAN | Self-conscious, rushed | Relieved, or let down if delayed |
| Pain point | Hypothesis: users may not know the documents needed before starting | Few, if any, since OTP is routine | Hypothesis: long forms before value is shown | Name mismatches in CKYC data led to a rejected account in one reported case (DesiDime) | Selfie and liveness checks are a common source of retries across KYC vendors, and up to 60% abandon digital account opening overall (Markswebb) | Some users report accounts showing as not serviceable after CKYC opening (DesiDime) |
| Idea | Checklist of what to keep ready, with time estimate | Auto-read OTP and clear retry timer | Ask name and email first, with reasons | Show the fetched name before submitting; let users correct it | Lighting tips, save-and-resume, booking a slot | Show account status and next step immediately |
Context: slice has used HyperVerge technology for identity checks (HyperVerge case study, vendor material). Forum users say account opening fetches CKYC data and uses video KYC with PAN, not Aadhaar, for many users (DesiDime).
Illustrative wireframes of proposed screens. They are not screenshots of slice's app, and all copy is placeholder.
1. Welcome: documents to keep ready and time needed, before any input
2. Basic details first, with a progress bar and a reason for each ask
3. KYC choice: time and effort shown, mismatch can be fixed in place
4. Video KYC: tips, camera preview, save and resume
My suggestions, not claims about slice's roadmap.
Open with a checklist and a time estimate before any field. Why: Users who leave to find a document often do not return. Risk: A long checklist can scare people off, so keep it to three items.
Ask name and email before PAN and the selfie, with a progress bar and a reason for each ask. Why: Small wins build investment before the sensitive steps. Risk: Longer flow if the extra steps add no information.
After the CKYC fetch, show the name and let the user correct or switch method without restarting. Why: Mismatch rejections are a reported cause of failure. Risk: Needs a safe correction path to satisfy compliance.
Keep progress after KYC steps and send a reminder with a deep link to the exact step. Why: Users who drop off mid-way are the cheapest to win back. Risk: Reminders must respect consent and frequency limits.
Verified accounts opened per day.
% of installs that finish video KYC.
% of users who leave mid-flow and later finish.
Format inspired by a Fi onboarding teardown by another author; all content here is original. Independent teardown, not affiliated with slice. Forum and vendor content is indicative only.