1. Check the Order’s Authority and Scope
FinCEN issued the MEXC order under Section 9714(a) of the Combating Russian Money Laundering Act. It is a federal measure, separate from state licensing rules.
The announcement came on November 6, 2026. Federal Register publication followed on November 10. The prohibition takes effect on December 10, with no stated end date.
Identify the Covered Institution
The order uses the financial institution definition in 31 CFR § 1010.100(t). A payment company’s activities, rather than its business label, determine whether it falls within scope.
For institutions handling cross-border payments, the order adds a specific restriction to broader banking and financial services obligations.
Identify the MEXC Entity
The definition includes overseas MEXC branches, subsidiaries, offices, and successor entities. A change of name may not remove an entity from scope.
US-located branches, subsidiaries, and offices are expressly excluded from that definition. This does not authorize transfers involving covered overseas entities or override other laws.
2. Which Transfers Require Further Review?
The order defines transmittals as sending and receiving funds, including convertible virtual currency, or CVC. Its definition replaces the usual definition in § 1010.100(ddd) for this purpose.
Section 9714 compliance therefore requires examining the actual source and destination of funds.
Trace the Payment Path
An intermediary may obscure MEXC’s involvement. Review:
- Who sends and receives the funds.
- Whether an intermediary acts for MEXC.
- What supports a wallet’s connection to MEXC.
- When the relevant transfers occurred.
- Whether the evidence shows current involvement or an older connection.
An analytics score can flag a transaction for review. It cannot settle the legal question.
The order provides no fixed number of wallet hops that makes a transfer permissible. A vendor’s screening threshold is not a legal safe harbor.
Resolve Uncertain Matches
A direct payment, an uncertain wallet label, and an older transfer through another wallet require different factual assessments.
Record what is known, what is missing, and what could change the result. Missing information alone does not establish that a transaction falls outside the prohibition.
3. Match Controls to the Transaction’s Status

A FinCEN enforcement action involving a crypto exchange can affect banks and payment providers with no direct exchange relationship.
The following controls are practical recommendations. The order does not prescribe a particular software system or checklist.
Review Outgoing Transfers before Release
Before December 10, teams should identify payment routes that could carry prohibited funds transmittals.
A focused review should cover:
- Verified entity names and wallet information.
- Fiat payment routes and intermediaries.
- Authority to pause payments during review.
- Responsibility for unresolved matches.
- Tests of revised screening controls.
Connect these changes to the existing AML compliance process. Assign unresolved cases to a person authorized to make the handling decision.
Internal approval cannot authorize a prohibited transfer. FinCEN retains authority to grant appropriate exemptions.
Assess CVC Already Received
A recipient may lack the technical ability to stop an incoming on-chain transfer.
The order’s explanation recognizes this limit and permits consideration of individual circumstances. It does not create a blanket instruction to return funds automatically to MEXC.
Preserve the transaction record and obtain a handling decision before moving the assets further.
| Transaction Status | Review Focus | Supporting Record |
|---|---|---|
| Outgoing payment awaiting release | Recipient and payment route | Screening result and decision |
| CVC already received | Source, technical limits, and handling options | Transaction hash and review timeline |
| Uncertain indirect connection | Attribution reliability and missing facts | Evidence supporting or weakening the match |
Outgoing payment awaiting release
- Review FocusRecipient and payment route
- Supporting RecordScreening result and decision
CVC already received
- Review FocusSource, technical limits, and handling options
- Supporting RecordTransaction hash and review timeline
Uncertain indirect connection
- Review FocusAttribution reliability and missing facts
- Supporting RecordEvidence supporting or weakening the match
4. Document the Decision and Control Changes
A closed alert should explain the result. “Reviewed by compliance” does not show why the reviewer accepted or rejected a match.
The file should connect the evidence, applicable restriction, and action taken.
Preserve the Supporting Evidence
A useful review file includes:
- Amount, asset, network, and timestamps.
- Payment instructions or transaction hashes.
- Wallet attribution sources and dates.
- Entity and payment-path findings.
- Missing facts and follow-up efforts.
- Decision, approver, and reasons.
If a wallet label changes, preserve the earlier evidence and record the update separately. This keeps the original decision understandable.
Separate Handling from Reporting
Keep configuration versions, test results, implementation dates, and assigned responsibilities. Distinguish deployed controls from unfinished changes.
The order preserves existing BSA and OFAC obligations. Transfer handling and reporting therefore require separate assessments under the applicable anti-money laundering compliance procedures.
A MEXC alert does not itself establish a criminal offense or automatically trigger an OFAC asset freeze.
5. Frequently Asked Questions
Do Other Crypto Rule Withdrawals Cancel This Order?
No. FinCEN’s October 2026 withdrawals concerned proposals involving certain unhosted-wallet transactions and CVC mixing.
Those separate withdrawals do not cancel the MEXC order.
Does a MEXC Alert Automatically Require a SAR?
No. Apply the suspicious activity reporting rule governing the institution and the facts identified during review.
Document that assessment separately from the transfer decision. Observe applicable filing deadlines and SAR confidentiality requirements.
18 Nov, 2026

