Pix vs SPEI side by side: who runs each rail, how recipients are identified, hours, settlement, returns, and proof of payment for stablecoin payouts.
Pix and SPEI are the instant payment rails of Brazil and Mexico. Pix is run by the Banco Central do Brasil and pays reais; SPEI is run by Banco de México and pays pesos. Both run 24/7 and settle in real time between institutions at the central bank. They differ in how recipients are addressed, how returns work, and how payment proof is issued.
For a company paying people in Latin America, these two rails do most of the work. If you pay out from stablecoins, they are the last leg after the conversion, and the leg the recipient actually sees.
Key takeaways
This page compares the rails themselves. For the specific fields to collect, see Pix keys, CPF, and CLABE payout details. For where these rails sit in the full payment stack, start with what stablecoin infrastructure is.
Pix is Brazil's instant payment scheme and SPEI is Mexico's interbank electronic payment system. Both are central bank infrastructure that banks and other licensed institutions plug into.
Pix is governed by the Pix regulation attached to Resolution BCB No. 1 of August 12, 2020. Payments settle in the SPI (Sistema de Pagamentos Instantâneos), which the regulation defines as a centralized real-time gross settlement infrastructure between participants holding an instant payments account at the Central Bank. Recipients are looked up through the DICT, the central directory that maps Pix keys to accounts.
SPEI (Sistema de Pagos Electrónicos Interbancarios) is administered and operated by Banco de México. Banxico describes it as a real-time settlement system that began operating on August 13, 2004 and runs on a 24/7 scheme. Its rules are set out in Banxico's Circular 14/2017.
Pix and SPEI are close on speed and hours. They differ most on addressing, returns, and proof of payment.
| Feature | Pix (Brazil) | SPEI (Mexico) |
|---|---|---|
| Operator | Banco Central do Brasil | Banco de México |
| Currency | BRL | MXN |
| Settlement | SPI, real-time gross settlement in central bank accounts | Real-time settlement at Banco de México |
| Hours | 24 hours a day, every day of the year | 24/7 scheme |
| Speed | Real time by definition in the regulation | Should not exceed 30 seconds, per Banxico |
| Recipient identifier | Pix key: CPF, CNPJ, phone, email, or random key | 18-digit CLABE, 16-digit debit card, or 10-digit phone |
| Recipient lookup | DICT returns the account holder before payment | CLABE check digit catches typos; no name lookup |
| Proof of payment | Receipt from the paying institution, with a transaction identifier | CEP issued from the receiving bank's confirmation |
| Tracking reference | Pix transaction identifier | Tracking key (clave de rastreo), up to 30 characters |
| Returns | Recipient can return within 90 days; MED for fraud | Receiving bank returns orders it can't credit |
| Fees between institutions | Regulation bars fees between the payer's and recipient's institutions | Banxico charges participants a fixed fee and a per-operation fee |
| QR payments | Static and dynamic Pix QR codes in the regulation | No data |
Two rows matter most for payouts. The recipient lookup row is why Pix keys produce fewer misdirected payments: the payer's institution sees the account holder's name before sending. The proof of payment row is why SPEI disputes are easier to close: anyone with the payment details can pull the CEP.
On Pix you address a key; on SPEI you address an account number, card, or phone.
Pix keys come in five types. The key resolves through the DICT to the recipient's account, so the payer never needs a bank code or branch. When a recipient has no key, many providers can pay the bank account directly using the bank code, branch, and account number.
SPEI destinations follow Banxico's user guide: an 18-digit CLABE, a 16-digit debit card number, or a 10-digit mobile phone number linked to the account. The CLABE includes a check digit, so many typos fail validation before any money moves. Card and phone destinations also need the receiving bank's institution code.
Pix keys, CPF, and CLABE payout details lists exactly what to collect from recipients in each country.
Pix has a written return framework with deadlines. SPEI returns are mostly operational: the receiving bank sends back what it can't credit.
On Pix, the Central Bank's guide to Pix returns and the MED sets out three paths:
On SPEI, a payment is returned when the receiving bank can't apply it, for example because the account is closed or the details don't match. Banxico's MI-SPEI status lookup shows the state as "undergoing return" and then "returned." The Mexico payout guide lists every SPEI status and what to do at each one.
Neither rail lets the sender pull money back. If the account details were valid but wrong, getting money back depends on the recipient or their bank. Are stablecoin payments reversible? covers the same question for the on-chain leg.
On SPEI, download the CEP. On Pix, rely on the paying institution's receipt and the transaction identifier.
The SPEI CEP lookup takes the payment date, the tracking key or reference number, the sending and receiving banks, the beneficiary account, and the amount. Banco de México generates the receipt from the receiving bank's credit confirmation. The lookup runs from 09:30 to 23:00, Monday to Sunday. The tracking key is up to 30 alphanumeric characters; the reference number is up to seven digits.
Pix has no equivalent public lookup. The receipt comes from the institution that sent the payment and carries a unique transaction identifier. In a stablecoin payout, that sending institution is your provider's local partner, so ask your provider which reference it returns and where. How to track a crypto off-ramp payout compares the references across rails.
A stablecoin payout to Brazil or Mexico has the same shape on both rails: quote, send the stablecoins, convert, and push local currency over the rail.
Step 5 is the shortest step. Steps 1 and 3 decide most outcomes. A wrong key or CLABE fails at the rail, and an under-confirmed on-chain transfer delays everything after it. Stablecoin payout cut-off times, weekends, and holidays explains when non-instant parts of the flow can still stall.
The failures look different on each rail, but most come from recipient data.
| Problem | On Pix | On SPEI | What to do |
|---|---|---|---|
| Wrong recipient | Key belongs to someone else | Valid CLABE for the wrong person | Show the resolved name before paying where possible; confirm details in writing |
| Invalid details | Key not found in the DICT | CLABE check digit fails | Validate at entry, not at payout time |
| Closed account | Institution can't credit, returns funds | Receiving bank returns the order | Get new details, then resend after the return completes |
| Fraud suspicion | Cautionary block up to 72 hours, MED return | Bank holds or returns per its own controls | Keep KYC and purpose records ready for the provider |
| Dispute "I didn't get it" | Share the transaction identifier and receipt | Share the CEP | Store the rail reference on every payout record |
Both rails are domestic, single-currency, and designed for bank accounts in one country. They don't fit every payout.
BlindPay converts USDC or USDT into reais or pesos and pays out over Pix and SPEI through one API, alongside ACH, RTP, SEPA, and SWIFT (POBO/COBO).
From the BlindPay docs as of this article's date:
pix_key, which can be a CPF, CNPJ, phone, email, or random key. When you have bank routing instead of a key, the PIX Safe account type uses the CPF or CNPJ, bank code, branch, and account number. Both settle instantly.processing to completed. A payout that ends refunded returns the stablecoins to the funding source; a failed payout isn't refunded automatically, so contact support (payouts).Development instances are free. Add a Pix key or CLABE in the sandbox and run your first test payout from the payout quickstart.
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.
Seven stablecoin payment platforms compared for US fintechs in 2026: what makes an API production-ready, how each provider handles compliance, settlement speed against ACH, and how to run the evaluation.