Ballistic Media
Quick answer: Good fintech onboarding gets a new user to their first moment of value, such as a funded account, a first payment or a connected bank, with as little friction as regulation allows. The patterns that work are consistent: show the value before asking for data, explain why each piece of information is needed, break identity checks into small steps with progress shown, verify automatically where possible, save progress so users can return, and design the "we need more information" paths as carefully as the happy path. Compliance requirements such as KYC are not optional, but how you ask for them is a design decision.
Why onboarding matters more in fintech
In most apps, onboarding is a few screens and a sign-up form. In fintech it often includes identity verification, address checks, regulatory questions and linking a bank account, all before the user has seen any benefit. Every step is a point where people leave. And unlike most apps, many of those steps are legally required, so you can't simply remove them.
Regulators also care about how onboarding is designed. In the UK, the FCA's Consumer Duty, in force since July 2023, expects firms to support customers' understanding through clear, timely communication. Onboarding is where much of that understanding is formed.
Nine onboarding patterns that reduce drop-off
1. Show value before asking for data
Let people explore a demo, see example rates or use a calculator before they create an account. Users who understand what they will get are more willing to complete identity checks.
2. Ask for the minimum at each step
Collect only what you need right now. An email or phone number to start, then identity details when they become necessary, for example before the first transaction rather than before the first screen.
3. Explain why you need each piece of information
"We're required by law to verify your identity" next to a passport upload removes a lot of hesitation. People are far more willing to share sensitive data when they understand the reason and know how it is protected.
4. Break identity verification into small, visible steps
Document capture, selfie or liveness check, address confirmation: show each as a separate step with a progress indicator. Tell users how long it will take and what they need to have ready before they start.
5. Verify automatically where you can
Automatic document reading, database checks and open banking connections remove manual typing and waiting. Manual review should be the exception, with a clear message when it happens.
6. Design the "we need more" paths
Some users will fail an automatic check or need manual review. Tell them exactly what happened, what they need to do and how long it will take. A vague "verification failed" screen is where many lose trust entirely.
7. Save progress and let people come back
People often start onboarding on the move and can't find their passport. Save every step, let them resume on another device, and send a helpful reminder rather than a pushy one.
8. Make the first action obvious
Once verified, guide users straight to their first moment of value: add money, make a first transfer, set up a first payment. An empty dashboard after a long verification process is a missed opportunity.
9. Put risks and fees in plain sight
Fees, risks and key terms should be clear before a user commits, not discovered later. This is both good design and, for many products, a regulatory expectation. Clear disclosure also reduces support tickets and complaints.
Common onboarding mistakes
| Mistake | Better approach |
|---|---|
| Asking for all personal details on the first screen | Progressive collection, with each step justified |
| No progress indicator during verification | Numbered steps with an honest time estimate |
| Generic error messages | Specific next steps and expected waiting times |
| Losing progress when users leave | Autosave and resume on any device |
| Legal text in long walls of small print | Plain-language summaries, with full terms available |
| Empty dashboard after sign-up | A guided first action |
What to measure
- Step-by-step completion rate: where exactly people leave.
- Time to verification: how long from sign-up to a verified account, including manual reviews.
- Time to first value: how long until the first deposit, transfer or other key action.
- Verification failure reasons: which documents or checks fail most, and why.
- Support contacts during onboarding: what users get stuck on.
Watch real users go through onboarding as well. Session recordings and short usability tests often reveal problems that funnel data can't explain.
Where Ballistic Media fits: we design and improve fintech app onboarding and dashboards, from KYC flows to first-action screens, working within your compliance requirements. See our fintech app and dashboard UX services, and our list of common fintech website mistakes.
FAQs
What is KYC in fintech onboarding?
KYC (know your customer) is the process of verifying a customer's identity and assessing risk, required for many financial products under anti-money-laundering rules. It usually involves collecting identity documents, checking them and screening against watchlists.
Can we let users in before KYC is complete?
Often, partly. Many products let users explore the app or see their account before verification, with transactions unlocked only once checks are complete. What is allowed depends on your product, licence and market, so confirm with compliance.
How many steps should fintech onboarding have?
As few as your regulatory requirements allow, but the number matters less than clarity. Users will complete more steps if each is short, explained and visibly moving them forward.
Does open banking help onboarding?
It can. Connecting a bank account through an open banking or account aggregation provider can confirm ownership of an account and pre-fill information, which reduces manual entry. Offer a manual alternative for users who prefer not to connect.
How do we reduce drop-off during identity verification?
Tell users what they need before they start, show progress, use automatic document capture, allow them to pause and resume, and make error messages specific. Then measure each step to find where the remaining drop-off is.
Sources
- FCA Handbook, PRIN 2A.5: Consumer Duty, consumer understanding
- Financial Conduct Authority, Consumer Duty
