#
Brazil's VASP licensing regime, built on Law 14,478/2022 and BCB Resolutions 519-521, has been in force since February 2, 2026, requiring authorisation, minimum capital (R$10.8M-R$37.2M), and applying a nine-month transition window closing in November 2026, after which non-compliant firms must cease operations. Foreign VASPs face an equivalent local-establishment requirement. A sourcing-tier contradiction affecting several Confirmed-tier claims in this module has been escalated for human verification and is not yet resolved.
The capital bars attached to this framework are not nominal. Firms face a baseline minimum capital requirement of roughly R$10.8 million (approximately US$2 million), rising as high as R$37.2 million depending on business type -- a bar high enough to function as a filter on market entry, particularly for smaller or newer VASPs. Existing firms already operating in Brazil before the new rules took effect are inside a nine-month transition window running from February 2026, with a compliance deadline in November 2026; firms that have not completed authorisation by that point are required to cease operations rather than simply facing supervisory censure. This is a materially harder deadline than a typical soft-launch grace period, and it is the single most consequential compliance event in Brazil's crypto calendar this cycle. Foreign VASPs serving Brazilian clients face the same underlying choice in substance: establish a locally authorised entity under the new framework or risk being barred from serving the market, though the strength of this specific inference rests on secondary reporting rather than a direct BCB statement to that effect.
One caveat needs to travel with this module's Confirmed-tier claims. An internal sourcing check this cycle surfaced a contradiction between the reported tier counts in the run's own metadata (all reporting zero at every tier) and the actual tier tags carried by the sources backing several of this module's core claims -- a BCB press release tagged T1, and academic BCB material tagged T2. That contradiction has been escalated for human verification rather than resolved automatically, and the claims it touches -- the core authorisation requirement, the Resolution 519 pathway update, and a related cross-border classification claim -- are held pending that resolution. The underlying facts are not in dispute; the question is whether the sourcing metadata supporting their Confirmed rating is itself trustworthy, and that has not yet been settled.
Outlook
The November 2026 transition deadline is the module's dominant near-term marker: it will reveal how much of Brazil's existing VASP population completes authorisation versus exits the market outright, and by extension how consolidated the licensed industry becomes. Separately, the primary statutory texts underlying this module -- Law 14,478/2022 itself and Decree 11,563/2023 -- have not yet been retrieved directly from Planalto or BCB primary sources this cycle; firming up that anchoring, alongside resolving the sourcing-tier contradiction noted above, is the priority before this module's claims can be treated as fully clear for publication.
No periodic updates recorded against this sub-brief.
Sources and findings (5)
- T1Banco Central do Brasil (BCB) — VASPs to operate, classified as intermediary, custodian, or virtual asset broker, under Resolution BCB 520retrieved M5bindingin forcenew
- T1Resolution BCB 519 — VASP operating-authorisation process, updating rules for segments previously regulated by CMN (FX brokers, securities brokers/distributors)retrieved M4bindingin forcenew
- T4Existing VASPs (transition cohort) — November 2026 compliance deadline (nine-month transition from Feb 2, 2026), after which non-compliant firms must cease operationsretrieved M4bindingin forcenew
- T4VASP firms (BR) — R$10.8 million baseline (~US$2M), up to R$37.2 million for certain business typesretrieved M4bindingin forcenew
- T4Foreign VASP firms serving Brazilian clients — the new BCB VASP framework or risk being barred from the marketretrieved M4bindingin forcenew