A stablecoin sandwich turns fiat into a stablecoin, moves it across a border on-chain, then back into local currency. Its three layers, costs, and timing.
A stablecoin sandwich is a cross-border payment that starts and ends in bank money, with a stablecoin in the middle. The sender's currency becomes a dollar token such as USDC, the token crosses the border on a blockchain in minutes, and it becomes local currency again in the recipient's bank account. Nobody at either end needs to hold crypto.
The term is shorthand used by payment teams and researchers. It describes almost every business use of stablecoins for cross-border payouts today, so it's the right mental model before you look at fees, rails, or providers.
Key takeaways
It's three conversions of state: money in, token across, money out.
Take a US company paying a supplier in Brazil 10,000 dollars (an illustrative example):
The supplier sees a Pix credit in BRL. The word "stablecoin" never appears on their statement.
| Layer | What happens | Who usually runs it | Where cost shows up |
|---|---|---|---|
| On-ramp | Fiat becomes a stablecoin | Issuer, exchange, or ramp provider | Conversion spread, funding rail fee |
| On-chain transfer | Token moves between addresses | The blockchain network | Network (gas) fee, usually cents |
| Off-ramp | Stablecoin becomes local fiat and is paid out | Payout provider with local banking | FX spread, payout rail fee, provider fee |
Because it shortens the chain of banks between sender and recipient.
A traditional international wire runs through correspondent banks that hold accounts for each other in different currencies. A March 30, 2026 FEDS Note from Federal Reserve staff lists what that chain costs end users: more time, because each intermediary processes the payment; poor visibility, because the payment can sit at any bank in the chain; and redundant AML checks run at several points. The same note says more than 60 percent of wholesale payments are routed through one or more intermediaries.
The sandwich replaces the middle of that chain with a token transfer. The Fed note's own example, a payment from the US to Mexico, shows the stablecoin going straight from the sender's side to the recipient's side, which "would eliminate any intermediation fee, reduce the time for the payment to reach the final recipient, and make it easier to track the payment."
It also removes pre-funding. With correspondent banking or a classic remittance network, someone parks money in foreign accounts ahead of time. In a sandwich, conversion happens per payment against a live quote. Nostro and vostro accounts explained shows why the old model ties up capital.
In the slices, not the filling.
The same Fed note is direct about this: the on-chain cost of moving stablecoins between entities that already hold them "is likely to be small," but "there may be greater 'on-ramp' and 'off-ramp' costs associated with exchanging payment stablecoins for fiat currency." It also notes that the receiving side still depends on someone to take the foreign exchange risk.
So the cost stack looks like this:
Why on-ramp and off-ramp rates differ covers the bid and ask behind each slice, and onchain liquidity vs off-ramp liquidity explains why a deep token market doesn't guarantee a deep BRL or COP payout.
The filling takes minutes. The top slice decides the total.
| Layer | Typical time |
|---|---|
| On-ramp from a bank transfer | Depends on the funding rail; zero if you already hold stablecoins |
| On-chain transfer | Seconds to minutes, depending on the network |
| Off-ramp over Pix, PIX Safe, SPEI, or Transfers 3.0 | Minutes |
| Off-ramp over RTP | Instant |
| Off-ramp over ACH, wire, TED, ACH Colombia, or SEPA | About 1 to 2 business days |
| Off-ramp over SWIFT | Up to 5 business days |
These are typical windows, not guarantees. A compliance review can hold any payment, and bank-side rails like ACH and SWIFT follow banking days. Stablecoin payout cut-off times covers weekends and holidays rail by rail.
Usually different companies, sometimes one.
A business can assemble these pieces itself or buy them through one API. Who is involved in a blockchain payment maps each role and what it's responsible for.
The recipient doesn't. The sender might not either.
If the payout provider runs the off-ramp, the recipient only needs a bank account and the usual details: a Pix key in Brazil, a CLABE in Mexico, an IBAN in Europe. The sender can hold USDC in its own wallet, or fund the payment from a bank account and let the provider handle the on-ramp. Do you need a crypto wallet for stablecoin payments? walks through each setup.
There's also a variant where the FX happens on-chain: the dollar stablecoin is swapped into a euro stablecoin before redemption. Most volume today stays in dollar tokens, so the classic sandwich is the one you will run into.
Three things don't change because a token sits in the middle.
Compliance. KYC on individuals, KYB on businesses, sanctions screening, and transaction monitoring apply at both ends. The CPMI's October 2023 report on stablecoin arrangements in cross-border payments puts it as "same business, same risks or risk profile, same regulatory outcome."
Liquidity. Converting USDC into BRL or MXN at scale needs a provider with real local currency depth. Thin corridors mean wider spreads or smaller maximums.
Issuer risk. A stablecoin is only as good as its reserves and redemption. Stablecoin depeg risk covers what past depegs teach and how to set limits.
The market is large enough to take seriously. Allium's September 2026 report puts total stablecoin supply at 303 billion dollars in August 2026.
Start from one corridor and one payment type.
BlindPay runs the top slice, and the bottom one when you need it, through one API. You send USDC or USDT from Ethereum, Polygon, Base, Arbitrum, Tempo, Arc, Stellar, Solana, or Tron, and BlindPay pays out over Pix, PIX Safe, TED, SPEI, ACH Colombia, Transfers 3.0, ACH, wire, RTP, SEPA, and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations. Each quote locks the rate and fees for 5 minutes. KYC and KYB run in the same API. BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. BlindPay combines a monthly plan with per-transaction fees that vary by rail and network, disclosed in the live quote before execute.
Take your most expensive cross-border payment from last month and price it as a sandwich: one live quote, same amount, same recipient. If the delivered amount and timing beat the wire, run five real payouts in that corridor before you move more volume. The payout quotes docs show the request shape on a development instance.
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.