One reference table for stablecoin payouts to Brazil, Mexico, Colombia, and Argentina: currency, rail, required bank details, timing, and common failures.
Paying out in Latin America means one rail per country: Pix or TED in Brazil (BRL), SPEI in Mexico (MXN), ACH Colombia (COP), and Transfers in Argentina (ARS). Each rail wants different bank details. Pix, SPEI, and Transfers settle in seconds around the clock, while TED and ACH Colombia take about one business day.
This page puts the four countries in one place. Bookmark it next to your payout code. For a deeper look at each corridor, follow the links in each section.
Key takeaways
Here is the cheat sheet. Timing is BlindPay's documented estimate for payouts as of October 2026, from the bank accounts docs and the payment methods reference.
| Country | Currency | Rail | Recipient identifier | Estimated payout time | Runs on weekends |
|---|---|---|---|---|---|
| Brazil | BRL | Pix | Pix key (CPF, CNPJ, phone, email, or random key) | Instant | Yes |
| Brazil | BRL | Pix with bank routing | CPF or CNPJ, ISPB bank code, branch, account with check digit | Instant | Yes |
| Brazil | BRL | TED | CPF or CNPJ, COMPE bank code, branch, account | About 1 business day | No |
| Mexico | MXN | SPEI | 18-digit CLABE (or debit card or phone with institution code) | Instant | Yes |
| Colombia | COP | ACH Colombia | Name, document type and number, email, bank code, account, account type | About 1 business day | No |
| Argentina | ARS | Transfers | CBU, CVU, or alias | Instant | Yes |
Definition: A local payout rail is a country's domestic bank transfer system, such as Pix in Brazil or SPEI in Mexico. A stablecoin payout converts USDC or USDT into local currency and delivers it over that rail, so the recipient gets an ordinary domestic bank transfer instead of an international wire.
Brazil has two rails for payouts: Pix for instant payments and TED for next-day bank transfers. Pix is the default for almost every payout.
Banco Central do Brasil describes Pix as an instant payment system it created that moves money between accounts in seconds, available 24 hours a day, 7 days a week, and it launched on 16 November 2020 (Banco Central do Brasil). Recipients are found by a Pix key, which is a CPF (individual tax ID), CNPJ (company tax ID), phone number, email, or random key.
You have three ways to address a Brazilian recipient on BlindPay:
12345-6.The full walkthrough is in how to send USDC to a bank account in Brazil. For collecting keys and tax IDs from recipients, see Pix keys, CPF, and CLABE.
Mexico pays out over SPEI, the interbank system run by Banco de México. Payouts are instant and the standard identifier is the 18-digit CLABE.
Banco de México lists SPEI as a real-time settlement system it administers and operates, in service since 13 August 2004, on a 24/7 schedule (Banco de México). SPEI does not close at night or on weekends.
On BlindPay a SPEI bank account needs a display name, the beneficiary name, a protocol, and the CLABE. The protocol also allows a 16-digit debit card or a 10-digit phone number linked to the account, and those two need the receiving institution's code. The CLABE's built-in check digit catches most typos at validation.
How to send USDC to a bank account in Mexico has the step-by-step flow, and Pix vs SPEI compares the two biggest rails in the region.
Colombia payouts go over ACH Colombia and take about one business day. The bank account record asks for more identity data than any other rail in the region.
BlindPay requires these fields for a Colombian payout account:
| Field | What to collect | Rule |
|---|---|---|
| Beneficiary first and last name | As the bank holds them | Separate fields |
| Document type | CC, CE, NIT, PASS, or PEP | NIT is for companies only |
| Document number | Must match the type | CC 3 to 10 digits, CE 6 to 10 digits, NIT 9 digits (10 with the verifier), PASS 3 to 15 letters or digits |
| Beneficiary email | Required | |
| Bank code and account number | The receiving bank and account | Required |
| Account type | Checking or savings | Required |
Validate the document number against its type in your own form before you call the API. It is the field recipients most often get wrong. Corridor costs and routes are compared in USDC to COP in 2026.
Argentina pays out over immediate bank transfers, which credit in seconds. The recipient is identified by a CBU (bank account), a CVU (payment account, such as a digital wallet), or an alias that points to either.
Argentina's central bank says immediate transfers under its Transfers 3.0 framework credit online in a maximum of 15 seconds and run 24/7 (BCRA). On BlindPay, an Argentine bank account needs the beneficiary name, the identifier type (CBU, CVU, or alias), and the identifier itself.
A beneficiary name that does not match the holder of the CBU or CVU is the classic failure, so collect it exactly as the bank holds it. ARS also moves fast against the dollar, which makes quote timing more sensitive than elsewhere. How live quotes handle volatile currencies explains why, and USDC to ARS in 2026 compares routes.
Most failures come from recipient data, not from the rail. A name, tax ID, or document number that does not match the receiving account is the top cause in all four countries.
| Failure point | Where it shows up | How to prevent it |
|---|---|---|
| Name does not match the account holder | All four countries | Collect the legal name exactly as the bank holds it |
| Wrong or inactive Pix key | Brazil | Confirm the key with the recipient before the first payout |
| CLABE typo | Mexico | Validate length and check digit in your form |
| Document type and number mismatch | Colombia | Enforce the length rule per document type |
| Alias points to a different holder | Argentina | Confirm the alias and holder name with the recipient before the first payout |
| Quote expired before execution | All | Quote right before you execute; BlindPay quotes last 5 minutes |
| Sent after TED or ACH Colombia cut-off | Brazil, Colombia | Expect the next banking day; cut-off times |
When a payout fails 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 like these, that refund is automatic.
Fund every payout in a stablecoin and let the payout API pick the local rail. You hold one dollar balance instead of four local-currency accounts.
With BlindPay, you add each recipient's bank account once, request a payout quote in USDC or USDT (or by the exact local amount the recipient should get), and execute it before it expires. Fees vary by rail and network and appear line by line in the live quote; there is no public static rate card. Stablecoins plus local rails explains why this model fits the region, and blockchain payments vs crypto payments explains why the recipient never sees crypto at all.
The same four countries work in reverse for collections: Pix, SPEI, Transfers, and PSE in Colombia can all fund stablecoins. How to integrate a crypto on-ramp API covers that side.
Check your recipient forms against the table above: one field set per country, validated before submission. Then send a test payout per country on a development instance, where payouts complete automatically.
Open the BlindPay bank accounts docs to copy the exact field names for Pix, SPEI, ACH Colombia, and Transfers into your form.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
Push means the payer sends an ACH transfer. Pull means you debit a connected account. How each funds a USD to USDC on-ramp, the fees, and the return risk.
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.