Design
Build
Not sure where to start? Start a project
Latest articles
Resources
Latest articleHow to Choose a Design Agency in 2027: A Practical ChecklistRecent cases
Explore
Case studyiGaming Branding & Web Design: Crypto Casino( Design )
Written by Mara Bureau · Published [date] · Last updated [date]
KYC onboarding loses most users through design, not regulation. Regulators decide what you must collect; your product decides when, how and in what order. In our review of 50 fintech products, the biggest leaks were document upload, unexplained verification waits, and asking for personal data too early: 34 of the 50 asked for details like date of birth or address before showing the product at all.
Less than most onboarding flows ask for. Under the US Customer Identification Program rule for banks, 31 CFR 1020.220, a bank must collect at minimum a name, a date of birth for individuals, an address and an identification number before opening an account. The rule says nothing about the order of screens, the copy, or what users see while they wait.
In the EU, the EBA Guidelines on remote customer onboarding (EBA/GL/2022/15), applied since October 2, 2023, add requirements on how evidence is captured: images clear enough to verify, a secure channel, and timestamped records kept for audit. Good document-capture design is part of meeting those rules, not a trade-off against them.
Data | Required by US bank CIP at account opening? | When products often ask | When to ask instead |
|---|---|---|---|
Name, date of birth, address, ID number | Yes | First screen | At the verification step, after the user has seen the product |
Employment status | No | Sign-up | When a feature needs it, such as credit or investing |
Income, source of funds | No, but may be needed for risk or suitability | Sign-up | At the first action that needs it, such as a higher limit |
Tax ID beyond the ID number | Depends on product | Sign-up | Before the first taxable event, such as interest or trading |
Phone number | No | Sign-up | At sign-up is fine if it is your login method |
What the table shows: the legal minimum is short. Everything else is a product decision, and each extra field at sign-up is a reason to leave.
Limit: lending, brokerage and crypto products often have extra obligations, such as affordability or suitability checks. Collect that data at the step that needs it, and say why on the screen. Confirm the exact list with your compliance team for each market.
In our review, three steps caused most of the visible friction across neobanks, lending, payments and crypto products.
1. Document upload. Among products that required a photo of an ID, this was the most common friction point. The best ones gave format guidance before the camera opened, offered both camera capture and file upload, and checked the photo immediately instead of rejecting it after the user submitted the whole form.
2. Unexplained verification waits. Automated checks sometimes take longer than expected. More than half of the products showed nothing between “uploading” and “verified” except a spinner. Users read silence as failure, close the app and contact support.
3. Premature data collection. 34 of 50 products asked for date of birth, address, employment or a tax ID before the user had any sense of the product. The best flows collected the minimum to show the product, then asked for the rest when a specific action needed it.

These are working benchmarks from our review of 50 products and our own project work, not an industry census. Use them to spot where your flow is far off, not as targets to report.
Metric | Poor | Average | Well-optimized |
|---|---|---|---|
KYC end-to-end completion | Below 35% | 40–55% | 55–70% |
Document upload success rate | Below 50% | 60–70% | Above 80% |
Verification support tickets per 100 users | Above 15 | 8–12 | Below 5 |
Time to first meaningful action | Over 10 min | 5–8 min | Under 3 min |
What the table shows: if completion is below 55%, look at document upload and the verification wait first. Both are fixable in weeks.
Limit: completion depends on your audience and market. A regulated lending product will complete lower than a prepaid card. Compare your numbers over time and by step, not only against this table.
Design KYC as seven steps, each with one job. The regulatory checks stay the same; what changes is what the user knows at each moment.

On the screens where users hand over sensitive data. In 41 of the 50 products we reviewed, encryption notices, regulatory registrations and partner bank logos appeared in the footer or on a separate security page.
Place one short, specific cue at each of those moments: the regulator and licence on the ID screen, the partner bank on the linking screen, and a line on how documents are stored. Limit: more badges do not mean more trust. One relevant line at the right moment does more than a row of logos.
Most KYC happens on a phone, and many flows are designed for desktop first. Of the 31 products in our review with both web and mobile versions, 24 shipped mobile as a compressed version of the web layout, and 18 had buttons with touch targets under 44 px.
The fixes are basic and often skipped: fields that move to the next input automatically, the right keyboard for each field (numbers for dates and codes), camera capture as the default for documents, and buttons large enough to hit on the first try. Limit: some desktop users onboard for business accounts; for B2B products, test both.
Three patterns come up in almost every KYC flow we work on.
( You may ask )
KYC onboarding is the part of sign-up where a financial product verifies who a customer is, usually with personal details, an ID document and often a selfie. The legal checks are fixed; the order, copy and design of the steps are product decisions.
For US banks, the Customer Identification Program rule requires at minimum a name, date of birth, address and identification number before opening an account. Other products and markets can require more, so confirm with your compliance team.
In our review, well-optimized flows completed at about 55–70%, average flows at 40–55%. Your rate depends on product type and market, so track it by step and over time.
Most often at document upload, during unexplained verification waits, and when asked for personal data before seeing the product. All three are design problems you can fix without changing the regulatory checks.
Aim for a first meaningful action within about 3 minutes for simple products. Automated checks often finish in under a minute, but some cases need manual review, so design the waiting state as carefully as the form.