Pain Point
The Bithumb case, made public in March 2026, lays out in granular detail exactly what “identity verification isn't working” looks like at exchange scale.
South Korea's Financial Intelligence Unit found roughly 3.55 million customer verification failures and 3.04 million cases where trading wasn't blocked despite incomplete identity checks — plus tens of thousands of unregistered foreign-operator transfers.
Blurred IDs and documents with data fields hidden were accepted rather than rejected; some re-verifications were completed by reusing the original sign-up document instead of collecting a fresh one.
Driver's license checks reportedly ran without validating the encrypted serial number needed to confirm authenticity — a document verification step that existed on paper but didn't actually verify anything.
The regulator's response matched the scale: a six-month partial business suspension and a fine of roughly 36.8 billion won, alongside a personal reprimand for the CEO.
Every one of these gaps sits inside identity verification specifically — not transaction monitoring, not sanctions screening. This is what happens when document checks and re-verification exist procedurally but don't function as real controls.
How It Works
What Bithumb's case shows failed points directly to what identity verification software actually needs to confirm, not just process:
Document verification software that rejects blurred or partially obscured IDs outright, rather than accepting them as passable.
Id verification software that validates a document's authenticity features — like an encrypted serial number — instead of treating document capture as the entire check.
A KYB onboarding solution where re-verification means collecting a genuinely fresh document, not reusing whatever was submitted at original sign-up.
Liveness detection software — id with liveness — layered with document checks, so a verification event actually confirms a live, present applicant, not just that some document was on file.
Every one of the 6.65 million violations traces back to one of these steps existing in name but not in function — which is precisely the gap a genuinely automated, enforced verification flow is built to close.
False Positives
A platform reacting to a case like Bithumb's by rejecting any document with the slightest imperfection risks losing legitimate users to friction that doesn't actually improve security — the finding wasn't that Bithumb verified too strictly, it was that verification didn't function as a real control at all. The fix is enforcement and completeness, not blanket rejection.
Business Impact
Reduced exposure to the exact violation categories that cost Bithumb a six-month partial suspension and a nine-figure-won fine.
User onboarding tools that verify onboarding customers by actually confirming their identity, not by accepting a submission and moving on.
A documented, enforced KYC onboarding solution ready for the kind of scrutiny regulators are now applying to exchanges globally.
Continued access to banking and liquidity relationships that increasingly expect platforms to demonstrate real, not procedural, identity verification.
How Finchecker Solves It
Finchecker's identity verification enforces document authenticity checks, genuine re-verification, and liveness detection as functioning controls, not procedural steps — closing exactly the category of gaps that turned into 6.65 million violations at Bithumb. Every verification event is logged and auditable, ready for the level of regulatory scrutiny crypto exchanges are now facing.
Make sure your identity verification actually works, not just exists on paper. Talk to Finchecker about identity verification built to withstand the scrutiny Bithumb didn't.