- Identity verification, not signup, is where most fintech funnels actually leak users.
- Friction and regulatory rigor aren't the same thing — many forms add friction that compliance never required.
- Progressive verification (light checks early, deeper checks at a threshold) keeps the funnel open.
- A KYC vendor's default widget isn't your onboarding flow — the retry and fallback logic has to be built around it.
- Instrument every step before redesigning, or you're guessing at the fix.
The drop-off nobody tracks
Product teams obsess over signup-form conversion and ignore the step right after it — identity verification. That's usually where the real bleeding happens. A clunky KYC flow can lose a third of otherwise-qualified users, and most dashboards never surface it as its own funnel stage.
A dashboard built around 'signups' as the top metric will never surface this, because the user technically did sign up — they just never made it through to a usable account.
Friction is not the same as rigor
Regulators care about the outcome — verified identity, documented decisioning — not about how many fields your form has. Teams conflate the two and add friction that doesn't actually improve compliance. The fix is separating what's legally required from what's just inherited from a template.
A regulator reviewing an approved application afterward cares whether the identity was actually verified and the decision documented — not whether the form had six fields or two.
Progressive verification works
Full KYC upfront kills conversion. Progressive verification — light-touch checks at signup, deeper checks only when a user hits a transaction threshold — keeps the funnel open while still satisfying the same regulatory bar, just staged differently.
In practice, that means asking for an email and a phone number at signup, and reserving document upload and liveness checks for the moment a user tries to move real money.
Your KYC vendor is not your onboarding flow
Persona, Onfido and similar tools handle document checks well. They do not, by default, handle your product's specific drop-off points, retry logic or fallback messaging. That layer has to be built around the vendor, not left to its default widget.
The gap shows up most in retry flows — a blurry photo upload with no clear next step is where most abandoned verifications happen, and it's almost entirely a UX problem, not a compliance one.
Instrument before you redesign
Before touching the flow, instrument every step so you can see exactly where users abandon. Redesigning a KYC flow without that data is a guess dressed up as a project.
In one build, adding a funnel-stage breakdown to an existing analytics setup took under a day and immediately reprioritized the redesign around the actual biggest drop-off, not the one the team assumed.