Regulation

DeCripto in Brazil: who files for stablecoin payments

DeCripto is Receita's crypto-asset declaration under IN RFB 2.291/2025: who files, the R$35,000 threshold, the dates and what a platform needs from a provider.

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: DeCripto in Brazil: who files for stablecoin payments
Cover image for Lumx blog article: DeCripto in Brazil: who files for stablecoin payments

DeCripto is the crypto-asset declaration that Receita Federal created with IN RFB 2.291 of November 14, 2025, replacing IN RFB 1.888/2019. The crypto-asset service provider files it every month and every year, for each customer operation. A user files only for operations outside a Brazilian provider, and only above R$35,000 in a month.

DeCripto replaced IN RFB 1.888, and the dates depend on the article

Providers send the DeCripto file through the Coleta Nacional system in the e-CAC (Receita's online service portal). Receita's notice on the norm says it adopts the OECD's Crypto-Asset Reporting Framework (CARF) for automatic exchange of information between tax administrations, and that it does not deal with taxation. Article 16 of the norm says the same: tax on the operations follows the specific legislation.

Summaries give two start dates, July 2026 and January 2026. Both are right, because article 19 sets a date per article.

When each part of IN RFB 2.291/2025 takes effect, per article 19, as read on November 16, 2026.

Part of the norm

Articles

Takes effect

First filing

Definitions, who files, operations covered, due diligence rules, filing system, penalties

The remaining articles and both annexes

November 17, 2025 (publication in the Diário Oficial da União)

Depends on the report below

Yearly aggregated report for CARF

Article 8

January 1, 2026

2026 operations, due January 29, 2027

Operation-by-operation monthly report, year-end balances, the user's own report, revocation of IN RFB 1.888 and IN RFB 1.899

Articles 7, 9 and 18

July 1, 2026

July 2026 operations, due August 31, 2026

January belongs to article 8. July belongs to the monthly reporting and to the end of IN RFB 1.888, which Receita's notice says applied until June 30, 2026. Article 12 sets the deadlines: the last business day of the next month for monthly data, and of January for yearly data. The next monthly filing, for October operations, is due November 30, 2026.

Who files: the provider, the platform or the customer?

The norm names two kinds of filer, and a payments platform can end up on either side.

Who files DeCripto in four situations, per article 5 of IN RFB 2.291/2025.

Situation

Who files

Basis

A customer operates through a provider that is tax resident in Brazil, formed or managed there, has a place of business there, or serves Brazil

The provider, for every operation, whatever the amount

Article 5, first item

A Brazilian resident operates through a provider located abroad

The user, when the month's operations exceed R$35,000, and the provider if it serves Brazil

Article 5, second item (a), §3, and first item (e)

A Brazilian resident uses a platform with no operator in control (the norm's plataforma descentralizada), or operates with no provider at all

The user, above R$35,000 in the month, alone or added up

Article 5, second item (b) and (c), §3

A platform sells exchange, transfer or custody to its own clients

The platform itself, if it meets the definition of provider

First annex, items 17 and 18

The provider definition is functional. The first annex calls a provider any person acting in business who performs crypto-asset operations for or on behalf of clients, as counterparty, as intermediary or by offering a trading platform. The services listed are exchange between a crypto-asset and a currency or another crypto-asset, transfer, custody or administration, and participation in offerings. A fintech that embeds stablecoin payments through a partner API should read that definition against what it does. That is a question for counsel. For the regulatory side of being a VASP (virtual asset service provider, the FATF term), see what a VASP is.

A stablecoin is inside the scope by default. The first annex defines a declarable crypto-asset as any crypto-asset usable for payment or investment, except a central bank digital currency and what it calls a specific electronic money product. A fiat-referenced token that is a claim on its issuer, redeemable at par at any time, could fall in that second exclusion. Which side a given stablecoin falls on is the provider's call, so ask which classification it applied.

Thresholds, deadlines and penalties

There is one money threshold in the norm. It belongs to the user and not to the provider: operations through a foreign provider, an operator-less platform or no provider count when the month's total is above R$35,000, up from R$30,000 under IN RFB 1.888. A provider reports every operation individually with no floor.

What a provider sends depends on the report:

  • Monthly (article 7, first item): date, type of operation, identity of the users, the crypto-asset, quantity, value in reais without fees, and the fees apart.

  • Yearly (article 7, second item): each user's balance in reais and in each crypto-asset on December 31.

  • Yearly for CARF (article 8): the reportable persons identified by the due diligence, aggregated by type of operation with the number of transactions, the total value and the total quantity.

Foreign-currency values go to US dollars and then to reais at the Central Bank's closing Ptax rate for the operation date (article 11). In a payments flow, a purchase or sale is the BRL to USDC on-ramp and the USDC to BRL off-ramp. An exchange between two crypto-assets is a USDC to USDT swap. Transfers in and out of a customer's account have their own types, including one for a transfer to a wallet not linked to a provider.

Penalties are in article 13, and they bite on the filer. Late filing costs R$1,500 per month or fraction for most companies, R$500 for start-ups, exempt or immune entities, Simples Nacional companies and those on presumed profit, and R$100 for individuals. The fine halves if the filing comes before any audit step. An inaccurate, incomplete or missing item costs 3% of the operation's value for a company, never below R$100, and 1.5% for an individual.

What a platform needs from its provider

The provider files, but it files what the platform's onboarding gave it. These are the points to put to a provider.

What to ask a stablecoin provider about DeCripto, and why.

Ask

Why

Under which status does it file in Brazil, and under which instruments?

Article 5 decides who files. A provider that does not say has not answered

Is each of your end users its own customer, with its own KYC (know your customer) or KYB (know your business) check?

The monthly report identifies the users of each operation (article 7, first item (c)). Users the provider cannot see cannot be identified

Which tax data does it collect, and when?

The second annex requires a self-declaration of tax residence at onboarding. Individuals give name, address, residence, CPF (the Brazilian individual taxpayer ID) and, if not Brazilian residents, a foreign tax number and birth date. Companies give legal name, address, residence, CNPJ (the Brazilian company taxpayer ID), a foreign tax number and, unless an active entity, their controlling persons

How does it map your flows to the article 6 operation types?

A transfer to a wallet outside a provider, a transfer for goods or services and an unknown origin are reported differently

What does it report on fees and on value?

Article 7 splits the value without fees from the fees, and article 10 sets how fair value is found

Can it export the transaction history and correct a filing?

Article 15 allows a corrected declaration, and the second annex keeps documents for at least five years after the reporting period

Who is responsible if a third party does the due diligence?

Second annex, item 41: the provider may use a third party, but the duty stays with the provider

I would treat DeCripto as a due diligence question for the provider and not as a tax question for the accountant. The accountant sees the declaration after it is filed. The data it needs, who the user behind each wallet is and where that person is tax resident, is collected at signup by whoever builds the flow. If the flow does not carry that data, no provider can report it correctly later.

A foreign provider with Brazilian customers

For a platform that uses a provider outside Brazil, article 5, paragraph 1, lists what counts as serving Brazil. Any one of four is enough: the provider uses a .br domain, it has a commercial agreement with a Brazilian entity or a related party that lets it receive funds locally from Brazilian residents, it names a Brazilian entity to intermediate withdrawals or offers another payment method such as Pix (Brazil's instant payment system, run by the Central Bank), or it advertises clearly to Brazilian residents. Receita's notice says this extends the duty to providers abroad, under Law 14.754/2023.

Two things follow. A provider that meets one of the four tests is a filer even with no office in Brazil. And a Brazilian customer that operates only through a provider abroad can still have its own duty above R$35,000 a month, because the second item (a) names operations through a provider residing abroad.

Article 8 paragraph 1 relieves a provider from the yearly CARF report where it already filed the same information in a partner jurisdiction. Receita publishes the list of partner jurisdictions. The relief covers the article 8 report, and the text does not extend it to the monthly report.

When DeCripto is the wrong frame

DeCripto is an information duty. It says nothing about what is taxable. For IOF on a BRL to USDC conversion, or the invoice behind a payment, read stablecoin tax in Brazil. For the Central Bank's reporting of transfers to a self-custodied wallet, read the self-custody reporting rule. For whether a use case is allowed at all, see the restricted use cases post. The wider rules are in Brazil's stablecoin rules for 2026.

What this 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 reporting of customer operations is Lumx's, as the VASP that filed its request for Central Bank authorization and operates under the transition regime described in Brazil's virtual asset license. Lumx reports under IN RFB 1.888/2019, IN RFB 2.291/2025 (DeCripto) and the Annex II-A report to the Central Bank. A platform that is itself a VASP in Brazil reports its own operations.

What the platform controls is the onboarding. In the Lumx docs, each end user, individual or business, is its own customer with its own verification: individuals give a tax ID, date of birth and address, businesses give a tax ID, incorporation date and address, documents from the representative and every owner above 25%, and the taxId is the local identifier of the country of residence. The nested payments rule says every transaction ties to an onboarded customer acting for itself, and a marketplace onboards each seller as a customer. That is the visibility a provider needs to identify the user of each operation. Each approved customer gets a custodial wallet on each supported network, and on-ramps, off-ramps and transfers report status by webhook, so the platform keeps its own record of every movement. The operator map shows which entity runs each leg, and global payments covers the product.

In Brazil, an external transfer is identified and reported to the COAF (Brazil's financial intelligence unit), Lumx asks about self-custody on an external transfer, and when a transaction needs a hold the customer receives an RFI (request for information, a compliance hold that asks for a document before a transaction clears). Relying on someone else's identity checks does not move the reporting, as covered in relying on client KYC in Brazil.

Methodology and sources

The full text of IN RFB 2.291/2025, articles 1 to 19 and both annexes, was read on November 16, 2026 from the reproduction of the Diário Oficial text on normaslegais.com.br. Receita's norm portal answers only with a script page, so the dates and article numbers were checked against three Receita pages read the same day: the notice on the norm (published November 17, 2025, updated October 28, 2026), the crypto-assets page (updated August 27, 2026) and the layout manual, version 1.01, approved by ADE Copes 02/2025.

Not read on the official portal: any act that amends article 19 or the penalties. Receita's DeCripto acts page lists two acts behind the same script-only portal, and a search for a postponement or amendment found none. Lumx product statements come from the Lumx docs pages on customers, wallets, transactions, identity verification and nested payments, read on November 16, 2026.

Verified on November 16, 2026. Operational context, not legal, tax, or investment advice. IN RFB 2.291/2025 checked against Receita Federal on November 16, 2026.

Cover photo: Katie Moum on Unsplash.

  • What is DeCripto in Brazil?

    DeCripto is the Declaração de Criptoativos, the report Receita Federal requires under IN RFB 2.291 of November 14, 2025, in place of IN RFB 1.888/2019. Providers file it monthly and yearly, and some users file for their own operations. It sets no tax. On Lumx, the reporting of customer operations is Lumx's, under IN RFB 1.888/2019, IN RFB 2.291/2025 and the Annex II-A report to the Central Bank.

  • Does a company that pays through a stablecoin provider have to file DeCripto?

    Usually the provider files, not the company, when the provider is a Brazilian crypto-asset service provider. The company files only for operations outside a provider or through a provider abroad, and only when the month's total is above R$35,000. A platform that sells exchange, transfer or custody to its own clients may itself meet the provider definition, which is a question for counsel. On Lumx, a platform that is itself a VASP in Brazil reports its own operations.

  • When did DeCripto start, and what happened to IN RFB 1.888?

    Under article 19, the yearly CARF report in article 8 took effect on January 1, 2026, and the monthly report, the user's report and the revocation of IN RFB 1.888 took effect on July 1, 2026. The first monthly filing was due August 31, 2026, and the first yearly one is due January 29, 2027. On Lumx, Lumx reports customer operations under IN RFB 1.888/2019, IN RFB 2.291/2025 (DeCripto) and the Annex II-A report to the Central Bank.

  • What must a foreign stablecoin provider with Brazilian customers do?

    It files if it serves Brazil by any of four tests in article 5: a .br domain, a local funding agreement, a Brazilian withdrawal intermediary or a payment method like Pix, or advertising aimed at Brazilian residents. It may be relieved of the yearly CARF report if it filed it in a partner jurisdiction. A Brazilian customer of that provider can still have its own duty above R$35,000 a month. On Lumx, the Brazilian entity handles only reais and stablecoin, and Lumx reports its customers' operations itself.

  • What happens if DeCripto is filed late or wrong?

    Article 13 sets R$1,500 per month or fraction for a late company filing, with lower amounts for some company types and R$100 for individuals, and 3% of the operation's value for an inaccurate or missing item. The fine halves if the filing comes before any audit step. On Lumx, the filing of customer operations is Lumx's, and the customer data it files comes from each customer's verification, so accurate onboarding data is the platform's part.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

decripto-brazil-stablecoin-payment-companies

A

decripto-brazil-stablecoin-payment-companies

DeCripto in Brazil: who files for stablecoin payments

Copy link

Copied!

decripto-brazil-stablecoin-payment-companies

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.