Signup → KYC → Bank Approval, benchmarked stage by stage against published fintech and neobank onboarding data. Funding/activation is out of scope for this pass.
Pana Global, 2026 YTD. Absolute users at each stage — the width is the true drop, not a rescaled one.
Bar = Pana Global's actual conversion rate for that stage. Shaded band = the range reported across fintech/neobank onboarding benchmark sources.
Wizard opened → Approved, Pana Global. Amplitude wizard-open tracking only goes back to Jul 2025, so this compares H2 2025 to 2026 YTD — same definition both periods, different lengths.
| Stage | Definition | Pana Global 2026 YTD | Industry benchmark | Verdict | Source |
|---|---|---|---|---|---|
| Signup → Wizard opened | User opens the in-app Bridge onboarding wizard (Amplitude) — the true start of KYC | 71.3% | — | No benchmark | No source isolates this exact step |
| Wizard opened → Persona application created | Backend creates a personainquiry record — the first point Persona's own system knows the user exists |
64.7% | — | No benchmark | Pana-specific backend step; no vendor publishes this either |
| Wizard opened → Approved (KYC completion) | Identity verification completed and approved, measured from where the user actually starts | 41.6% | ~55–65% | Below range | Perspective AI, 2026 |
| Persona application created → Approved | Same "completion" measured only from Persona's own intake step, not from the wizard | 64.3% | ~55–65% | Not the industry metric | Included for continuity with the prior version of this deck |
| Overall onboarding abandonment | Share who never complete onboarding, any stage | context only | ~68% abandon | Context | Perspective AI (Signicat-sourced) |
user.createdAt, Pana Global (usertype = GLOBAL), signup-month cohort.Bridge Onboarding Started or Viewed Onboarding Bridge Wizard, per user, from panaapp-16ce3.amplitude.EVENTS_396830. This is t1 in Pana's own canonical KYC event table — the true first step, ahead of anything Persona's backend tracks. Query diag-onboarding-wizard-started-monthly.personainquiry record exists for the user (BigQuery, planetscale_pana.personainquiry). This is t7 in the same canonical table — created by Pana's backend once the user has gone far enough into the wizard, not when they open it.bankapplication.status = 'Approved'. Metabase queries funnel-3step and persona-funnel-flow (cross-checked, agree to within 0.3%).panaapp-16ce3.planetscale_pana and panaapp-16ce3.amplitude, Sep 8, 2026.persona-funnel-flow) tracked. Claudia flagged that KYC should start counting from when Persona actually takes the user, which led to checking Pana's own canonical event table and finding the wizard-open event (t1) is the true start — 25pp earlier than what the deck first reported.started/7001, Plaid's IDENTITY_VERIFICATION_START_STEP), but their own funnels begin after a verification session is already created, not at account signup. That earlier handoff sits outside what any vendor or industry report measures, so it isn't a gap in this research — it's an industry-wide blind spot. It's exactly why "wizard opened → approved" is the right stage to benchmark against their "KYC completion" figures — it's Pana's closest match to what vendors mean by "started."