Nils Silinevics
Partner · AML & Crypto Compliance · Former FIU Investigator
You've been told your identity verification failed without explanation on WhiteBit. WhiteBit, headquartered in Lithuania (White Bit UAB), is regulated by Lithuanian Financial Crime Investigation Service (FCIS) under Lithuanian Law on Prevention of Money Laundering and Terrorist Financing (transposing EU AMLD6). The exchange uses Chainalysis for blockchain analytics and Sumsub for identity verification. WhiteBit holds a Lithuanian crypto license, making it subject to full EU AML directives — which means stricter compliance requirements than Seychelles-based exchanges but also more predictable resolution processes through EU regulatory frameworks. WhiteBit freezes accounts when their Lithuanian compliance team flags transactions under EU AML Directive 6 requirements, particularly for high-value transfers or sanctions-adjacent activity. You submit your ID documents and selfie, but receive a rejection notification. The rejection may not explain why — the platform often just says 'verification failed' without specifics, leaving you to guess what went wrong.
WhiteBit freezes accounts when their Lithuanian compliance team flags transactions under EU AML Directive 6 requirements, particularly for high-value transfers or sanctions-adjacent activity. WhiteBit holds a Lithuanian crypto license, making it subject to full EU AML directives — which means stricter compliance requirements than Seychelles-based exchanges but also more predictable resolution processes through EU regulatory frameworks. This background matters because it shapes how WhiteBit handles compliance — and how we approach resolving your case.
The compliance framework: WhiteBit operates under Lithuanian Law on Prevention of Money Laundering and Terrorist Financing (transposing EU AMLD6), overseen by Lithuanian Financial Crime Investigation Service (FCIS). Their compliance infrastructure uses Chainalysis for blockchain analytics and Sumsub for identity verification. WhiteBit is known for EU-licensed exchange with competitive futures markets, serving European and CIS traders — and their compliance team is calibrated to flag deviations from typical user behavior in that segment.
What triggers kyc failed on WhiteBit:
Real case — EU regulatory framework: A Russian-born EU resident had €85,000 frozen on WhiteBit because their compliance team flagged his account under EU sanctions screening — despite his holding a valid EU residence permit. WhiteBit's Lithuanian compliance team required proof that his funds were not connected to sanctioned Russian entities. We provided his EU residency documentation, source-of-funds from his EU-based business, and a formal declaration of non-association with sanctioned individuals. Resolution took 12 days.
What WhiteBit requires to resolve this: Depending on the trigger, WhiteBit may ask for government-issued photo ID (verified through Sumsub), proof of address (utility bill or bank statement within 3 months), identity verification process (exchange statements, bank records, payslips, tax returns, or business documents), detailed transaction explanations with on-chain evidence, and in some cases a video verification interview. The challenge: WhiteBit rarely tells you which specific trigger caused the kyc failed, so you're guessing at what documentation to provide — and each rejected submission makes the next one harder.
Our approach is specific to WhiteBit: Because WhiteBit is EU-regulated, we use EU regulatory frameworks — including the right to a timely compliance decision under AMLD6 — to force resolution. Lithuanian FCIS is responsive to complaints about unreasonable delays. WhiteBit's compliance team understands EU law better than offshore exchanges, which actually makes negotiation more productive.
KYC Failed on WhiteBit — our strategy: We analyze the likely failure reason — document quality, name mismatch, expired ID, nationality restriction, or liveness check failure — and prepare a clean resubmission package that addresses the specific issue.
The submission that matters: Instead of submitting through WhiteBit's standard support channels (where you'll get automated responses or generic template replies), we prepare a professional legal submission — a structured compliance package with a cover letter from a Swiss law firm citing Lithuanian Financial Crime Investigation Service (FCIS) obligations and Lithuanian Law on Prevention of Money Laundering and Terrorist Financing (transposing EU AMLD6). WhiteBit's compliance team processes legal submissions differently from regular user tickets — they're assigned to senior compliance officers, not support agents, and they bypass the automated response loop that delays most cases by weeks.
When standard compliance isn't enough: Some situations fall outside the normal compliance flow — inherited crypto holdings, accounts registered under another person's name, unprovable source of funds through conventional documentation, or cross-jurisdictional complications where your residence, the exchange's jurisdiction, and the fiat banking path all differ. If that sounds like your case, our complex cases practice handles scenarios that other firms decline.
Further reading: our guide on what to do when a crypto exchange freezes your account covers the documentation and legal strategy in more depth.
We identify why KYC failed: expired/damaged ID, photo quality, name mismatch, nationality restriction, address verification gap, or liveness check issue. {p_name} rarely tells you the specific reason — we find it.
We prepare a clean resubmission: correctly formatted ID photos (no glare, full frame, valid expiry), matching name across all documents, proof of address within 3 months, and if needed, a legal name-change document or translation.
We resubmit through {p_name}'s verification team with a legal cover letter explaining any discrepancies (name variations, dual citizenship, transliteration issues). We cite {regulator} KYC requirements.
KYC verification passed — full account access restored. We advise on keeping documents current and avoiding KYC expiry issues on {p_name}.
WhiteBit, as a Lithuanian-licensed exchange, must comply with EU sanctions regulations. EU sanctions restrict certain Russian nationals from accessing EU financial services — but there are exemptions for EU residents, dual nationals, and individuals who can demonstrate non-association with sanctioned activities. If you hold an EU residence permit, WhiteBit cannot simply freeze your account based on nationality. We help frame your case under the specific EU sanctions exemptions that apply.
Paradoxically, yes — if you're a legitimate user. WhiteBit's EU license means they follow EU AML directives, which include your right to a timely compliance decision and due process. Offshore exchanges (BVI, Seychelles) can freeze accounts indefinitely with no regulatory oversight. With WhiteBit, we can escalate to Lithuanian FCIS if they delay unreasonably. This regulatory pressure typically resolves cases faster.
Common reasons include: expired or damaged ID document, document photo too blurry or with glare, selfie doesn't match the ID photo, name on account doesn't exactly match the ID, nationality not supported, or liveness check failed. The platform rarely tells you which specific reason caused the rejection.
Most platforms allow 3-5 KYC attempts. After that, your account may be permanently restricted. Each failed attempt makes the next one harder because the system flags repeated failures as suspicious. If you've already failed twice, we strongly recommend professional help before your next attempt.
Yes. Platforms operate under regulatory restrictions that may prevent them from serving nationals of certain countries (typically sanctioned jurisdictions). Even if you're a resident of an allowed country, your nationality can trigger a refusal. We help dual nationals navigate this by demonstrating their primary jurisdiction and compliance with applicable regulations.
Tell us what KYC documents were rejected and what reason WhiteBIT gave. We respond within 6 hours.