A company in Brazil or Mexico pays a US supplier by funding USDC over Pix or SPEI, then paying out over ACH, wire, or RTP. Steps, rules, and timing.
A Brazilian or Mexican company pays a US supplier with stablecoins in two moves. It funds USDC with a local transfer, Pix in Brazil or SPEI in Mexico, then pays out that USDC to the supplier's US bank account over ACH, wire, or RTP. The supplier sees a normal domestic dollar transfer. The stablecoin only carries the value across the border.
That's the stablecoin sandwich run north instead of south. Most guides cover the opposite direction, a US company paying Latin America, which is in paying suppliers in Brazil and Mexico from a US bank account. The reverse has its own rules.
Key takeaways
Because a traditional FX remittance from Brazil or Mexico goes through a bank's FX desk, a correspondent, and a US receiving bank, with the spread set inside the bank's rate. Wires that cross several banks also lose fees along the way, which hidden fees in international wires breaks down by OUR, SHA, and BEN.
The Federal Reserve's FEDS Note of March 30, 2026 names the costs of that chain: each intermediary adds processing time, the payment's status is hard to see, and compliance checks repeat at several points. A stablecoin leg replaces the correspondent hop with an on-chain transfer, while the domestic rails at each end stay the same.
The common buyers are importers paying US manufacturers, software companies paying US vendors and cloud bills by bank transfer, and agencies paying US contractors.
Six steps, two quotes.
| Step | Rail | What the company sees | Typical time |
|---|---|---|---|
| Payin, Brazil | Pix | A Pix code to pay | Minutes |
| Payin, Mexico | SPEI | A CLABE to transfer to | Minutes |
| Payout, US | RTP | Supplier's routing and account number | Instant |
| Payout, US | Domestic wire | Same details | About 1 business day |
| Payout, US | ACH | Same details | About 1 to 2 business days |
Timing follows BlindPay's payins docs and payment methods. A compliance review can add time on either side.
Brazil brought this flow inside its FX framework. The Banco Central do Brasil published Resolutions 519, 520, and 521 on November 10, 2025, and they took effect on February 2, 2026. Resolution BCB 521 brings international payments and transfers with virtual assets inside the foreign exchange rules. A dollar stablecoin payment out of Brazil is treated like an FX operation, with reporting.
Three practical consequences for the paying company:
Taxes on payments abroad, such as withholding on imported services, depend on what's being paid for, not on the rail. Ask your Brazilian tax advisor before the first payment, not after.
Lighter on stablecoins specifically, strict on AML. Mexico has no stablecoin-specific law. Banxico's Circular 4/2019 lets banks and fintech institutions use virtual assets only in internal operations, with prior approval. So the Mexican company's bank sends pesos over SPEI, and the conversion happens at a provider.
Outside the banking system, exchanging virtual assets as a business is a "vulnerable activity" under Mexico's federal anti-money laundering law, with customer identification and threshold reporting. Are blockchain payments legal covers both countries side by side.
The same details a US domestic payment needs. For ACH, wire, and RTP: beneficiary name, routing number, account number, account type (checking or savings), and address (bank accounts docs). Business beneficiaries also need a NAICS industry code. RTP needs a routing number that is RTP-eligible; The Clearing House runs the RTP network and the receiving bank has to participate.
Set recipient_relationship to vendor_or_supplier. A document isn't required on ACH, wire, or RTP, but you can attach the invoice to the payout for compliance, which helps on large or unusual amounts. The ACH network is the most widely reachable US rail, so use ACH when you don't know whether the supplier's bank supports RTP.
Illustrative example, with invented rates. A São Paulo importer owes a Texas manufacturer US$18,000.
| Amount | |
|---|---|
| Invoice | US$18,000 |
| Payout quote, receiver side, ACH | Supplier receives US$18,000; company sends 18,040 USDC including fees |
| Payin quote, sender side, Pix | Company pays R$99,800; wallet receives 18,040 USDC |
| Total cost in reais | R$99,800 |
The two quotes are separate prices, taken minutes apart. Run the payout quote first to know how much USDC you need, then fund exactly that with the payin. For large BRL amounts, an OTC payin quote prices through an OTC desk with a 10-second expiry and a US$5,000 minimum, in USDT only (OTC vs standard quotes).
BlindPay runs both legs in one API: Pix and SPEI payins into USDC or USDT, then payouts over ACH, domestic wire, RTP, or SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations. KYB on the paying company runs inside the same integration. Each quote locks the rate and fees for 5 minutes. BlindPay combines a monthly plan with per-transaction fees that vary by rail and network, disclosed in the live quote before execute. If the USDC should sit somewhere other than a wallet the company controls between the two legs, BlindPay-managed wallets (beta) are custodial when you choose that path.
Take one recent US supplier invoice and price it both ways: your bank's FX remittance quote, and a payout quote plus a payin quote on a development instance, following the payin quotes docs. Compare the reais each route costs for the same dollars delivered.
Always cheaper? No intermediaries? Recipient needs a wallet? 10 common claims about cross-border stablecoin payments, checked against the Fed and the BIS.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
The dates that turned stablecoins from a trading tool into cross-border payment rails: USDC, Pix, MiCA, the GENIUS Act, ISO 20022, and Visa settlement.