Skip to content

Stablecoins 5 min read

Brazil's eFX Virtual-Asset Settlement Rule: Resolution 561

What Brazil's BCB Resolution 561 requires for the overseas-counterparty leg of eFX payments, when it took effect, and what operators should verify.

By Shaun Toh Published Updated
TL;DR

Since 1 October 2026, Brazil's eFX rules require the overseas-counterparty settlement leg to use an FX transaction or non-resident BRL account movement. Virtual assets are barred on that leg; the rule does not describe any named provider's architecture.

The rule is in force. Since 1 October 2026, Article 50 of Brazil's eFX framework has required a payment or receipt between an electronic foreign-exchange (eFX) provider and its overseas counterparty to use either a foreign-exchange transaction or a movement in a non-resident account denominated in Brazilian reais. Virtual assets cannot be used for that leg. BCB Resolution 561 made the amendment to Resolution 277.

That is a narrower finding than “Brazil banned stablecoins.” It describes a specific regulated service and the payment between the provider and its overseas counterparty. It does not identify which businesses use virtual assets on that leg, or determine how unrelated virtual-asset services are regulated.

What the text changes

Article 50 sets out two permitted routes for the covered payment or receipt: an FX transaction or a movement in a non-resident BRL account held in Brazil. It expressly bars virtual assets for that leg. The text does not say that every cross-border payment, every customer-facing crypto transaction, or every domestic Pix transfer is an eFX provider-counterparty settlement. The classification of a particular product and its transaction legs matters.

A customer payment and the provider's settlement with an overseas counterparty can be different operations. An operator should therefore map the complete chain before using a headline about stablecoins to decide whether a route is compliant. The Brazil market guide covers Pix, cards, licensing and the broader checkout context.

The operator check

  1. Identify the Brazil-facing service and whether it falls within the eFX framework in Resolution 277.
  2. Map the payment or receipt between the eFX provider and its overseas counterparty, including any partner that performs that leg.
  3. Establish whether that leg uses a documented FX transaction or a movement in an eligible non-resident BRL account. If virtual assets appear in that leg, investigate the arrangement against Article 50 before continuing it.
  4. Confirm permissions, account structure and records with the regulated counterparties and Brazilian counsel. The published rule does not validate any provider's private architecture.

This is a decision framework for investigating a specific flow, not a conclusion that a named company breaches the rule. Nor does the BCB text alone establish a universal cost or speed difference between the permitted routes and a virtual-asset route. Those economics depend on the actual counterparties, prices and settlement design.

Sources and scope

The cited provisions support the settlement-leg conclusion above. They do not support attributing a non-compliant architecture to Wise, Nomad, Braza Bank or any other named provider, so this reference makes no such claim.

Shaun Toh By Shaun Toh · Director, Digital Payments · Razer

More Stablecoins briefings