Three ways to pay suppliers in Brazil and Mexico from dollars in a US bank account: an international wire, a fintech transfer, or USD to Pix or SPEI.
A US company can pay suppliers in Brazil and Mexico from a US bank account in three ways: an international wire, a fintech transfer, or a stablecoin route that turns dollars into reais over Pix or pesos over SPEI. With BlindPay, USD arrives by ACH or wire, converts to USDC, and pays out over Pix or SPEI in minutes, with every fee shown in the quote.
This guide starts where most finance teams actually start: dollars in a US business checking account and an invoice in reais or pesos. If you already hold USDC, how to send USDC to a bank account in Brazil is the shorter path.
Key takeaways
There are three: send an international wire from your US bank, use a fintech that converts and pays out locally, or convert dollars to a stablecoin and pay out over Pix or SPEI. Each moves the money between countries differently.
For context on price levels, the World Bank's Remittance Prices Worldwide, Issue 54 put the average cost of sending $200 from the US at 5.04% in Q3 2025, and banks were the costliest type of provider at 14.99%. Those are consumer remittance figures, not B2B invoices, but the cost layers are the same ones a supplier payment runs through. What cross-border payments cost in 2026 has the corridor detail.
The stablecoin route is the fastest to the supplier once dollars are in, and the only one of the three that shows the market rate next to your rate in every quote. A wire still wins when the supplier needs dollars.
| Route | How money crosses the border | Supplier receives | Time once funded | Cost visibility | Pre-funding |
|---|---|---|---|---|---|
| BlindPay: USD in, Pix or SPEI out | USD to USDC, on-chain settlement, local payout | BRL over Pix or MXN over SPEI | Minutes, 24/7 | Market rate, rate after fees, flat fee, and amount received in each quote | None; each payout is funded when you send it |
| International wire from a US bank | Correspondent banking chain | BRL, MXN, or USD, depending on who converts | Up to 5 business days | Outgoing fee known; intermediary deductions and FX margin often not | None for you; correspondents hold balances |
| Fintech transfer | Provider pays from its own local balance | BRL or MXN, usually over a local rail | Often same day | Depends on the provider; ask for the rate before fees | None for you; the provider pre-funds |
BlindPay also sends SWIFT (POBO/COBO), with UETR tracking and MT103 confirmations, for suppliers who want dollars. POBO vs COBO explained covers how those payments are made on your behalf.
It runs in two legs: dollars in and reais or pesos out, with USDC in a wallet in between. Each leg has its own quote.
Leg 1: dollars in. You have two ways to send USD from your US bank, both covered in the payins docs:
memo_code to put on the transfer. Good for occasional payments. ACH and wire payins can take up to 5 business days to arrive, and payins without a virtual account are capped at $500,000 per transaction.A third option, ach_pull, pulls the dollars from a bank account you connect through Plaid, with a flat $1.00 fee per pull.
Leg 2: reais or pesos out. From the wallet, you create a payout quote against the supplier's bank account and execute it. Per the payment methods docs, Pix, PIX Safe, and SPEI settle in minutes. TED, Brazil's wire-style rail, takes about 1 business day.
Both instant rails run around the clock. The Banco Central do Brasil describes Pix as available 24 hours a day, every day, with funds available to the recipient in a few seconds. Banco de México runs SPEI on a 24/7 schedule and has operated it since August 13, 2004. Instant payment systems by country compares them with the US and European rails.
The wallet in the middle is either an external wallet your company controls, which keeps the payout non-custodial, or a BlindPay managed wallet (beta), where BlindPay custodies the balance and you skip on-chain signing (payout with managed wallet).
For Brazil, a Pix key or full bank routing. For Mexico, an 18-digit CLABE and the beneficiary's name. Get them before the invoice is due, not on the day.
| Country | Rail | Details to collect |
|---|---|---|
| Brazil | Pix | Pix key: CPF, CNPJ, phone, email, or random key |
| Brazil | PIX Safe | Beneficiary name, CPF or CNPJ, bank ISPB code, branch, account number with check digit, account type |
| Brazil | TED | Same as PIX Safe, with the bank's COMPE code instead of ISPB |
| Mexico | SPEI | 18-digit CLABE and beneficiary name |
Field-level rules are in the bank accounts docs. Pix keys, CPF, and CLABE explained covers what each identifier is and how to validate it.
When you add the supplier, set recipient_relationship to vendor_or_supplier. It records why you're paying this account, and it tells BlindPay the account belongs to a third party rather than your own company.
An invoice, at minimum, kept in your own records and ready to attach. What the rail requires depends on the rail.
on_hold after creation until the required compliance documents are submitted and approved. Payments to your own account don't need them.One practical gap: the supplier's statement for a Pix or SPEI payout shows BlindPay's name as the sender, per the payout descriptor docs. Send remittance advice (invoice number, amount, date) by email or from your accounts payable tool so the supplier can match it.
The quote does the math, so the job is to read it. The numbers below are made up to show the arithmetic. They are not a BlindPay rate.
Assumptions:
currency_type: "receiver" (the amount is in reais) and cover_fees: true (fees are added on top, so the supplier gets the full amount).commercial_quotation) of 5.400 BRL per USDC and a rate after BlindPay's fee (blindpay_quotation) of 5.373.The math:
flat_fee the quote shows, and you have the all-in cost of the payout leg.The payin leg (USD to USDC) has its own quote with its own fees, so price both legs. How to calculate FX spread runs the same check against any provider's quote, including a bank wire, so you can compare like for like.
Your company is checked once at onboarding, and each payment is screened as it runs. Both sides of the corridor have their own rules too.
This is for information only and is not legal advice. Rules differ by country and by the type of supplier.
Six steps, and only the first one is slow.
recipient_relationship set to vendor_or_supplier.completed, then email the supplier the invoice reference.Paying the same suppliers every month? Many teams keep a USDC balance sized to a week or two of payables. Then step 2 happens in the background, and each supplier payment is just steps 5 and 6.
When the supplier invoices in dollars, holds a dollar account, or banks in a country without a local rail you can reach. A wire is also simpler for a one-off payment where speed doesn't matter and your bank already knows the supplier.
For Brazil and Mexico specifically, the local rails cover almost every business account, so the wire is the exception. USDC to BRL routes and USDC to MXN routes compare the providers and rules on each corridor, and the hub on real-time cross-border settlement explains why the leg between countries sets the speed.
Pick one supplier in Brazil or Mexico and price their next invoice both ways: your bank's wire quote against a BlindPay payout quote. Start with the payout quickstart on a free development instance.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.
A 10-point checklist and a side-by-side of BlindPay, Wise Platform, Airwallex, Thunes, Bridge, and Circle for real-time, low-fee cross-border settlement.