RegulationNovember 7, 202611 min read

Binance DOJ settlement: failures and compliance lessons

What the 2023 Binance resolutions found about KYC, sanctions controls, monitoring and governance — and the checks a compliance team can run this quarter.

On 21 November 2023, Binance pleaded guilty to US offences involving its anti-money-laundering programme, money-transmitter registration and sanctions compliance. Its founder, Changpeng Zhao, separately pleaded guilty to failing to maintain an effective AML programme and resigned as chief executive. The corporate criminal resolution comprised $4,316,126,163 in forfeiture and a criminal fine, with credits for payments under parallel agency resolutions (DOJ).

For a fintech, payment service provider, electronic money institution or crypto platform, the useful lesson is not the headline amount. It is how customer identification, geographic restrictions, transaction monitoring and management oversight failed together — and how to test whether the same weaknesses exist in your own programme.

This article summarises public enforcement documents as published in 2023–2024. It is educational material, not legal advice, and it is not a list of currently sanctioned jurisdictions.

The resolution at a glance

These are overlapping obligations, not amounts to add together. The agreements contain substantial payment credits, and forfeiture, disgorgement and civil penalties are different forms of monetary relief.

Proceeding	Amount imposed or agreed	Principal finding or admission	Source
DOJ — Binance	$2,510,650,588 forfeiture plus $1,805,475,575 criminal fine: $4,316,126,163	Binance admitted AML-programme, unlicensed money transmission and sanctions offences.	DOJ release; plea agreement
FinCEN	$3.4 billion assessed; $2.47 billion credited; $150 million suspended; $780 million payable	Wilful failure to register, maintain an effective AML programme and report suspicious transactions.	Consent order
OFAC	$968,618,825 settlement; $898,618,825 satisfied by DOJ payments; $70 million payable	Apparent violations: US users trading with users in sanctioned jurisdictions or blocked persons.	Settlement agreement
CFTC — Binance entities	$1.35 billion disgorgement plus $1.35 billion civil penalty, subject to credits	Unregistered derivatives activity and failures of identification, supervision and compliance controls.	Consent judgment
Zhao — individual	$50 million criminal fine; $150 million CFTC civil penalty	Criminal plea to the AML-programme offence; the CFTC order separately addressed his responsibility.	Criminal judgment; CFTC judgment

Reading the headline correctly

The commonly reported “$4.3 billion” is rounded shorthand for the DOJ corporate resolution, not an instruction to add every agency’s assessment. The agreements credit qualifying payments made under one resolution against obligations under another — FinCEN, for example, credits $2.47 billion paid to DOJ and the CFTC against its $3.4 billion penalty (FinCEN order). Use the signed instruments for the allocation; a press-release headline is not a consolidated cash-payment schedule.

Timeline

14 July 2017 – 30 July 2023: FinCEN’s stated relevant period (FinCEN order).
Approximately August 2017 – October 2022: OFAC’s apparent-violations period. The CFTC judgment uses a different period, at least July 2019 – 27 March 2023. Each agency measured its own population.
20 August 2021: Binance announced broader identity verification, with unverified existing customers moving to withdrawal-only by 19 October 2021. The CFTC judgment found the promised restrictions were not implemented by that deadline.
May 2022: until then, according to DOJ, users who had not completed KYC could keep trading (IRS-CI). The later changes did not erase the earlier conduct.
21 November 2023: the criminal pleas and coordinated resolutions were announced.
14 December 2023: the CFTC consent judgment was filed.
30 April 2024: Zhao was sentenced to four months’ imprisonment and a $50 million fine (judgment).
21 October 2025: a presidential pardon named Zhao’s individual case (grant of clemency). It does not concern Binance’s corporate resolution.

What went wrong, control by control

The working controls below are recommendations drawn from the findings, not statements that every jurisdiction imposes identical requirements. Note the different standing of each source: the pleas are admissions; OFAC describes apparent violations; and the CFTC consent order was entered without the defendants admitting or denying its findings, apart from facts already admitted elsewhere.

KYC and customer identification

The finding. The CFTC judgment describes a route through which customers could deposit, trade and withdraw without KYC as long as they withdrew less than the value of two bitcoin a day. It also records that by February 2022 Binance had verified the identities of only approximately 30–40% of its customers through KYC documentation (CFTC judgment, paragraphs 34 and 39).

FinCEN described something more serious than incomplete onboarding: employees helped commercially valuable US customers change documentation or use offshore entities while keeping material US connections, and broker arrangements obscured underlying users (FinCEN order).

Why it failed. A withdrawal threshold became a substitute for understanding the customer. Elsewhere, collecting new paperwork displaced, rather than resolved, contradictory evidence about ownership, control and location.

A working control. Define the evidence required before each account capability becomes available. Assess incorporation, beneficial ownership, controlling persons, operating location and actual access patterns separately. An offshore registration certificate should not automatically extinguish contrary evidence. For intermediated accounts, document who checks the underlying customers, what your firm receives, and what triggers restriction or termination — and test it on real sub-account records, not on contractual assurances alone.

Sanctions and jurisdiction controls

The finding. OFAC identified at least 1,667,153 transactions, totalling approximately $706,068,127, between US users and users in Iran, Syria, North Korea, Crimea, Cuba, the so-called Donetsk and Luhansk People’s Republics, or blocked persons (OFAC settlement, section II).

OFAC described a matching engine that paired orders on price and time with no control preventing those prohibited pairings. It also described location knowledge drawn from KYC information, IP addresses and telephone numbers, alongside suggestions that users employ VPNs to get round geographic restrictions.

Why it failed. Knowing where a user was did not reliably change what the platform allowed them to do. A geographic policy, a customer declaration and a name-screening result could not make up for access and execution paths that stayed open.

A working control. Connect customer risk decisions to onboarding, login, API access and transaction execution. Reconcile IP and device signals with verified information, and treat VPN indicators as evidence to assess, not automatic proof. Test regional restrictions as well as country restrictions. For an exchange, include internal trades and ledger movements: OFAC noted that trades between Binance users were recorded internally rather than on the blockchain.

Do not merge different measurements. DOJ described more than $898 million in trades between US users and users in Iran from January 2018 to May 2022 (IRS-CI). OFAC’s own schedule lists 1,205,784 Iran trades totalling $599,515,938. These are agency-specific populations, not interchangeable estimates — and they are historical findings under the restrictions that applied at the time, not a current country checklist. For how today’s main lists differ, see OFAC vs UN vs EU vs UK sanctions lists.

Monitoring and suspicious activity reporting

The finding. DOJ stated that Binance did not systematically monitor transactions and never filed a suspicious activity report with FinCEN. FinCEN identified “well over a hundred thousand suspicious transactions” that were not timely and accurately reported (FinCEN order). That wording is not an exact count of missing reports, and the findings should not be rewritten as proof that every flagged transaction was money laundering.

Why it failed. Detection, investigation and statutory reporting were not a functioning chain. Information from service providers or law enforcement did not consistently produce a documented reporting decision.

A working control. Reconcile the transactions entering monitoring against the source ledger, including internal transfers and intermediary activity. Give every alert an accountable owner, an investigation record and a reporting decision. Keep alert creation, investigation and filing distinct: a closed case is not proof that a required report was submitted. Use your own jurisdiction’s reporting rules and deadlines; do not transplant US requirements unchanged into an EMI or PSP programme elsewhere.

Governance and management conduct

The finding. FinCEN described preferential treatment for VIP customers, changes to internal country reporting and efforts to conceal continuing US activity. The CFTC judgment additionally records supervisory failures and instructions to evade controls.

Why it failed. Revenue interests could override compliance decisions, and management information became less reliable. A written policy offered little protection when exceptions contradicted its purpose.

A working control. Remove unilateral commercial overrides of legal restrictions. Require an independent approver, a documented rationale, an expiry and a later review for any permissible exception, and keep the underlying location evidence when a customer’s classification changes. Give the board unresolved control gaps, overdue investigations and the concentration of exceptions — not only training completion and alert volumes.

Remediation and independent scrutiny

The DOJ agreement required an independent compliance monitor for three years. FinCEN imposed a separate five-year monitorship with access to records and personnel, and required a historical review of suspicious-activity reporting (FinCEN). OFAC’s agreement records commitments on user and transaction screening, geolocation, customer due diligence and lookback reviews. These describe required remediation, not an independent certification that every control now works.

What to check this quarter

Use these tests to produce evidence, not another policy refresh.

Map regulatory scope. Reconcile products, legal entities and actual customer locations against your permissions and registrations; record open legal questions.
Test account capabilities. Try deposits, transfers, trading and API access from an unverified test account and confirm the restrictions hold.
Challenge jurisdiction changes. Sample customers moved to another country classification; check the earlier evidence and the approval rationale were kept.
Inspect valuable customers. Compare VIP and standard restrictions, including allowlists, service-team permissions and temporary exceptions.
Test intermediary visibility. Trace one underlying customer through a broker or omnibus arrangement to what your investigators can actually see.
Exercise geographic controls. Test restricted-country and regional scenarios across web, mobile, API and already-open sessions.
Challenge conflicting signals. Check how your programme resolves a mismatch between documents, beneficial ownership, IP location and device data.
Simulate a screening failure. Make an in-scope list unavailable and confirm the workflow records the gap and routes the case to review instead of clearing it.
Reconcile monitoring coverage. Compare ledger events with the events your monitoring ingested; investigate anything missing or duplicated.
Trace reporting decisions. Follow selected alerts through investigation, escalation, filing or documented non-filing, and submission acknowledgement.
Review overrides and records. Identify who can change restrictions or customer data, then inspect their activity logs and retention settings.
Independently retest fixes. Ask someone outside the team that built a fix to reproduce the original failure before you close it.

How screening evidence helps

Design the evidence record to show the customer information used, the list versions searched, whether each source was available, any potential matches that need review, the investigation rationale and the final approval. Keep screening decisions connected to account restrictions and monitoring cases.

Verifex screens people and companies against official sanctions lists and PEP data through its sanctions screening API, records the list versions each screening used, and marks a screening it cannot complete as requiring review, never as clear. A name match is returned as a candidate for human review (“potential match — review required”), and no match result is treated as a clearance. Check current list availability on Sources & Freshness, and see PEP screening for enhanced due diligence.

Those functions support parts of a control framework. They do not replace identity verification, jurisdiction analysis, ownership assessment, reporting decisions or accountable management.

Sources

This is educational material about screening operations. Verifex provides screening infrastructure and evidence records, not legal advice, transaction approval, or a replacement for your risk-based compliance program.

All blog

FAQ

Questions about this topic.

Something else? Talk to us.

Why was Binance fined?

Binance admitted corporate offences involving its anti-money-laundering programme, failure to register as a money transmitter and sanctions violations. Parallel proceedings by FinCEN, OFAC and the CFTC addressed further Bank Secrecy Act, sanctions and derivatives-market requirements; describing the whole resolution as a single KYC fine misses that distinction.

How much was the Binance DOJ settlement?

The corporate criminal resolution totalled $4,316,126,163: $2,510,650,588 in forfeiture and a $1,805,475,575 criminal fine. Parallel agency amounts overlap through payment credits and should not simply be added to that headline.

What were Binance's OFAC violations?

OFAC identified at least 1,667,153 transactions, totalling approximately $706 million, in apparent violation of several sanctions programmes, involving US users and users in sanctioned jurisdictions or blocked persons. Its settlement was $968,618,825, most of it satisfied by payments under the DOJ resolution.

Did Binance help users bypass KYC?

FinCEN described employees helping certain US VIP customers alter documentation or use offshore entities to obscure US connections, and OFAC described suggestions that users employ VPNs to get round geographic restrictions. The findings concern deliberate circumvention, not only customers defeating otherwise effective checks.

What happened to Changpeng Zhao?

Zhao pleaded guilty to failing to maintain an effective AML programme, resigned as CEO, and on 30 April 2024 was sentenced to four months in prison and a $50 million criminal fine. A presidential pardon dated 21 October 2025 names his individual case, United States v. Zhao; it does not concern Binance's corporate resolution.

Was Binance's monitor appointed for three or five years?

Both, under different instruments. The DOJ agreement required an independent compliance monitor for three years; FinCEN's consent order imposed a separate five-year monitorship. These are the original terms, not a statement of the arrangements in force today.

Run a screening and inspect the decision record.

The free trial gives you 5 screens on the Starter source set: sanctions, PEP and watchlists. Coverage stays explicit when a required source is unavailable.

Start screening free Talk to us