The Real Reason Users Abandon KYC (It's Not Compliance, It's the Design)
Every team I meet blames the regulator for their KYC drop-off. The regulator isn't the problem. The way you asked is.
Strahil Hadzhiev
AUTHOR
"It's compliance, our hands are tied" — the most comfortable lie in fintech
I hear the same sentence in almost every kickoff. We'd love a smoother signup, but KYC is compliance — our hands are tied. It's said with a shrug, as if the abandonment is a law of physics. As if the regulator personally designed your document-upload screen.
They didn't. And that shrug is the most expensive sentence in the building.
Here's the distinction that took me years to be able to explain cleanly, and it changes everything once a team really gets it. Compliance defines what you must collect. Design defines how it feels to hand it over. Those are two completely different jobs, owned by two completely different parts of the org, and confusing them is the single biggest reason KYC bleeds users. The law says you need a verified identity — a name, an address, a government ID, a face match. The law does not say the ID upload has to feel like being frisked. It does not require the eleven fields on one screen, the missing progress indicator, the cold "verification failed" with no way forward. Every one of those is a design decision someone made and then blamed on the regulator.
So when I look at a KYC flow losing users, I'm not looking at a legal problem wearing a design costume. I'm looking at a design problem wearing a legal alibi.
And the alibi doesn't even hold when the KYC is outsourced — which, these days, it usually is. Most teams plug in a third-party verification provider to save build time and stay compliant, then treat the whole experience as someone else's box to check. But the user doesn't know or care that a vendor is running the check. They're still moving through your interface, in your product, feeling your level of care or carelessness. The provider handles the verification. You still own the experience. Outsourcing the compliance never outsources the trust.
The numbers on this are brutal, and they're not about the law being hard. Signicat's research put average fintech onboarding drop-off around 63%, and estimated something on the order of €5.7 billion wasted every year across Europe on onboarding people never finish. That's not the cost of regulation. Regulation is a fixed requirement everyone in the market shares equally. That five-point-seven billion is the cost of design — the gap between companies that made meeting the requirement feel safe and companies that made it feel like an interrogation.
Same law. Wildly different outcomes. The variable was never compliance.
Nobody abandons the requirement. They abandon the feeling.
Here's what I've learned watching real people move through real KYC flows: users almost never quit because of what is being asked. They quit because of how it feels to be asked. Those are not the same thing, and the entire drop-off lives in the difference.
Watch where people actually bail, and it's rarely the abstract idea of identity verification. It's specific, designed moments. It's the document-upload step, where someone photographs their ID and then just... waits, with no framing guide, no real-time feedback, no confirmation the photo was even acceptable — left guessing whether it worked, which in a money app reads as something is wrong and it's my fault. It's the ID request that arrives cold, with no explanation, so instead of feeling routine it feels invasive. It's the screen with no sense of how long this will take or how far along they are, so a two-minute process feels like a trap with no exit. It's the tone — dense, impersonal, procedural — that makes a person feel like a suspect being processed rather than a customer being welcomed.
None of that is the regulator's doing. All of it is fixable without touching a single legal requirement.
Because the flip side is just as true: people will hand over a passport, a selfie, and their home address without hesitation when they feel safe and guided. Give them one clear ask at a time instead of a wall of fields. Give every single request a plain-language reason sitting right next to it — not a legal disclaimer, a human sentence explaining why you need this and what you'll do with it. Turn the document capture into something that actively helps: framing guides, real-time validation, instant confirmation, so nobody's ever guessing. Tell them, honestly, that this takes about ninety seconds, and show them moving through it. Design the failure states with as much care as the success states, so a blurry photo becomes "let's just retake this one, everything else is saved" instead of a dead end. Stop designing a form. Start designing a conversation.
Do that, and the requirement doesn't change one bit — but the abandonment collapses. In one documented redesign, KYC drop-off fell from around 62% to 27%, verification time more than halved, and completed-verification rates jumped — and not a single regulatory obligation was altered. Only the experience was. That's the whole argument in one data point: when you fix the design, the "compliance problem" quietly disappears, because it was a design problem the entire time.
The regulator sets the questions. You decide whether answering them feels like a threat or a handshake.
Compliance owns the "what." You own the "how." Stop hiding behind the lawyers.
Once you accept that KYC abandonment is a design outcome, the strategic weight of it changes completely — and this is the part I most want founders to sit with.
KYC isn't a box at the bottom of the signup you tolerate. It's one of the most leveraged screens in your entire business. Think about what rides on it. You spent real money acquiring this person — ads, content, referrals, incentives, hundreds of dollars a head. All of that customer-acquisition cost is riding on whether they get through verification. Every point of KYC completion you win is wasted acquisition spend recovered, activation lifted, lifetime value unlocked, support tickets never filed. That makes the KYC flow less a compliance chore and more the highest-return design work in the company. It isn't a design task. It's a growth initiative wearing a compliance uniform.
And here's the evergreen part, the reason this matters no matter what changes around it. Regulations will keep shifting — new rules, new checks, new jurisdictions, new verification tech. But the human on the other end of the KYC flow does not change. They will always feel the same things when asked to hand over their identity: a flicker of suspicion, a fear of being scammed, a need to understand why, a hope that this is safe. Design for that human — the constant — and you'll meet whatever the regulator asks for next without bleeding users, because the fundamentals of feeling safe don't move when the rules do. Design for the lawyer instead of the human, and you'll keep losing two-thirds of the people you paid to bring to the door, and you'll keep blaming a regulation that never wrote a word of your interface.
So the question I put to every fintech team is simple, and a little pointed. Is your onboarding designed for humans, or for lawyers? Are you making people feel safe, or making them feel processed? Because the requirement to verify identity is shared by every competitor you have. The experience of it is the only part you control — and it's the part deciding who finishes and who walks.
Users never abandon KYC because it's required. They abandon it because it was designed as if they were a suspect instead of a customer. Change that, and you don't need to change the law — you just need to stop blaming it.
Strahil Hadzhiev
AUTHOR
