Brazil expands reporting to $10K self-custody transfers

TLDR

Brazil will require banks and crypto platforms to report crypto transfers of $10,000 or more between their services and self-custody wallets to the countrys anti-money-laundering authority.

1. From 1 Oct 2026, Resolution BCB 588 makes institutions report large self-custody deposits and withdrawals to Coaf by the next business day, even without suspicion of wrongdoing.
2. The rule mainly affects high value users and trading firms, increasing data collection and reducing privacy at the on and off ramp, but it does not ban self-custody or large transfers.
3. A second rule from 2027 can delay some outbound transfers, and similar reporting regimes like EU DAC8 suggest a broader trend of tighter monitoring of self-custody boundaries.

Confidence: high because this relies on published Brazilian central bank resolutions and detailed regulatory summaries.

Deep Dive

1. What Brazil Is Changing

Brazils central bank adopted Resolution BCB 588, which requires financial institutions to report crypto transfers of $10,000 or more involving self-custody wallets to Coaf, the national financial intelligence unit, starting 1 Oct 2026.

Reporting covers both directions:

1. Deposits from self-custody wallets into exchanges, banks, or other regulated providers.
2. Withdrawals from those institutions to self-custody wallets.

According to the central bank summary, reports must be filed by the next business day and are triggered by amount and transaction type, not by a prior suspicion finding, extending Brazils anti money laundering framework to large but otherwise legitimate movements across the self-custody boundary. One detailed overview notes that Brazil handled about $252.5 billion in crypto activity and leads Latin America by adoption, so this rule applies in a large and active market.

2. Impact On Users And Platforms

For typical retail users, everyday transfers below $10,000 should not trigger these new reports, so day to day self-custody use remains largely unchanged.

High value individuals, OTC desks, and trading firms, however, can expect:

1. More detailed KYC and address information requests when funding or withdrawing large amounts to self-custody.
2. Automatic reporting of those transfers to Coaf, reducing anonymity at size even if no suspicious activity is suspected.

Institutions must also upgrade systems to flag self-custody counterparties, value transactions, and submit reports automatically. In practice, many may adopt internal thresholds below $10,000 or temporarily hold transfers they consider higher risk, creating potential friction and timing uncertainty for large moves.

3. What To Watch Next

A related Resolution BCB 584, effective 1 Jan 2027, introduces a precautionary holding procedure for certain outbound transfers from regulated institutions, allowing them to pause transfers while they perform extra checks. This can further slow some large exits to self-custody.

Internationally, Spains tax authority has clarified that self-custody holdings controlled by the users own keys are excluded from Form 721 reporting at the 50,000 level, while the EUs DAC8 regime requires crypto asset service providers to report movements between platforms and external addresses. Brazils move places it on the stricter side of this spectrum by directly targeting large self-custody flows.

The key variables to monitor are how Brazilian institutions interpret self-custody, whether they implement address whitelisting, how often precautionary holds are used, and whether other large markets adopt similar self-custody reporting rules.

Conclusion

Brazils new rule does not restrict self-custody, but it turns large transfers between exchanges and private wallets into routinely reportable events. That tightens the compliance net at the perimeter between regulated platforms and on chain activity.

For crypto users and businesses connected to Brazil, the practical impact is concentrated in high value moves, where greater transparency and potential delays at the on and off ramp become part of the operating environment.