USDC to Pix: how to send stablecoin payouts to Brazil

To send USDC to Pix, a payout platform creates a quote that converts USDC to BRL, executes the payout and delivers reais to the recipient over Pix, which runs 24/7 and settles in seconds. The recipient is identified by a Pix key (CPF, CNPJ, phone, email or random key), or by bank details on PIX Safe or TED.

This guide covers how to choose between the three Brazilian payout rails, as of November 2026, and sits within our stablecoin payouts API guide. For the full path from quote to settlement, start with the canonical USDC to Pix guide. To see the live rate shape, open USDC to BRL.

Key takeaways

• The Central Bank of Brazil launched Pix on 16 November 2020, and it runs 24/7 including weekends and holidays.
• Pix moved R$3.81 trillion across 7.89 billion transactions in September 2026, a monthly record, reported by LatAm Rails on 3 November 2026 from Carta Circular data.
• Pix and PIX Safe payouts are instant at BlindPay, and TED settles the same banking day before the cut-off.
• The BlindPay quote locks rate and fees for 5 minutes by default, and cover_fees decides who pays the fees.
• Regulation changed in 2026, so check the box on rules below before you launch.

Which Brazilian payout rail should you use?

Use Pix when you have a Pix key, PIX Safe when you only have bank details and need instant delivery, and TED when you pay by bank details and can wait for the banking day. Pix covers most payouts.

Third-party recipients are allowed, so set recipient_relationship accurately. In the bank accounts docs, PIX Safe and TED share a field shape, with the bank code keyed by ISPB for PIX Safe and by COMPE for TED. The cut-off rule is in cut-off times. For which details break payouts most often, read Pix key, CPF and CLABE payout details.

What is Pix and why is it the default?

Pix is Brazil's instant payment system, run by the Central Bank of Brazil since 16 November 2020, according to the Banco Central do Brasil. It works every hour of every day, and recipients can be addressed by a key instead of bank coordinates.

That second point simplifies onboarding. You ask the recipient for one value, not for bank, branch and account. Scale is no concern: LatAm Rails reported on 3 November 2026 that Pix moved R$3.81 trillion across 7.89 billion transactions in September 2026, a monthly record, with registered keys above 1 billion, citing Valor and Carta Circular from 20 to 27 October 2026 (LatAm Rails). We have not independently audited those figures.

If you compare Pix with Mexico's rail, read Pix vs SPEI.

What does an illustrative USDC to BRL payout look like?

It takes three steps: add a bank account, create a quote, execute. This walkthrough is illustrative and uses no real rates. Where a number is needed, a placeholder stands in.

1. Add the Pix bank account once. Create a bank account of type pix with the recipient's name and Pix key, or pix_safe or ted with bank details. Reuse it for later payouts.
2. Create the payout quote. Request a quote against that bank account with a network, a token of USDC and a request_amount. Say you quote 100.00 USDC from the sender side, which is 10000 in minor units, with cover_fees set to false.
3. Read the quote fields. The response gives you the numbers to show your user:
   • expires_at: when the quote stops being valid, in epoch milliseconds. The default window is 5 minutes.
   • commercial_quotation: the raw market rate, shown here as <market rate>.
   • blindpay_quotation: the rate net of BlindPay's fee, shown as <net rate>.
   • sender_amount: the USDC the funding source sends, 10000 in this example.
   • receiver_amount: the BRL the recipient's bank account receives, in minor units, roughly sender_amount x <net rate> minus the flat fee.
   • flat_fee, partner_fee_amount and billing_fee_amount: the fee components. partner_fee_amount is nonzero only if you pass a partner fee.
4. Execute before expires_at. Create the payout from the quote, authorize the exact amount and let BlindPay deliver.
5. Follow webhooks. payout.new, payout.update and payout.complete report progress. The statuses are processing, on_hold, completed, failed and refunded.

With cover_fees: false, the fees come out of the reais the recipient receives, which is the common case. With true, the fees are added on top so the recipient gets the full quoted amount, the usual choice for payroll. The fields are documented in payout quotes.

The minimum for Pix, PIX Safe and TED is 10 USD sender amount, and a lower amount returns LIMITS_AMOUNT_OUT_OF_RANGE. Pricing: BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. BlindPay does not publish a static flat rate card; always cite the quote's fee breakdown rather than a fixed bps number. The billing docs add that there is no setup fee and no monthly minimum, and development instances are always free.

How are failures and refunds handled?

If a payout cannot be delivered after the stablecoins are collected, they go back to you. BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

A failed payout is not refunded automatically in every case, so contact support@blindpay.com if one sits outside the normal review. Holds can last up to 30 days, and a timeout fails the payout. In a development instance, use request_amount 66600 to force failed and 77700 to force refunded.

What do Brazil's 2026 rules mean for Pix payouts?

Brazil treats stablecoin payouts as foreign exchange operations since 2 February 2026, so your provider needs authorization and reporting in place. This is a short summary, not legal advice.

• Resolutions 519, 520 and 521 took effect on 2 February 2026.
• Resolution 561 applies from 1 October 2026 to eFX settlement, and individual international transfers using virtual assets remain permitted (CryptoSlate, 19 September 2026).
• Monthly reporting starts on 3 November 2026 (LatAm Rails, 3 November 2026).

The dated timeline and a diligence checklist are in Brazil's stablecoin rules for payout teams. For KYC, KYB, sanctions screening and travel rule checks, BlindPay runs them inside the payout and payin API.

How does a platform integrate this?

Treat Pix as one rail among several and keep the logic in your own system short.

1. Collect the Pix key at recipient onboarding, and fall back to bank details if the recipient has none.
2. Pick the rail in code: pix when you have a key, pix_safe for instant bank-detail payouts, ted otherwise.
3. Quote at the last moment before the user confirms, so the 5-minute window does not lapse.
4. Store the quote, payout and webhook IDs next to your own record.
5. Send an idempotency key on create calls, as described in the idempotency docs.

For a longer walkthrough, see how to send USDC to a bank account in Brazil and USDC to BRL routes in 2026.

Methodology and sources

External: Banco Central do Brasil, Pix (launch on 16 November 2020), LatAm Rails, 3 November 2026 (Pix volume, Resolution 574), CryptoSlate, 19 September 2026 (Resolution 561) and Banco Central do Brasil, Resolution 521. BlindPay docs: payouts, payout quotes, bank accounts, cut-off times and billing.

What to do next

Request a live USDC to BRL quote on your own amount at USDC to BRL, then test the whole flow on a free development instance. Talk to BlindPay when you are ready for production.