FinCEN drops wallet and mixing proposals, changing crypto compliance plans

FinCEN has withdrawn two long-running digital-asset proposals, ending the prospect of the additional reporting systems described in those rulemakings. Its 5 October announcement was followed by withdrawal notices effective on 6 October. For banks, money-services businesses and crypto platforms, the immediate consequence is a narrower compliance-development pipeline, rather than the disappearance of their existing financial-crime responsibilities.[1][2][3][4]

The two abandoned regimes covered different activity

The proposed foreign-hosted category covered institutions outside the BSA framework in jurisdictions named by FinCEN. The two thresholds also had different functions: retaining information and submitting a report.[2]

A hypothetical example illustrates the former aggregation test. Assume two otherwise covered transfers by the same customer of $6,500 and $4,500 within 24 hours. Their $11,000 total would exceed the proposal’s reporting threshold even though neither transfer individually did. The withdrawal removes that proposed reporting route. Any assessment under an independently applicable rule must still be made on its own terms; the example does not decide that separate question.[2][4]

The mixing decision also withdraws the underlying finding

FinCEN’s mixing notice identifies concerns that the proposal’s broad definition could restrict legitimate activity and create a large reporting burden. The proposed reports would have included transaction and wallet identifiers, amounts, dates and a narrative. FinCEN nevertheless says it will continue monitoring mixers for illicit-finance indicators and may take further action.[3]

The commercial distinction is between a specialised reporting obligation and risk assessment. A business can remove a build item whose sole purpose was to implement the abandoned proposal without concluding that the same transaction is immaterial to every other control. A disciplined change review would trace each proposed form, data field and alert to its legal or business purpose before retiring it. Shared data used by another control may still have value.

Existing business models still determine BSA responsibilities

FinCEN’s established CVC guidance applies money-transmitter analysis to what a business actually does. Non-exempt money transmitters have registration, AML-programme, reporting and recordkeeping obligations; applicable funds-transfer and travel rules also matter. Banks and SEC- or CFTC-regulated institutions instead sit within their relevant BSA categories. A technology label alone does not decide which rules apply.[4]

That matters for a platform combining execution, custody and transfers. The withdrawal does not turn every service into a single exempt activity. The useful implementation question is which legal entity performs each function, receives the value, instructs the transfer and maintains the customer relationship. Mapping those responsibilities makes it easier to retire obsolete project work while retaining the controls needed for the business that continues to operate.[4]

Neither notice quantifies industry cost savings. The effect will depend on how far each institution had progressed with implementation and whether its proposed systems were dedicated or shared. The clearest near-term benefit is certainty about the fate of these two pending rulemakings, rather than a published estimate of lower compliance spending.[2][3]

Report an error or submit an update