Brazil's self-custody wallet rule is a Central Bank of Brazil (BCB) requirement that authorized institutions report to COAF, the national financial intelligence unit, every transfer of virtual assets to or from a self-custodied wallet worth US$10,000 or more. It applies from October 1, 2026. The provider files the report, not the user.
What Resolution 591 requires
The rule sits in Article 49 of Circular 3.978/2020, the BCB's anti-money-laundering circular. Article 49 lists operations that must always be reported to COAF, whatever the institution's own suspicion. Until this year the list held three items, all about cash of R$50,000 or more. Resolution BCB 591, dated September 30, 2026, rewrites the article as a caput with five incisos and adds two items: inciso IV, cash foreign exchange of US$10,000 or more, and inciso V, the self-custody item: "as operações relativas a transferências de ativos virtuais para ou de carteiras autocustodiadas de valor igual ou superior ao equivalente a US$10.000,00."
The trigger is the amount and the wallet type, not suspicion.
The threshold is US$10,000 or the equivalent, per operation.
It runs both ways: a transfer into a self-custodied wallet and a transfer from one both count.
The normal deadline is the next business day after the operation. Resolution 591 carves out the start: for operations contracted between October 1 and December 31, 2026, Article 49 §2 sets the filing date at the first business day of January 2027, for inciso IV and inciso V alike.
Lumx wallets are custodial, with BitGo as custodian, so the customer does not control the keys and a Lumx customer's own wallet is never the self-custodied side of this rule. The self-custodied side is the external address a customer sends to or receives from.
Which resolution is in force: 588, 591, 521 and 584
Four BCB resolutions touch self-custody, and documents written in late September still cite a revoked one.
Resolutions on self-custodied wallets, read in the BCB's normative database on November 1, 2026.
Date | Resolution | What it does | In force |
November 10, 2025 | BCB 521 | Defines a self-custodied wallet and requires the provider to identify its owner | February 2, 2026 |
August 7, 2026 | BCB 584 | Adds a 24-hour precautionary hold on some transfers to self-custodied wallets | January 1, 2027 |
September 23, 2026 | BCB 588 | First version of the US$10,000 report | Revoked by 591 |
September 30, 2026 | BCB 591 | Restates the report as Article 49, inciso V (next to the new cash-FX inciso IV), and sets the January 2027 filing date for October to December | Date of publication (October 1, 2026) |
Resolution 591's Article 2 revokes Resolution 588, so a citation to 588 now points to a revoked text.
Resolution BCB 520 of November 10, 2025 matters here too. Its Article 87 tells virtual asset service providers to follow the regulation that applies to BCB-authorized institutions, as applicable, and its Article 88 gives providers already operating a transition period to apply for authorization. Lumx applied for its SPSAV authorization and operates under that transition regime. The licensing picture is in the PSAV license explainer and the 2026 Brazil regulation guide.
What counts as a self-custodied wallet?
A self-custodied wallet is one whose owner controls the private key and can move the funds without a virtual asset service provider taking part. That is the definition in Resolution BCB 521, which inserted it into Article 76-A, §1, inciso II of Resolution BCB 277/2022: "aquela cujo proprietário detém o controle da respectiva chave privada, sendo capaz de movimentá-la sem necessidade de participação de prestadora de serviços de ativos virtuais."
How the Resolution 521 definition sorts common wallet types. A given wallet's classification is for the provider and counsel.
Wallet | Self-custodied under the definition | Reason |
Mobile or browser wallet where the user holds the seed phrase | Yes | Owner controls the key |
Hardware wallet | Yes | Owner controls the key |
Deposit address at an exchange | No | A provider holds the key and takes part in every movement |
Wallet at a provider that holds the keys | No | Same reason |
Multisig or smart-account wallet | Depends | Yes if the owner's keys alone can move funds; no if a provider's key can act without the owner |
The same Article 76-A, §5 adds a duty on the provider: identify the owner of the self-custodied wallet and document the processes that check the origin and destination of the assets. Annex II-A lists what the provider sends the BCB for each such transfer: date, amount, customer, the wallet owner's identification and whether the wallet was origin or destination. Article 76-A covers transfers that involve no international payment, which is why the rule lives in the foreign exchange regulation.
Every Lumx customer gets a custodial wallet on each supported blockchain, provisioned with the customer and enabled once verification reaches approved, and the customer does not hold the keys. See custodial wallets on Lumx and our explainers on what a custodial wallet is and on custodial versus non-custodial wallets for businesses.
Who has to report a self-custody transfer in Brazil?
The filing duty sits with the institution; everyone else feels it through questions and records.
Who does what under the rule. The first two rows follow the text of Resolutions 591 and 521; the last three are practical consequences, not text from the resolutions.
Actor | Role |
Institution authorized by the BCB, including a virtual asset service provider (VASP, the FATF term; see what a VASP is) | Identifies the wallet owner, records the transfer and files the COAF report |
Brazilian individual or company with its own wallet | Is identified as the owner of that wallet; the transfer is reported when it reaches US$10,000 |
Platform whose Brazilian users connect external wallets | In practice, expect your provider to ask whether each wallet is self-custodied, because the provider must identify the owner |
Company outside Brazil paying Brazilian recipients through a provider | Usually files nothing; in practice, expect its provider to ask more about large transfers |
Company paying Brazilian recipients in reais over Pix | No wallet on the Brazilian side of that leg, so the rule does not reach it |
What happens to an institution that does not report? Resolution 591 cites Law 9.613/1998 as its legal basis (Articles 10, 11 and 11-A), and Article 12 of that law lists the sanctions for breaching Articles 10 and 11: a warning, a fine, temporary disqualification of administrators, and revocation or suspension of the institution's authorization. They can be applied separately or together. This post cites Law 9.613/1998 by number and does not quote the fine amounts, so check them in the statute with counsel.
On Lumx's own position: Lumx applied for its SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais) authorization and operates under the Article 88 transition regime. External transfers are identified and reported to COAF as the rule requires, Lumx asks Brazilian customers about self-custody on an external transfer, and where a hold is needed it is applied through a transactional RFI (request for information, a compliance hold that asks for a document before a transaction clears). Because the authorization request is filed, Lumx keeps its own banking access, which Article 91 of Resolution 520 makes a condition from November 6, 2026.
On Lumx, the payer and the payee in a payout both have to be onboarded customers or registered destinations, and pooling funds for unboarded third parties is not allowed (Nested Payments rules).
What changes on January 1, 2027 with the 24-hour hold
Resolution BCB 584 is the bigger operational change. It adds Article 2-B to Resolution BCB 142/2021 and takes effect on January 1, 2027. A provider may execute a transfer order of virtual assets only 24 hours after the funds that fund it arrived in the wallet, in reais or as virtual assets, when the destination is a self-custodied wallet or a foreign entity operating in the virtual asset market.
The hold is not a freeze:
It is precautionary, for a risk analysis, and does not make assets permanently unavailable.
It applies when the operation exceeds US$10,000, per operation or as the customer's total that day, or when the provider's own risk policy flags it.
The provider must tell the customer that the hold was applied, that it is precautionary and for how long.
When the 24 hours end, the provider either lifts the hold or rejects the operation. It may lift early on a reasoned, documented decision.
Stablecoins are named as covered.
A platform with Brazilian users should show "up to 24 hours" instead of "minutes" for large outgoing transfers to personal wallets from that date.
On Lumx, a transfer is a single transaction that moves from TRANSFERRING_STABLECOIN to SUCCESS and fires the transfer.success webhook, and every customer has per-transaction and daily limits on the transfer type. Those limits are in the transaction limits documentation: the default per-transaction ceiling is $7,500 at the KYC (know your customer, for individuals) Standard tier and $50,000 at the KYB (know your business, for companies) Standard tier, so a business can pass the US$10,000 line in a single transfer. The $7,500 per-transaction default for an individual sits below the Article 49 inciso V threshold, which is per operation. But the $15,000 daily limit at the KYC Standard tier can still pass the daily-total trigger of Resolution 584, since two $7,500 transfers add up to more than US$10,000. A business at $50,000 per transaction can pass either one.
How to prepare a platform for the rule
The preparation is mostly data work.
Map every place a Brazilian user can add an external address: onboarding, withdrawal settings, payout destinations.
Ask in plain terms whether a third party can move funds out of the wallet without the user's approval. If nobody can, the wallet is self-custodied.
Store the answer next to the address, with who answered and when.
Backfill saved wallets that have no answer before the field becomes mandatory with your provider.
Tell users that large transfers to or from personal wallets are reported under Central Bank rules, and promise nothing about a specific report. Show the 24-hour window in January release notes.
I would ask the self-custody question at the moment the address is added, never later in a settings page, and I would treat the answer as a compliance record rather than a user preference. The reason is that every report downstream inherits that one answer: a wrong "no" produces a report nobody files, a wrong "yes" produces one nobody needed, and both are wrong the same way every time the wallet is used. I recommend a platform lock the answer after it is saved and send corrections through a reviewed process.
When this rule is the wrong thing to worry about
The rule covers wallet-to-wallet transfers with no fiat leg, which is not most payments in Brazil.
A USDC payout to a Brazilian bank account over Pix ends in a bank account. The recipient never holds a wallet, so the self-custody test never runs on that leg.
A company that holds balances only inside a provider's custodial wallets has no self-custodied side in its own flows.
Transfers below US$10,000 are not reported under Article 49, inciso V, although a provider's risk policy can still ask questions about them and can still apply the 24-hour hold under Resolution 584.
The rule fits when your Brazilian users withdraw to wallets they control or deposit from one.
On Lumx, a Pix (Brazil's instant payment system, run by the Central Bank) payout is an off-ramp from the customer's wallet to a registered destination, with the customer shown to the recipient as the payer. The currency pair and rail are on the USDC to BRL page and in the coverage list.
What a transfer to a self-custody wallet looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
On Lumx, the Transfer endpoint sends USDC or USDT from a customer's wallet to another customer or to an external address, and the wallets documentation names a self-custody wallet as one of the destinations. The customer behind the transfer has passed KYC or KYB before the wallet is enabled. Screening of the address and monitoring use Chainalysis, and identity checks use Sumsub.
A transfer that crosses a limit is rejected with a 422 and the code TRANSACTION_LIMIT_EXCEEDED. A transaction under monitoring can also pause for an RFI, raised at customer, account or transaction level. Lumx handles compliance and conversion inside the API.
Methodology and sources
Every resolution below was read in the BCB's normative database, through the page behind the linked address, on November 1, 2026. Quoted passages are in the original Portuguese; the English is not an official translation. Law 9.613/1998 is cited by number and article, and its Article 12 sanctions are described but no fine amounts are quoted. The Lumx statements come from the Lumx docs pages on wallets, transactions, transaction limits, destinations and RFI, read the same day.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Next step: size your exposure in the transaction limits documentation and custodial wallets on Lumx.
Circular BCB 3.978/2020 checked against bcb.gov.br on November 1, 2026. Resolution BCB 591/2026 checked against bcb.gov.br on November 1, 2026. Resolution BCB 588/2026 checked against bcb.gov.br on November 1, 2026. Resolution BCB 584/2026 checked against bcb.gov.br on November 1, 2026. Resolution BCB 521/2025 checked against bcb.gov.br on November 1, 2026. Resolution BCB 520/2025 checked against bcb.gov.br on November 1, 2026. Law 9.613/1998 cited by number and article (Articles 10, 11, 11-A and 12).
What is Brazil's self-custody wallet rule?
It is item V of Article 49 of the Central Bank's Circular 3.978, added by Resolution BCB 591 of September 30, 2026. Institutions authorized by the Central Bank must report to COAF every transfer of virtual assets to or from a self-custodied wallet worth US$10,000 or more, from October 1, 2026. On Lumx, a transfer to an external address is a Transfer transaction from the customer's wallet, and the customer is KYC or KYB approved before that wallet is enabled.
Is self-custody banned in Brazil?
No. Nothing in Resolutions 591, 521 or 584 prohibits holding stablecoins in a wallet you control or moving them to and from a regulated provider. The rules add a report above US$10,000, a duty on the provider to identify the wallet owner, and from January 1, 2027 a 24-hour precautionary hold on some transfers. Lumx supports moving USDC or USDT from a customer's wallet to any external address, including a self-custody wallet, through the Transfer endpoint.
Does the rule apply to a company outside Brazil?
The duty to report belongs to the institution authorized by the Central Bank, so a foreign company does not file the report itself. It can still feel the rule: its provider may ask whether a Brazilian recipient's wallet is self-custodied and may ask for more on large transfers. A company paying Brazilian recipients through Lumx onboards each payer and payee as a customer or registered destination, because Lumx needs to see every party in a payment.
Does a Pix payout trigger the report?
No. The report covers transfers of virtual assets to or from a self-custodied wallet, and a Pix payout ends in a bank account with no wallet on the Brazilian side. The leg that comes before it, if the sender funds from a personal wallet, can fall under the rule. On Lumx, a Pix payout is an off-ramp from the customer's wallet to a registered destination, and the recipient sees the customer as the payer.
When are the first reports due?
Resolution 591 sets the first business day of January 2027 for transfers contracted between October 1 and December 31, 2026. After that, the normal deadline of the next business day applies. The records have to exist from October 1, because the transfers are in scope from that date. Each Lumx transfer moves from TRANSFERRING_STABLECOIN to SUCCESS and fires the transfer.success webhook, which gives a platform a dated record for every transfer.
