WhiteBit · Sanctions Screening Match
90%+ success

WhiteBit flagged you
in sanctions screening? We clear it.

You've been told your name or address matches a sanctioned individual 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 receive a notice that your account has been flagged for a sanctions screening match, or your account is suddenly frozen without explanation. The platform is legally obligated to block accounts with potential sanctions matches pending verification.

Fixed fee
€399 from
Or success fee
% of amount
Response
< 6h
◉ Swiss licensed lawyers◉ 90%+ success rate◉ No upfront payment option
Why WhiteBit flagged you in a sanctions screening match

Why WhiteBit flagged you in a sanctions screening match

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 sanctions screening on WhiteBit:

  • Name-based false positive: WhiteBit screens all users against OFAC SDN, EU consolidated, UN, and Lithuania-specific sanctions lists. Partial name matches trigger automatic freezes — false positives are common, especially for Middle Eastern, Eastern European, and African names.
  • Nationality flag: If your nationality or country of residence is on a sanctions list (e.g., Iran, North Korea, Syria, Cuba), WhiteBit must freeze your account and may be required to report to Lithuanian Financial Crime Investigation Service (FCIS).
  • Counterparty sanctions exposure: If you've received crypto from an address that interacted with a sanctioned entity, WhiteBit flags your account — even if you had no knowledge of the connection.
  • PEP or sanctions-adjacent person: Politically Exposed Persons and individuals connected to sanctioned entities (family, associates) are flagged by WhiteBit's screening system and may face account restrictions.

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), AML compliance review (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 sanctions screening, so you're guessing at what documentation to provide — and each rejected submission makes the next one harder.

Our approach
How we resolve WhiteBit sanctions screening

How we resolve WhiteBit sanctions screening

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.

Sanctions Screening on WhiteBit — our strategy: We prepare a formal non-association declaration with evidence that you are not the sanctioned individual — different date of birth, different nationality, different address, different occupation — and submit it through the platform's compliance channels with a legal cover letter.

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 OFAC sanctions false positives in crypto covers the documentation and legal strategy in more depth.

1

False Positive Confirmation

We confirm the sanctions match is a false positive by comparing your identity details against the sanctioned individual's known attributes: date of birth, nationality, address, occupation. Partial name matches are the most common cause.

Timeline: 24 hours
2

Non-Association Declaration

We prepare a formal non-association declaration with evidence: your passport/ID, date of birth, nationality, address, occupation, and a sworn statement that you are not the sanctioned individual. We cross-reference OFAC SDN, EU consolidated, and UN sanctions lists.

Timeline: 2–3 days
3

Legal Submission to Sanctions Team

We submit the non-association declaration to {p_name}'s sanctions compliance team — not standard support. Our legal cover letter references {regulator} sanctions screening requirements and the false positive rate for common names.

Timeline: 3–7 days
4

Sanctions Flag Cleared

Sanctions screening false positive resolved — account fully restored. We advise on name variations that may trigger future sanctions matches on {p_name}.

Timeline: until cleared
FAQ

WhiteBit sanctions screening match questions

WhiteBit froze my account because I'm a Russian citizen — is this legal?

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.

Is WhiteBit safer than offshore exchanges for compliance?

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.

Why was I flagged for a sanctions screening match?

Platforms screen all users against OFAC SDN, EU consolidated, UN, and national sanctions lists using name-matching algorithms. If your name is similar to a sanctioned individual — even a partial match — your account is automatically flagged. False positives are extremely common, especially for names from the Middle East, Eastern Europe, Africa, and Asia. The flag doesn't mean you're sanctioned — it means the platform needs to verify you're not the sanctioned person.

What sanctions lists are used for screening?

Platforms screen against: OFAC SDN List (US), EU Consolidated Financial Sanctions List, UN Security Council Consolidated List, UK HM Treasury Sanctions List, and potentially national lists for the platform's jurisdiction. Each list covers different individuals and entities, and a match on any one list triggers a block.

How do I prove I'm not the sanctioned person?

We prepare a non-association declaration that includes: your full legal name, date of birth, nationality, passport number, current address, and occupation — compared side by side with the sanctioned individual's known details from the sanctions list entry. Key differentiators: date of birth (most definitive), nationality, place of residence, and occupation. The more differences we can demonstrate, the faster the flag is cleared.

Nils Silinevics
Nils Silinevics
Partner · AML & Crypto Compliance · Former FIU Investigator
VIEW PROFILE →
GET HELP NOW

WhiteBIT sanctions-screened you?
Let's get it back.

Tell us your nationality, what WhiteBIT flagged, and any sanctions screening details. We respond within 6 hours.

Swiss lawyersNo upfront payment90%+ successWhiteBIT specialists