FinCEN MEXC Global Order: Transmittals Barred 30 Days After Publication

On 6 November 2026, FinCEN released an order under section 9714(a) of the Combating Russian Money Laundering Act finding that MEXC Global, a convertible virtual currency (CVC) exchanger incorporated in the Seychelles, is a financial institution operating outside the United States of primary money laundering concern in connection with Russian illicit finance. The FinCEN MEXC Global order then imposes one special measure: a covered financial institution is prohibited from engaging in any transmittal of funds from or to MEXC Global, whether the value moves as fiat currency or as CVC.

FinCEN’s 6 November pre-publication copy states that the order was pending Federal Register publication. The order will take effect 30 days after its official Federal Register publication date. That leaves an undated window to load the entity perimeter into screening and to settle how inbound CVC from MEXC addresses is handled.

Related reading: FinCEN A7 Network Special Measure: Prohibiting Sub-Agent Transmittals

Key dates for the MEXC Global order

• 6 November 2026: FinCEN posts the signed pre-publication order; Treasury announces it the same day.
• Federal Register publication: pending.
• Effective date: 30 days after the date of Federal Register publication.
• End date: none. The order applies “with no cessation date”.

FinCEN chose an order over a regulation, citing the imminent threats posed by the illicit actors MEXC Global serves, and requests no public comment; parties with relevant information may send it through FinCEN’s contact page.

What the FinCEN MEXC Global order prohibits

The prohibition in section VI.B is a single sentence. Its reach comes from two definitions.

A covered financial institution has the meaning of “financial institution” in 31 CFR 1010.100(t): each agent, agency, branch or office within the United States of a business acting in a listed capacity, which includes banks, securities broker-dealers, money services businesses, casinos, futures commission merchants and mutual funds. CVC exchangers doing business in the United States fall inside it as money transmitters, the classification FinCEN gives MEXC Global itself.

The second definition does more work. Transmittals of funds means “the sending and receiving of funds, including CVC”, and the order applies that meaning in place of 31 CFR 1010.100(ddd). The general definition excludes electronic fund transfers under the Electronic Fund Transfer Act and transfers made through an automated clearinghouse, an ATM or a point-of-sale system.

The order repeats none of those exclusions, so I read the prohibition as reaching ACH and card rails alongside wires and on-chain transfers. A control build that watches only wires and blockchain activity covers less than the text does. The order’s CVC definition also expressly includes bitcoin, which it describes as having legal tender status in at least one jurisdiction.

Who falls inside the MEXC Global definition

MEXC Global means the Seychelles-based exchanger plus its branches, subsidiaries and offices operating as a financial institution in any jurisdiction outside the United States, and any successor entity: a person that replaces any of them by acquiring their assets, in whole or in part, or by carrying on MEXC Global’s affairs under a new name. Footnote 1 names affiliates it includes, without limiting the definition to them:

• MEXC Global Ltd and MX Global Ltd (Seychelles)
• MEXC Estonia OÜ (Estonia)
• GIDA Technology AG (Switzerland)
• MXC Global Ltd (United Kingdom)
• MEXC Global Foundation Ltd and MEXC Singapore Pte Ltd, formerly incorporated in Singapore

Name screening built on the string “MEXC” misses part of this list. MX Global Ltd, GIDA Technology AG and MXC Global Ltd do not contain it, and the order notes the exchanger was called MXC before a 2021 rebrand. The successor clause also reaches renamed operations FinCEN has not listed, so a static list ages from the day it is loaded.

Two boundaries run the other way. MEXC Global branches, subsidiaries and offices located in the United States are expressly excluded. The order identifies MEXC-associated entities and jurisdictions, and lists no deposit addresses attributable to MEXC Global. Footnote 33 separately identifies A7A5 token smart-contract addresses, which are not MEXC deposit addresses, so attributing MEXC deposit addresses requires other evidence. FinCEN’s stated view is that compliance “requires no tools or competencies other than those already employed” in current AML/CFT programs.

Rejecting CVC that arrives from MEXC Global

In its burden analysis (section IV.B), FinCEN says it has “elected to provide within this order for the rejection of certain transmittals of CVC” from MEXC Global and to outline the steps a covered financial institution should take. Footnote 50 concedes there are “few, if any, readily available ways” to reject incoming CVC before receipt. The preamble then describes flexibility to comply where the originating address is no longer accessible, with two examples: CVC that came from MEXC Global but sat in an unhosted wallet for an extended period, and cases where the institution’s risk mitigation procedures would preclude returning funds to MEXC Global. That is the unhosted-wallet exposure covered in our summary of the FATF report on stablecoins and unhosted wallets.

Section VI, as posted, contains no rejection provision. After the prohibition sentence come the order period, reservation of authority, other obligations, penalties and severability. The two earlier section 9714 orders were drafted differently.

The posted order warns that the Federal Register version may vary slightly after editorial review, so whether the published text adds the rejection mechanism the preamble describes stays open until publication. My reading is that preamble discussion explains FinCEN’s intent without supplying the express deemed-compliance wording the Bitzlato and PM2BTC orders carried in their operative text.

SAR and OFAC obligations stay where they were

Section VI.E provides that nothing in the order modifies, impairs or otherwise affects BSA requirements, including SAR filing, or other laws such as OFAC sanctions. Neither the order nor FinCEN’s 6 November release sets a SAR key term for MEXC activity. Treasury’s release announces no OFAC designation of MEXC Global, and OFAC’s 6 November designations did not name it. The order does not itself impose an OFAC-style asset-blocking requirement. Counterparties separately designated by OFAC, such as Garantex, remain subject to the applicable sanctions requirements.

A declined transfer can still be a SAR event. The SAR rules reach transactions “conducted or attempted by, at, or through” the institution; for money services businesses subject to 31 CFR 1022.320, paragraph (a)(2) generally sets a USD 2,000 threshold, alongside the suspicion criteria, for conducted or attempted transactions. Paragraph (a)(3) sets a USD 5,000 threshold for specified money order and traveller’s cheque issuers where the activity is identified through clearance-record or similar reviews.

Declining a proposed MEXC transmittal before execution addresses the prohibition. However, section VI does not specify how to treat CVC already received or provide an express rejection safe harbour. Whether a particular response to incoming CVC complies with the prohibition therefore requires separate assessment. SAR obligations continue independently. Our note on FinCEN’s withdrawn CVC mixing and unhosted wallet proposals covers the CVC obligations that remain in force.

Penalties, exemptions and the record behind the finding

Under section VI.F, a covered financial institution and its officers, directors, employees and agents may be liable for civil or criminal penalties under 31 U.S.C. 5321 and 5322 for willfully violating the order. Section 9714(d) applies those penalty provisions to orders made under subsection (a), and the order’s Executive Order 14294 statement ties criminal liability to willfulness under 31 U.S.C. 5322(a) and (b) and 31 CFR 1010.840. FinCEN reserves authority to impose conditions on transmittals from or to MEXC Global and to grant appropriate exemptions. The order grants none.

The finding rests on public and non-public information. The figures most useful for a counterparty risk review:

• USD 16.7 billion connected to Russian illicit finance and other illicit activities, including sanctions evasion and cybercrime, between May 2021 and May 2026.
• About USD 129 million with Garantex and USD 4.1 million with Grinex after their public designations, with transactions as recently as June 2026.
• More than USD 1 billion in direct transactions with more than 40 Iranian CVC exchangers, within about USD 1.87 billion of exposure to Iran.
• About USD 350,000 received by OFAC-designated DPRK money launderer Sim Hyon Sop between June and September 2025, although his April 2023 designation identified his CVC addresses.

FinCEN assumes that some MEXC Global business is legitimate but says it cannot fully assess the extent of that activity. It concludes that the risks from MEXC Global’s facilitation of illicit activity outweigh any legitimate business conducted there and notes that equivalent services are available through other regulated institutions. For the EU side of Russia-related screening, see our note on the EU 21st sanctions package.

Frequently Asked Questions

Can a customer move their own holdings from MEXC Global to a US account after the effective date?

The prohibition covers any transmittal of funds from MEXC Global and has no carve-out for a customer’s own funds or for legitimate activity. FinCEN has reserved authority to grant exemptions and has granted none in the order as posted. CVC that arrives anyway falls into the rejection question above.

Does a transfer to a MEXC-hosted deposit address count when the address is not named anywhere?

The order lists no MEXC deposit addresses and, unlike the Bitzlato and PM2BTC orders, does not mention accounts or CVC addresses administered on the target’s behalf. A deposit address the exchange controls still delivers the funds to MEXC Global, so on a plain reading a transfer to it is a transmittal “to MEXC Global”. The text is silent on indirect routes through unrelated intermediaries.

Does the order reach a US bank’s branch outside the United States?

The definition borrows 31 CFR 1010.100(t), which covers each agent, agency, branch or office within the United States. On that wording a foreign branch sits outside it, an interpretation the order does not address directly. A US office that itself sends or receives the transmittal is inside it.

Related Articles

• FinCEN A7 Network Special Measure: Prohibiting Sub-Agent Transmittals: the proposed section 9714 rule that FinCEN cites in the MEXC Global record.
• FinCEN CVC Mixing Withdrawal: Mixer and Wallet Proposals Dropped: the 6 October 2026 withdrawals and the US AML obligations that still apply.
• FATF Stablecoins and Unhosted Wallets Report: AML/CFT Implications for EU Firms: FATF’s analysis of unhosted wallet and stablecoin risk.
• EU 21st Sanctions Package: What Screening Desks Must Update: the 23 July 2026 EU Russia package, including its crypto restrictions.
• FATF Travel Rule Implementation: The Enforcement Gap: FATF’s July 2026 update on Travel Rule laws and enforcement.

Key Takeaways

• Screening lists need every affiliate named in footnote 1, the former MXC name and a route for adding successors; FinCEN lists no MEXC deposit addresses (the A7A5 token contract addresses in footnote 33 are not MEXC deposit addresses).
• Without the 1010.100(ddd) carve-outs, ACH, card and other EFT channels belong in scope next to wires and on-chain flows (interpretation).
• The order prohibits covered financial institutions from transmittals to or from MEXC Global. Its preamble discusses rejection of incoming CVC, but section VI provides no express rejection safe harbour. Independent OFAC blocking obligations remain applicable where relevant.
• A declined MEXC transmittal still goes through the ordinary SAR assessment.

Sources and References

• FinCEN, Imposition of Special Measure Prohibiting the Transmittal of Funds Involving MEXC Global, section 9714(a) order, pre-publication text (6 November 2026): fincen.gov PDF
• FinCEN, Federal Register notice page for the MEXC Global order (6 November 2026): fincen.gov
• FinCEN, Operation Economic Outcast Severs MEXC Global’s Access to the U.S. Financial System (6 November 2026): fincen.gov
• U.S. Department of the Treasury, press release sb0685 (6 November 2026): home.treasury.gov
• Section 9714 of Public Law 116-283, as amended by section 6106(b) of Public Law 117-81, note to 31 U.S.C. 5318A: law.cornell.edu
• 31 CFR Part 1010 (7-1-25 edition), sections 1010.100(t), (ff), (ddd) and 1010.840: govinfo.gov
• 31 CFR Part 1022 (7-1-25 edition), section 1022.320: govinfo.gov
• FinCEN, Bitzlato order, 88 FR 3919 (23 January 2023), FR Doc. 2023-01189: govinfo.gov
• FinCEN, PM2BTC order, 89 FR 82499 (11 October 2024), FR Doc. 2024-23430: govinfo.gov
• OFAC, Recent Actions, Iran-related Designations (6 November 2026): ofac.treasury.gov

Preparing for the MEXC Global effective date

Once the order appears in the Federal Register, its publication date fixes the effective date, and the published section VI shows whether FinCEN added the CVC rejection clause or address-level wording that the posted version lacks.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.