Sending USDC to a bank account in Brazil means converting the token into reais and delivering them over Pix (Brazil's instant payment system, run by the Central Bank) or over a TED bank transfer. The blockchain carries the value to a provider; the provider sells it for reais and pays the recipient's account. It is one transaction to the sender and two very different systems underneath, which is why the failures all cluster on the Brazilian side.
This guide covers what you need before the first transfer, the sequence itself, what it costs, how long it takes, why payouts get rejected, and when this is the wrong way to move the money. It assumes you know what USDC is; the mechanics of the conversion leg are in the off-ramp explainer.
What you need before the first transfer
A provider authorized to pay out in Brazil. Paying reais into a Brazilian account is a regulated activity. The framework is Law 14.478 of December 21, 2022, which set the rules for virtual asset service providers, and, where the operation involves converting foreign currency, Law 14.286 of December 29, 2021, whose Article 3 restricts exchange operations to institutions authorized by the Central Bank. An exchange account is not a substitute: it settles into your own account, not the recipient's.
The recipient's full banking data. For Pix, either a Pix key or the bank code, branch, account number and account type. In both cases you also need the holder's CPF (the Brazilian individual taxpayer ID) or CNPJ (the Brazilian company taxpayer ID), because Brazil validates the tax ID against the account holder before the credit lands.
A completed onboarding. A provider will run KYB (know your business, the verification of a company and its owners) on your company before the first payout, and the KYB explainer lists what is usually asked for, which takes days rather than minutes and is worth starting before the money is urgent.
Agreement on which network you will send from. USDC exists on several blockchains and a provider accepts a specific list per corridor. Sending on a network the provider does not credit is the one mistake that is genuinely painful to reverse.
Clarity on who the recipient is. Paying yourself and paying a third party, such as a supplier or a contractor, can carry different requirements. Get that answer per corridor before the first transfer rather than at the first rejection.
The sequence, step by step
1. Request a quote. You ask for the BRL amount that a given USDC amount will produce. The answer should include the rate, the fee and an expiry. The USDC to BRL page shows the live rate and the accepted networks for this pair.
2. Register the recipient. Bank data plus CPF or CNPJ. A good provider validates the tax ID against the account holder at this moment and rejects the registration, not the payment.
3. Send the USDC. Transfer to the deposit address the provider gives you, on the agreed network. Confirmation is seconds to a couple of minutes depending on the chain.
4. The provider converts and runs compliance. Sale into reais at the quoted rate, sanctions and pattern checks on the destination. A first payout to a new recipient is the most likely moment for a request for information, which is a compliance hold asking for a document before the transaction clears.
5. The reais leave over Pix. The recipient's account is credited, normally within minutes of the blockchain confirmation, at any hour including weekends. The provider should return the Pix end-to-end identifier, which is the reference the receiving bank can look up if the recipient claims not to see the money.
Steps 1 to 3 and step 5 are fast by construction. Step 4 is the one that varies, and it varies with how new the recipient is rather than with the amount.
What it costs
Three lines make up the cost, and only two of them are usually quoted.
The network fee on the send leg, which you pay to the blockchain, not the provider. On Ethereum it can be dollars per transfer during congestion; on Polygon, Base or Solana it is cents. For a single large transfer this is noise. For a payroll of two hundred recipients it decides the fee line.
The spread between the quoted rate and the mid-market USD to BRL rate. This is the real price of the service and the number to compare between providers, because a provider advertising a low fee and a wide spread is charging more than one doing the reverse.
The fixed fee per payout, if the provider charges one, which matters at small ticket sizes and disappears at large ones.
For scale, the average cost of sending 200 dollars to Brazil through traditional remittance channels was 5.38 percent in 2025, according to the United Nations Statistics Division series for SDG indicator 10.c.1, for which the World Bank is the custodian agency. Business rates on a stablecoin route are a fraction of that, but the comparison is only useful as an order of magnitude, since those are consumer remittance averages.
How long it takes
Blockchain confirmation runs from a few seconds to a couple of minutes. Conversion is immediate when the provider holds BRL inventory. Pix settles in seconds and operates around the clock, weekends included. TED runs only on business days inside banking hours, so a Friday evening TED is a Monday credit.
The honest end-to-end figure for an established recipient is minutes. For a brand new recipient, add the compliance step, which can be minutes or can be a day if a document is requested. Any provider quoting a fixed time for the first payout to a new recipient is quoting the happy path.
My own worst version of this was a payroll run for a client paying developers in Brazil, where we had onboarded the recipients but the client sent the batch on a network we did not credit for that corridor. The tokens sat in an address nobody was watching over a weekend, the developers did not get paid on the day they expected, and the recovery took us four days of coordination that had nothing to do with technology. Nothing was lost and everyone was eventually paid, which does not change the fact that people I had never met waited four days for money they had already earned. We changed two things after it: the deposit address is now issued per network rather than shown as a single string, and the first transfer on any new corridor is a small test amount, which I now recommend to every client whether or not they think they need it.
Why a payout gets rejected, and what the rejection looks like
Tax ID does not match the account holder. The single most common cause. Pix rejects the credit when the CPF or CNPJ does not belong to the holder of the destination account. The funds come back, the fix is data, and a provider that validates at registration spares you the round trip.
The Pix key points somewhere else. A key can be reassigned to a different account. If the recipient moved banks and took the key, the money follows the key.
Bank-side limits. Brazilian banks set per-transaction and nightly Pix limits per account, and a large payout into a personal account can bounce off a limit the recipient did not know existed.
Compliance hold. New recipient, amount out of pattern, or a recipient category that requires extra review. This is not a rejection, it is a pause, and the thing that matters is whether the provider tells you it is paused and why.
Wrong network on the send leg. Recoverable only if the provider controls that address on that network. Read the accepted list per pair, and send a test amount first.
When this is not the right way to move the money
When both parties are Brazilian and already hold reais. Send Pix directly. Converting into USDC and back adds two conversions and a counterparty for nothing.
When the recipient wants to keep dollars. A contractor who prefers holding USDC does not want an off-ramp, and converting on their behalf destroys the thing they asked for.
When the payment may need to be recalled. The blockchain leg is final and the Pix leg is final on settlement. Recovery means asking the recipient to send it back.
When the amount is very small and the recipient is new. The fixed costs and the first-payout compliance step dominate, and it can be worth batching.
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, a USDC to BRL payout is a transaction from a custodial wallet to a destination that was validated against its CPF or CNPJ when it was registered, so a mismatch is returned at registration time with a reason rather than by the bank hours later. Every stage emits a webhook event: quote accepted, funds received, compliance cleared or held with a reason, payout settled with the Pix end-to-end identifier, or rejected with the bank's own return code. Brazil is one of six countries where we operate the local rail directly, and how it connects to the rest is described in the corridor explainer.
Verified on September 25, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Isis França on Unsplash.
Can I send USDC straight to a Brazilian bank account?
No. Banks hold reais, not tokens, so a provider always sits in the middle to convert and pay out. What varies is whether that provider is authorized in Brazil, whether it validates the recipient before accepting the payment, and whether it pays over Pix or only over TED.
Do I need a Brazilian company to receive the money?
No. The recipient can be an individual with a CPF or a company with a CNPJ. What matters is that the tax ID matches the holder of the destination account, and that the provider is allowed to pay third parties in that corridor.
Which network should I send USDC on?
Send on a network the provider credits for this pair, and prefer a low fee chain such as Polygon or Base when the payout count is high. Ethereum still holds the deepest liquidity for very large tickets, which can outweigh its fees.
Is there a limit on how much I can send?
The blockchain has no limit, but the Brazilian side does. Receiving banks apply per-transaction and nightly Pix ceilings per account, and providers set their own limits per client and per corridor. Large payouts are usually arranged in advance rather than attempted cold.
