Em processo de adequação ao regime das SPSAV, nos termos da Resolução BCB nº 520/2025 (regime de transição do art. 88)

  • Em processo de adequação ao regime das SPSAV, nos termos da Resolução BCB nº 520/2025 (regime de transição do art. 88)

Guides

How to send USDT to a bank account in Brazil

How to turn USDT into reais in a Brazilian bank account: the network choice, why the issuer will not redeem for you, what it costs and where the payout fails.

Caio Barbosa

Fundador & CO-CEO

Forbes Under 30. Uma das principais vozes em Fintech & Crypto no Brasil. Escreve semanalmente sobre stablecoins, pagamentos e o futuro da infraestrutura financeira na América Latina.

Cover image for Lumx blog article: How to send USDT to a bank account in Brazil
Cover image for Lumx blog article: How to send USDT to a bank account in Brazil

Sending USDT to a bank account in Brazil means converting the token into reais through a provider authorized to pay out locally, which credits the recipient over Pix (Brazil's instant payment system, run by the Central Bank). The sequence is the same one the USDC guide walks through step by step. What is not the same is the token.

Three things change when the token is USDT: which network the money arrives on, who you can convert with, and how the liquidity behaves in Latin America. This guide covers those differences, the cost, the failures that are specific to USDT, and when a different token is the better choice. The issuer and its reserves are covered in what USDT is.

The network question comes first

USDT exists on more blockchains than any other stablecoin, and in practice two carry most of the payment flow: Tron, where the token is called TRC20 USDT, and Ethereum, where it is ERC20 USDT. The distinction is not cosmetic. USDT on Tron and USDT on Ethereum are different tokens on different networks, and sending one to an address meant for the other is the most expensive mistake available on this route.

Tron dominates the payment use because fees are cents and confirmation is seconds, which matters when a payroll means two hundred transfers rather than one. Ethereum holds the deeper liquidity for very large tickets, and its fees are trivial against a seven figure transfer. Solana and Polygon sit in between and are accepted by fewer providers for this pair.

Before the first transfer, confirm the exact network your provider credits for USDT to BRL, and send a small test amount. The USDT to BRL page lists the networks we accept for this corridor and the live rate.

Why you cannot go to the issuer

With USDC or USDT, the intuitive idea is to redeem the token with whoever issued it and receive dollars. For a business paying suppliers in Brazil, that route is closed by the issuer's own terms.

Tether's published fee schedule, read on September 22, 2026, sets the minimum acquisition or redemption amount at 100,000 USD, charges the greater of 1,000 USD or 0.1 percent per redemption, 0.1 percent per acquisition, and a non-refundable verification fee of 150 USD in tokens just to be verified. Even if you clear the minimum, the issuer pays dollars to a verified account, which is a wire in the wrong currency to the wrong country, not a Pix credit to a Brazilian supplier.

The practical consequence is that every USDT payout into Brazil runs through somebody's local liquidity. The question to ask a provider is not whether it accepts USDT, but where the reais come from and whether that source holds at the size you send.

What it costs

The network fee on the send leg is cents on Tron and a few dollars on Ethereum during congestion. This is the clearest reason USDT payment flow concentrated on Tron.

The spread between the quote and the mid-market rate is the real price. On USDT to BRL it is often slightly different from USDC to BRL for the same provider on the same day, because the two tokens have different depth against the real and both trade against local order books rather than against a published rate.

The fixed fee per payout, where a provider charges one, dominates small tickets and vanishes on large ones.

A detail worth checking rather than assuming: some providers quote USDT at parity with the dollar and hide the token's own basis inside the spread. Ask for the rate to be shown as USDT to BRL rather than as a dollar rate with a conversion applied, so the whole price is visible in one number.

Where a USDT payout fails differently

Wrong network. The dominant USDT failure. An address is valid on several chains, so a transfer sent as ERC20 to a provider expecting TRC20 can land somewhere nobody is watching. Recovery depends on whether the provider controls that address on that chain.

Provider does not accept USDT for the corridor. Some providers support USDC into Brazil and not USDT, or support USDT only on one network. This is a corridor-level answer, not a company-level one.

Tax ID does not match the account holder. Shared with every Brazilian payout. Pix rejects the credit when the recipient's CPF (the Brazilian individual taxpayer ID) or CNPJ (the Brazilian company taxpayer ID) does not belong to the holder of the destination account.

Compliance hold on a new recipient. Also shared. What matters is whether the provider tells you the payment is held and why.

Thin liquidity at size. Specific to the token and the day. A large USDT ticket can price worse than the same value in USDC in the same corridor, or the other way round, and the only way to know is to ask for both quotes.

I have had the network conversation more times than any other on this corridor, and the one that stayed with me involved a client whose finance team had done everything right except read one line. They sent a large USDT transfer on Ethereum to an address we had issued for Tron, on a Friday afternoon, because the address string looked plausible and the treasury tool they used did not check. We recovered it, and I will not pretend that recovering it was routine. What that taught me was not that clients should be more careful. It was that showing one address and expecting the sender to remember the network is a design failure on our side, which is why the address is now issued per network and refuses to render without one.

When USDT is the wrong token for this payment

When the sender does not already hold it. If the money starts as dollars in a bank account, buying USDT to convert it into reais adds a conversion for no gain, and a direct dollar to real route or a USDC route is usually cleaner.

When the counterparty's compliance policy restricts it. Some regulated counterparties treat the two large stablecoins differently, and in Europe the token's availability on regulated venues has changed with the rules there. Confirm before building the flow.

When the payment is small and the recipient is new. Fixed costs and the first-payout review dominate, and batching is cheaper.

When the recipient wants dollars, not reais. Then the payout leg should not happen at all, and the question becomes where they hold the token rather than how to convert it.

Doing this 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, 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 the global payments API, USDT and USDC are two balances in the same custodial wallet and settle to the same validated Brazilian destinations, so a client that built the USDC flow does not build a second integration for USDT. Deposit addresses are issued per network, which is the direct product of the failure described above. Destinations are validated against their CPF or CNPJ at registration rather than at payment, and each payout returns the Pix end-to-end identifier so the recipient's bank can trace the credit. How the Brazilian leg connects to the rest is in the corridor explainer.

Verified on September 25, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Mike Hindle on Unsplash.

  • Is sending USDT to a Brazilian bank different from sending USDC?

    The bank leg is identical: reais over Pix, validated against the recipient's tax ID. What differs is the network you send on, since USDT payment flow sits mostly on Tron, and the liquidity behind the quote, which can price the two tokens differently on the same day in the same corridor.

  • Can I redeem USDT directly with Tether instead?

    Only above its published minimum of 100,000 USD, with a redemption fee of at least 1,000 USD, and the payout is a dollar wire to your own verified account. That does not pay a Brazilian supplier, which is why business flows go through a provider with local liquidity.

  • Which network is cheapest for USDT payouts to Brazil?

    Tron is the cheapest and fastest in practice, with fees measured in cents. Ethereum costs more per transfer but carries deeper liquidity for very large amounts. Use whichever your provider credits for this pair, and never assume an address works on both.

  • How long does a USDT to BRL payout take?

    Minutes end to end for an established recipient: seconds on Tron, immediate conversion when the provider holds reais, then a Pix credit that settles at any hour including weekends. A first payout to a new recipient can take longer if compliance asks for a document.

Fique por dentro do que a Lumx está desenvolvendo.

Inscreva-se para recebê-los por e-mail.

Compartilhe nas redes sociais:

how-to-send-usdt-to-bank-account-brazil

A

how-to-send-usdt-to-bank-account-brazil

How to send USDT to a bank account in Brazil

Copiar link

Copiado!

how-to-send-usdt-to-bank-account-brazil

FALE COM NOSSO TIME

Pronto para transformar seu negócio com stablecoins?

Descubra como nossa infraestrutura pode integrar stablecoins às suas operações financeiras de forma rápida, segura e eficiente.

Guides

Nesta página

©2026. Todos os direitos reservados.

A LUMX SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA., pessoa jurídica de direito privado, inscrita no CNPJ/MF sob o nº 42.887.120/0001-00, (“Lumx”) atua como prestadora de serviços de ativos virtuais e encontra-se em processo de adequação ao regime regulatório das Sociedades Prestadoras de Serviços de Ativos Virtuais (SPSAV), nos termos da Resolução BCB nº 520/2025, estando atualmente sujeita ao regime de transição previsto em seu art. 88.

A Lumx não é banco, instituição financeira, instituição de pagamento ou custodiante de recursos de clientes. Determinados serviços disponibilizados por meio da Plataforma poderão ser prestados por parceiros terceiros devidamente autorizados e regulados, nos termos da legislação aplicável.

Consulte os Termos de Uso e o Aviso de Privacidade da Lumx para obter mais informações sobre as condições de utilização da Plataforma e o tratamento de seus dados pessoais.