Six real payment scenarios, one rail each: supplier in Mexico, contractors in Brazil, EU payouts, remittances, US collections, and weekend treasury moves.
No single rail wins every payment. Stablecoin rails win when money crosses a border and has to land fast, especially into countries with instant local systems like Pix and SPEI. ACH wins for domestic US dollars. SEPA wins inside the euro zone. SWIFT still wins for reach. Cards win at consumer checkout. Pick the rail per scenario.
The difference between the rail and the money on it is covered in blockchain payments vs crypto payments. Here we compare rails head to head, then walk through six scenarios.
Key takeaways
Each rail was built for a different job, and it shows in hours, reach, and reversibility. The table compares them on the dimensions that decide a business payment.
| Blockchain (stablecoin) | SWIFT | ACH | Domestic wire | Cards | Local instant (Pix, SPEI) | |
|---|---|---|---|---|---|---|
| Settlement time | Seconds to minutes on-chain | Hours to days to the end customer | Same day to next business days | Same day | Days to the merchant | Seconds |
| Operating hours | 24/7/365 | Bank hours, per correspondent | Business days | Business days | 24/7 to authorize | 24/7/365 |
| Cost components | Network fee, on-ramp, off-ramp, FX spread | Sender fee, intermediary deductions, FX spread, receiving fee | Low per item fee | Flat wire fee | Interchange, scheme, acquirer fees | Low or zero per item |
| Geographic reach | Anywhere with a wallet, plus a local off-ramp to reach a bank | 200+ countries | US accounts | Domestic accounts | Anywhere cards are accepted | One country each |
| Reversibility | Final once confirmed | Recalls possible, not guaranteed | Returns and reversals within rule windows | Final | Chargebacks | Final, with fraud refund schemes |
| Compliance load | KYC, KYB, wallet screening, Travel Rule | KYC, sanctions, purpose of payment | KYC, Nacha rules | KYC, sanctions | Merchant onboarding, PCI | KYC, local tax ID |
| Programmability | High (APIs, smart contracts) | Low (messages) | Medium (files, APIs) | Low | Medium | Medium (APIs, QR codes) |
Two caveats. A blockchain payment that ends in a bank account inherits the hours of the bank rail at the end. And a SWIFT payment reaching the bank fast is not the same as reaching the customer: Swift said in October 2024 that 90% of payments on its network reach the destination bank within an hour, while only 43% reach the end customer within an hour.
Definition: A payment rail is the system that moves money between two accounts and settles it, with its own rules for hours, limits, fees, and reversals. ACH, SWIFT, Pix, and a public blockchain carrying a stablecoin are all rails.
The yardstick most regulators use is the G20 roadmap. The Financial Stability Board's final targets report (October 2021) sets, for retail cross-border payments by end-2027, an average cost of no more than 1% with no corridor above 3%, and 75% of payments credited within one hour, the rest within one business day. These are retail targets. Wholesale payments have speed targets but no cost target.
Remittances have their own goal: an average cost of 3% by 2030. The World Bank's Remittance Prices Worldwide (Issue 54, Q3 2025 data) put the global average cost of sending $200 at 6.36%, more than double that goal.
What cross-border payments cost in 2026 has the corridor numbers.
Use a stablecoin leg ending in a SPEI payout in pesos. It usually beats a USD wire over SWIFT on speed and on what actually arrives.
A SWIFT wire to Mexico can pass through correspondent banks, each able to deduct a fee, and the supplier's bank converts to pesos at its own rate. With stablecoin settlement, the company funds in dollars, the value moves as USDC or USDT, and the supplier receives pesos over SPEI, Banco de México's instant system, which runs 24/7. The supplier needs a CLABE, the 18-digit account number. What details you need to pay someone in Brazil or Mexico lists them.
When SWIFT still wins: the supplier contractually requires a USD wire into a dollar account, or your bank relationship already prices wires well at your volume.
A stablecoin leg ending in Pix. Contractors get reais in seconds, any day, in their own bank account.
Pix is run by Banco Central do Brasil and works every day of the year. The alternatives are a SWIFT wire, which lands in days and often short of the invoiced amount, or a contractor holding a foreign dollar account and converting it themselves. For monthly payroll across dozens of people, the difference in support tickets alone is large. Stablecoin payroll for LATAM contractors covers the workflow.
When it is not the right fit: contractors who want to be paid in USD into a US account. Then ACH or a wire is simpler.
It depends on the currency you hold. If the marketplace already holds euros in a European bank, SEPA directly. If it holds dollars or stablecoins, a stablecoin leg ending in a SEPA payout avoids a separate FX and wire step.
SEPA covers the euro zone and several non-euro countries under one scheme. Instant euro transfers are becoming the default under the EU Instant Payments Regulation. A marketplace funded in USD from US buyers faces two jobs: convert to euros and pay out locally. Off-ramping USDC to euros over SEPA shows the second half, with IBAN details and timing.
Sometimes. They help most on expensive corridors where the recipient can receive on a local instant rail, and least where cash pickup or thin off-ramp liquidity sets the cost.
The Federal Reserve's March 30, 2026 FEDS Note on payment stablecoins and cross-border payments makes the key point: stablecoins can cut intermediary fees and delivery time, but on-ramp and off-ramp costs can remain even when on-chain costs are small. With the global average at 6.36% per $200, there is room to win. Whether you do depends on the spread at both ends, not the network fee.
When to stay traditional: corridors where recipients need cash, or where no licensed off-ramp pays out in local currency at a competitive rate.
ACH, RTP, or cards, not a blockchain. Both payer and payee are in dollars, in the US, inside rails that already work.
ACH debits suit subscriptions and invoices. RTP and wires suit urgent or large payments. Cards suit consumer checkout, where the buyer expects to pay that way. A stablecoin leg here means converting dollars to stablecoins and back for no reason. When not to use blockchain payments lists this and six other cases.
The exception is a business that wants the collected dollars to end up as stablecoins, for example to fund payouts abroad. Then a virtual account that converts incoming ACH or wire deposits into USDC makes the domestic leg useful.
A stablecoin transfer. It is the only rail in the table that settles cross-border on a Saturday.
Funding a subsidiary or a payout float on Friday evening over SWIFT means Monday at the earliest, often later. Moving USDC between wallets settles in seconds to minutes. The catch: the local payout at the far end still follows the local rail's calendar. Pix and SPEI run all week, while ACH and standard SEPA credit transfers wait for business days. Cut-off times, weekends, and holidays by rail has the calendar.
| Scenario | Usual winner | Runner-up | Deciding factor |
|---|---|---|---|
| US company pays supplier in Mexico | Stablecoin + SPEI | SWIFT wire in USD | Supplier's currency and account |
| Contractors in Brazil | Stablecoin + Pix | SWIFT wire | Speed and full-amount delivery |
| Marketplace payouts in Europe | SEPA (if holding EUR) or stablecoin + SEPA (if holding USD) | SWIFT | Currency you hold |
| Remittance | Depends on corridor | Licensed money transfer operator | Off-ramp spread and cash needs |
| Domestic US collections | ACH, RTP, or cards | Wire | Both sides in USD |
| Weekend treasury move | Stablecoin transfer | None | Rail operating hours |
They pick the payout rail per recipient and keep one integration. That is the point of an API that sits on top of several rails.
BlindPay, a Y Combinator-backed payments API, connects stablecoin settlement to US and local rails: ACH, wire, RTP, and SWIFT (POBO/COBO) for dollars, Pix in Brazil, SPEI in Mexico, Transfers in Argentina, ACH Colombia, and SEPA in Europe. Its docs list documented timing per rail, from instant for RTP, Pix, and SPEI to about 5 business days for international SWIFT (overview). SWIFT payouts carry the customer's name under the POBO model, explained in POBO vs COBO.
List your last 50 outgoing payments by country, currency, and amount. Mark which ones crossed a border and which ones landed late or short. Those are the payments to move to a stablecoin leg plus a local payout first. Leave domestic dollars on ACH.
See the rails and documented settlement times BlindPay supports in the API overview.
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.