What is KYC drop-off?
Used in a sentence: KYC drop-off is worst at the selfie step, so let's nudge users who leave there with a short guide on lighting and framing.
How it works
KYC in a fintech app is a multi-step flow: personal details, ID number, document upload, selfie or video check, and sometimes bank account verification. Each step fires an event, such as “KYC started”, “PAN entered” or “selfie submitted”.
KYC drop-off is the share of users who fire “KYC started” but never reach “KYC completed” within a set window. Teams usually break it down by step to find where users leave, and by cohort to see whether a change helped.
Drop-off spikes at steps that need something the user doesn’t have at hand, a document or good lighting, or where verification fails without a clear reason.
Example
A lending app sees many users stall at the bank statement upload. The team adds two nudges. Before the step, a short card explains which statement formats work. For users who leave at that step, a bottom sheet appears on their next session saying where they stopped and offering to resume. Users who have completed KYC are excluded, and drop-off at that step is compared against a holdout cohort.
KYC drop-off vs onboarding drop-off
| KYC drop-off | Onboarding drop-off | |
|---|---|---|
| Scope | Identity verification steps only | The whole first-run journey |
| Typical causes | Documents, failed checks, trust | Friction, unclear value, sign-up effort |
| Who owns it | Product, compliance and growth | Product and growth |
KYC drop-off is a subset of onboarding drop-off, but it needs its own funnel because regulatory steps can’t simply be removed.
Best practices
- Track drop-off per KYC step, not just start to finish, so you know which screen to fix.
- Tell users up front which documents they need, before they begin.
- Re-engage users who left mid-flow on their next session, and resume them at the step where they stopped.
- Exclude verified users and anyone with a pending manual review from reminder campaigns.
How to do this with Digia Engage
A growth team uses KYC events already tracked in CleverTap, MoEngage or WebEngage to trigger nudges at the right step: a tip before the selfie screen, a resume prompt for users who left. Messages are built in the no-code builder and go live without an app release. The Activation use case covers KYC completion nudges, and the Financial services page shows how fintech teams apply them.
Frequently asked questions
- Why do users abandon KYC?
- Common reasons are not having documents at hand, unclear instructions, failed selfie or document captures, slow verification responses, and worry about sharing identity data. Some users simply get interrupted and never come back. Step-level funnel data shows which reason dominates, because each one tends to cluster at a specific screen.
- How can apps reduce KYC drop-off without an app update?
- Use an in-app engagement layer that renders messages from server-side configuration. Teams can then add reminders for users who left mid-flow, tips before tricky steps and reassurance about data security, all triggered by existing KYC events. Copy, timing and targeting change from a dashboard, so fixes reach users without a release.
Related terms
Read more
Part of the In-app engagement glossary.