Regulation

COAF reporting for companies paying with stablecoins in Brazil

COAF reporting is the duty of Brazil's obliged entities to report suspicious and high-value operations. Who files for a stablecoin payment, what, and when.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: COAF reporting for companies paying with stablecoins in Brazil
Cover image for Lumx blog article: COAF reporting for companies paying with stablecoins in Brazil

COAF reporting is the duty of Brazil's obliged entities to send the financial intelligence unit (COAF) communications about suspicious operations and a few high-value ones, under Law 9.613/1998. A company that pays suppliers with stablecoins files none itself unless it is also an obliged entity. Its virtual asset provider files the reports the rules require for the payments it processes.

Licensing is in the PSAV license explainer, the wider rulebook in Brazil's stablecoin regulation for 2026.

Who is an obliged entity under Brazil's money-laundering law?

Law 9.613 of March 3, 1998 puts its duties on the people and companies listed in Article 9. The list covers financial intermediaries, insurers, factoring companies and real estate promoters, among others. Item XIX, added by Law 14.478 of December 21, 2022, adds the VASP (virtual asset service provider, the FATF term; see what a VASP is).

Being on the list brings the duties in Articles 10 and 11: identify clients, keep records, run internal controls, register with the sector regulator or with COAF, and report. The trigger is the activity, not the currency. A company that pays for goods and services in stablecoins is not on the list because of that payment. It is on the list if its own business falls under Article 9, for example if it factors receivables.

COAF (Conselho de Controle de Atividades Financeiras) is Brazil's financial intelligence unit. It receives communications through its system, Siscoaf, and its site gives 2025 figures of 7.6 million communications received and 20,548 intelligence reports. The same page warns that COAF does not block, release or hold money.

Lumx's Brazilian entity filed its SPSAV (Sociedade Prestadora de Serviços de Ativos Virtuais, the company type that holds a virtual asset authorization) request on October 27, 2026, operates under the transition regime of Article 88 of Resolution BCB 520 and reports customer operations as the provider.

Who reports what when a company pays with stablecoins in Brazil?

Five reports touch a stablecoin payment in Brazil, each with its own filer and clock. Only the first three go to COAF.

Reports that can touch a stablecoin payment in Brazil, read from the norms on November 21, 2026.

Report

Goes to

Filed by

Trigger and clock

Suspicious operation or situation

COAF

The institution that detected it

Analysis in a dossier within 45 days of selecting the operation; communication by the next business day after the decision (Circular 3.978, Articles 43 and 48)

Transfer to or from a self-custodied wallet

COAF

Institutions authorized by the Central Bank of Brazil (BCB), VASPs as applicable

US$10,000 or more per operation; next business day after the operation, and the first business day of January 2027 for operations from October 1 to December 31, 2026 (Article 49, item V and §2)

Annual no-occurrence declaration

COAF

An institution that filed no communication in the calendar year

Within 10 business days after the year ends (Article 54)

Virtual asset service report (Annex II-A)

BCB

Institutions authorized in the foreign exchange market, and the VASP companies covered by Article 29, §5 of Resolution BCB 277

By the 5th of the month after the operation (Resolution BCB 277, Article 82-A, inserted by Resolution BCB 521)

Crypto-asset declaration

Receita Federal

The crypto-asset service provider; a Brazilian resident only for operations outside a Brazilian provider (IN RFB 2.291/2025, Article 5)

Monthly by the last business day of the next month, yearly by the last business day of January (Article 12). It replaced IN RFB 1.888/2019 on July 1, 2026; see DeCripto in Brazil

Law 9.613, Article 9, item XIX, binds the VASP directly, and Article 11, item II, sets 24 hours for communications to COAF. Article 87 of Resolution BCB 520 applies the Central Bank's rules for authorized institutions to a VASP "as applicable", and the table gives those clocks.

Annex II-A has four report types: international payments with virtual assets, transfers to the issuer of an international card, self-custody transfers with no international payment, and the monthly total of fiat-referenced assets bought, sold or swapped. The international payment report carries the purpose of the operation and the link between the client and the payer or recipient abroad, and Lumx's purpose code and holder relationship fields are where that data enters. The self-custody item has its own post: Brazil's self-custody wallet reporting rule.

At Lumx, reporting customer operations to the Receita Federal and to COAF is Lumx's job as the provider. It reports to Receita Federal under IN RFB 2.291/2025 and files the Annex II-A report to the Central Bank. BCB Circular 3.978/2020 applies to Lumx. The custodian of the wallets is BitGo, and Lumx is the intermediary. A client that is itself a VASP in Brazil reports its own operations.

What turns a stablecoin payment into a COAF communication

Article 39 of Circular 3.978 tells institutions what monitoring must look for. Six indicators matter most for a company paying through a provider:

  • operations that do not fit the client's income or revenue;

  • operations with politically exposed persons;

  • clients whose ultimate owner cannot be identified;

  • flows to or from countries the FATF flags for strategic deficiencies;

  • client data that cannot be kept current;

  • a pattern or form that looks designed to evade the identification and monitoring procedures.

The business-payout version is in money laundering red flags.

Monitoring may take up to 45 days from the operation, and analysis another 45 from selection, with a dossier whether or not a communication follows. Article 44 bars institutions from hiring third parties to run the analysis or from running it abroad, though auxiliary services stay allowed.

At Lumx, the fiat legs are monitored by an in-house stack that combines AI agents and external bureaus, on top of Chainalysis KYT for blockchain activity. A flagged on-ramp or off-ramp is put on hold for review. Compliance usually asks for the relationship between sender and receiver, the purpose and the expected outcome, and if the customer does not answer within 24 hours the transaction may be refunded to the sender.

What stays with the paying company when the provider files

A provider's filing does not clear the company of three things.

First, the data. A provider reports only what it was told, and the Annex II-A report asks for the purpose and the relationship to the counterparty abroad. A vague purpose or the wrong relationship makes a routine payout look inconsistent, which is how it turns into a hold. A provider may reuse part of a client's KYC (know your customer, the verification of an individual), as relying on client KYC explains.

Second, silence. The company will not be told. Article 11 of the law requires communications to be made without telling anyone, including the person the information is about, and Circular 3.978, Article 50, repeats it. A hold is the only sign it sees.

Third, its own duties, if it has any. A company on the Article 9 list reports for itself; the provider's filing covers only the provider's side.

I would put three questions to a provider in writing before the first Brazilian payment: which reports it files, under which norms, and which fields from me it needs on each payment. I would not ask for copies of what it filed. Article 11 forbids telling anyone about a communication, so a provider that hands one over has a problem and a provider that refuses is doing its job. I recommend keeping the answers in the vendor file next to the provider's licence status and rereading them when that status changes, because who files each report follows the provider's status, not the contract.

At Lumx, the data goes in at two points. Every on-ramp and off-ramp takes one of nine purpose codes, which Lumx uses for AML monitoring and regulatory reporting, and every destination carries the holder's tax ID and its relationship to the customer, such as SUPPLIER or EMPLOYEE. A mismatch between the two can trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears).

Penalties, secrecy and record keeping under Law 9.613

Article 12 lists the sanctions for an obliged entity and its administrators that fail the duties in Articles 10 and 11, separately or together. Good-faith communications carry no civil or administrative liability (Article 11, §2):

  • a warning;

  • a variable fine not above twice the value of the operation, twice the profit made or expected from it, or R$20,000,000;

  • temporary disqualification of administrators for up to ten years;

  • revocation or suspension of the authorization to operate.

Records have their own clock. The law sets five years as the minimum, from the closing of the account or the conclusion of the transaction (Article 10, §2). The circular sets ten years for the institutions it covers, from the first day of the year after the relationship ends or after the operation, and the dossier of each analysis is kept for ten years too (Article 67).

When COAF reporting is the wrong thing to worry about

Three cases where a company has no COAF filing of its own:

  • The company pays a Brazilian supplier against an invoice and is not on the Article 9 list. The provider reports what it must, and the company's job is accurate data.

  • The company fears COAF will freeze its funds. COAF says on its own site that it does not block, release or hold money. A hold comes from the provider or a bank, and the way out is the RFI, where Lumx's compliance reviews the answer and decides whether to release the transaction.

  • The company is a VASP or another obliged entity itself. The provider's reporting is the wrong thing to lean on, and the company needs its own Siscoaf habilitation (Circular 3.978, Article 55) and procedures.

Who owns which duty in a stablecoin API is in who owns stablecoin compliance, and the program a fintech runs is in stablecoin AML compliance for fintechs.

What a Brazilian payment 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.

Take a company that pays a Brazilian supplier from a stablecoin balance. It is a customer approved through KYB (know your business, the verification of a company and its owners), and wallets are enabled only after approval. The supplier is registered as a destination with a Pix (Brazil's instant payment system, run by the Central Bank) key, the holder's CPF (the Brazilian individual taxpayer ID) or CNPJ (the Brazilian company taxpayer ID) and the relationship SUPPLIER. Lumx verifies each holder, and an off-ramp to a destination that is not approved fails. The payout is then an off-ramp from the customer's wallet, with a purpose such as TRADE_TRANSACTIONS, and the customer appears to the supplier as the payer.

For a transfer to an outside wallet, Lumx asks Brazilian customers about self-custody, and the transfer is identified and reported to COAF. If a payout is held, the customer answers the RFI on its usual channel with the relationship, the purpose and supporting context such as an invoice. Lumx handles the reporting as the provider, and the company keeps its data accurate.

The customer's country has to be on the supported countries list, and rails are on the coverage page. See also Lumx's global payments page.

Methodology and sources

Everything here was read on November 21, 2026. Law 9.613/1998 was read on planalto.gov.br in its current wording, with the changes of Law 12.683/2012 and Law 14.478/2022, citing the new wording.

Circular BCB 3.978 was read in the consolidated PDF that includes Resolution BCB 591, because the norms API still serves only metadata. Resolution BCB 591 of September 30, 2026, Resolution BCB 520 (Articles 87 and 88) and Resolution BCB 521 (Article 82-A and Annex II-A), both of November 10, 2025, were read in full.

IN RFB 2.291 of November 14, 2025 was read in the reproduction of its Diário Oficial text (Articles 5, 12 and 19), because Receita's norm portal answers only with a script page. That IN RFB 1.888 applied until June 30, 2026 comes from Receita's notice on the norm, and the crypto-assets page, updated on August 27, 2026, lists both numbers. The COAF figures and warning are on the COAF home page.

Lumx behavior comes from the docs on request for information, purpose codes, destinations, paying out via Pix, transactions and wallets. That Lumx reports customer operations to the Receita Federal and to COAF, that it reports under IN RFB 2.291/2025 and that Circular 3.978 applies to it are Lumx's own statements, as of November 21, 2026.

Verified on November 21, 2026. Operational context, not legal, tax, or investment advice. Law 9.613/1998 checked against planalto.gov.br on November 21, 2026. Circular BCB 3.978/2020 checked against bcb.gov.br on November 21, 2026. Resolution BCB 591/2026 checked against bcb.gov.br on November 21, 2026. Resolution BCB 520/2025 checked against bcb.gov.br on November 21, 2026. Resolution BCB 521/2025 checked against bcb.gov.br on November 21, 2026.

Cover photo: Ramon Buçard on Unsplash.

  • What is COAF reporting for companies paying with stablecoins in Brazil?

    It is the duty of obliged entities under Law 9.613/1998 to report suspicious operations, and a few specific high-value ones, to COAF, the financial intelligence unit. A company that only pays suppliers does not file; the virtual asset provider that processes the payment does. At Lumx, reporting customer operations is Lumx's job as the provider.

  • Does my company have to report to COAF if it pays suppliers in stablecoins?

    Not because of the payment. The duty depends on the company's own activity: it applies if the company is on the Article 9 list, for example as a financial intermediary, a factoring company or a VASP. Any company still owes its provider accurate data on each payment. On Lumx, that is the purpose code of the transaction and the holder's tax ID and relationship on each destination.

  • When does a COAF communication have to be filed?

    The law binds a VASP to 24 hours (Article 11, item II). The circular, applied to a VASP "as applicable" under Article 87 of Resolution BCB 520, allows up to 45 days of analysis for a suspicious operation and requires the filing by the next business day after the decision. A self-custody transfer of US$10,000 or more is filed the next business day, or on the first business day of January 2027 for operations from October 1 to December 31, 2026. A Lumx payout under review is held, and the customer has 24 hours to answer the RFI before it may be refunded.

  • Can a provider tell me that it filed a COAF report about my payment?

    No. Article 11 of Law 9.613 requires the communication to be made without telling anyone, including the person it concerns, and Circular 3.978, Article 50, repeats it. A provider can say that a payment is on hold and what it needs to release it, and Lumx does that through an RFI on the customer's usual channel.

  • What happens if a provider or an obliged company does not report?

    Article 12 of the law allows a warning, a fine, temporary disqualification of administrators for up to ten years, and revocation or suspension of the authorization, separately or together. The fine cannot exceed twice the value of the operation, twice the profit from it or R$20,000,000. At Lumx, the customer's side is accurate data and a prompt answer to an RFI, and the filing is Lumx's.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

coaf-reporting-stablecoin-payments-brazil

A

coaf-reporting-stablecoin-payments-brazil

COAF reporting for companies paying with stablecoins in Brazil

Copy link

Copied!

coaf-reporting-stablecoin-payments-brazil

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Regulation

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.