---
title: "What is a stablecoin sandwich? How cross-border stablecoin payments go from fiat to fiat"
seoTitle: "What is a stablecoin sandwich? Fiat to fiat, explained"
description: "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."
date: "2026-10-03"
updated: "2026-10-03"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "What is a stablecoin sandwich?"
    a: "A stablecoin sandwich is a cross-border payment that starts and ends in ordinary bank money with a stablecoin in the middle. The sender's currency is converted into a dollar stablecoin such as USDC, the token moves across the border on a blockchain, and it is converted into the recipient's local currency and paid into a bank account. Neither end has to hold crypto."
  - q: "Why is it called a sandwich?"
    a: "Because the stablecoin is the filling between two slices of fiat. The first slice is the on-ramp, where dollars, reais, or pesos become a stablecoin. The second slice is the off-ramp, where the stablecoin becomes local currency again. The on-chain transfer in the middle is the part that crosses the border, and it is usually the cheapest and fastest part."
  - q: "Where does the cost of a stablecoin sandwich sit?"
    a: "Mostly in the two slices, not the filling. A March 2026 Federal Reserve FEDS Note says the on-chain cost of moving stablecoins between holders is likely small, while on-ramp and off-ramp costs can be greater. In practice the spread on each conversion, the payout rail fee, and the provider's fee decide the total. Compare the amount the recipient receives, not the network fee."
  - q: "Does the recipient need a crypto wallet?"
    a: "No, not when a payout provider runs the off-ramp. The provider receives the stablecoin, converts it, and pays the recipient's bank account over a local rail such as Pix in Brazil, SPEI in Mexico, or SEPA in Europe. The recipient sees a normal bank credit in their own currency. Only the sender's side touches a stablecoin, and often the provider handles that too."
  - q: "How long does a stablecoin sandwich take?"
    a: "The on-chain transfer usually confirms in seconds to minutes, depending on the network. The total time is set by the payout rail at the end. Instant rails such as Pix and SPEI settle in minutes, ACH and SEPA take about one to two business days, and SWIFT can take up to five business days. Compliance review can add time on any rail."
  - q: "Is a stablecoin sandwich always cheaper than a wire?"
    a: "No. It removes correspondent banking hops and the need to pre-fund foreign accounts, which often lowers cost. But each conversion carries a spread, local currency liquidity can be thin in smaller corridors, and compliance checks still apply. For some corridors and payment sizes a bank wire or a local transfer is competitive. Request a quote for the exact amount before deciding."
---

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**

- The sandwich has three layers: an on-ramp (fiat to stablecoin), an on-chain transfer, and an off-ramp (stablecoin to local fiat).
- The on-chain transfer is the cheap, fast part. Most of the cost and time sit in the two conversions and the payout rail.
- Recipients get a normal bank credit over a local rail, such as Pix, SPEI, ACH, or SEPA.
- Compliance applies at both ends. KYC, KYB, and sanctions screening don't go away because a token is in the middle.
- Judge a sandwich by the amount delivered and the time to the recipient's account, not by the network fee.

## What does a stablecoin sandwich look like, step by step?

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):

1. **Bottom slice, the on-ramp.** The company's dollars are converted into 10,000 USDC. If the company already holds USDC, this step is skipped.
2. **Filling, the on-chain transfer.** The USDC moves from the sender's wallet to the payout provider's address on a network such as Polygon, Solana, or Base. Settlement takes seconds to minutes.
3. **Top slice, the off-ramp.** The provider converts the USDC into reais at the quoted rate and pays the supplier's account over Pix.

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 |

## Why do businesses use the sandwich instead of a wire?

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](https://www.federalreserve.gov/econres/notes/feds-notes/payment-stablecoins-and-cross-border-payments-benefits-and-implications-for-monetary-policy-20260330.html) 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](/resources/more/nostro-vostro-accounts-explained) shows why the old model ties up capital.

## Where does the cost of a stablecoin sandwich actually sit?

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:

- **On-ramp spread.** The difference between the rate you get and the market rate when fiat becomes a stablecoin. Zero if you already hold USDC.
- **Network fee.** Usually cents on networks like Polygon, Solana, Base, or Stellar. More on Ethereum mainnet.
- **Off-ramp FX spread.** The markup on the stablecoin to local currency rate. This is the line that moves most between providers and corridors.
- **Payout rail fee.** What it costs to deliver over Pix, SPEI, ACH, SEPA, or SWIFT.
- **Provider fee.** Fixed, percentage, or both.

[Why on-ramp and off-ramp rates differ](/resources/more/why-onramp-and-offramp-rates-differ) covers the bid and ask behind each slice, and [onchain liquidity vs off-ramp liquidity](/resources/more/onchain-liquidity-vs-offramp-liquidity) explains why a deep token market doesn't guarantee a deep BRL or COP payout.

## How long does each layer take?

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](/resources/more/stablecoin-payout-cut-off-times-weekends-holidays) covers weekends and holidays rail by rail.

## Who runs each layer of the sandwich?

Usually different companies, sometimes one.

- **Stablecoin issuers** such as Circle (USDC) and Tether (USDT) mint and redeem tokens against reserves.
- **Exchanges and ramp providers** convert fiat to stablecoins and back.
- **Blockchain networks** move the token and finalize the transfer.
- **Payout providers** hold the local banking relationships that deliver Pix, SPEI, ACH, or SEPA payments and run the compliance checks on each payout.

A business can assemble these pieces itself or buy them through one API. [Who is involved in a blockchain payment](/resources/more/who-is-involved-in-a-blockchain-payment) maps each role and what it's responsible for.

## Does anyone in the sandwich need to touch crypto?

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?](/resources/more/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.

## What are the limits and risks?

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](https://www.bis.org/cpmi/publ/d220.htm) 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](/resources/more/stablecoin-depeg-risk-payments) covers what past depegs teach and how to set limits.

The market is large enough to take seriously. [Allium's September 2026 report](https://www.allium.so/reports/state-of-stablecoins-and-payments-september-2026) puts total stablecoin supply at 303 billion dollars in August 2026.

## How do you get started with a stablecoin sandwich?

Start from one corridor and one payment type.

1. Pick the corridor where wires hurt most, for example US to Brazil supplier payments.
2. Decide who holds the stablecoin: you, in your own wallet, or the provider, funded from your bank account.
3. Request a live quote for a real amount and compare the delivered BRL with your last wire.
4. Run a small batch of real payouts and measure time to the recipient's account.
5. Write down who owns KYC, KYB, and screening in your setup before you scale.

## How does BlindPay handle the stablecoin sandwich?

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.

## What to do next

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](/docs/payout-quotes) show the request shape on a development instance.