explains
The Fiat Sandwich
Most cross-border stablecoin payments are fiat in, stablecoin in transit, fiat out.
Published
Most cross border stablecoin payments do not involve anyone paying in crypto. The dominant model is simpler: fiat in, stablecoin in transit, fiat out.
Reader Brief
Most cross-border stablecoin payments do not involve anyone paying in crypto. The dominant model is simpler: fiat in, stablecoin in transit, fiat out. The stablecoin is the filling, not the bread.
Reading Guide
Four moves that explain why fiat-in-stablecoin-out is the dominant cross-border architecture and what makes it institutionally legible.
Fiat sandwich means fiat in, stablecoin in transit, fiat out.
Neither end user touches crypto. Neither needs a wallet. The stablecoin is the pipe between two fiat endpoints, held for minutes by licensed operators, not by users. Five steps, minutes total: sender pays in local fiat; licensed on-ramp converts to stablecoin; stablecoin transits across border; licensed off-ramp converts to fiat; recipient receives local currency. The user experience is indistinguishable from a bank transfer. This is fundamentally different from "paying in crypto." Direct crypto usage puts exchange-rate and custody risk on the user; the fiat sandwich confines crypto exposure to the settlement layer for minutes. Most regulatory confusion comes from treating the fiat sandwich as if it were direct crypto usage. The architectures are not the same.
The model exists because correspondent banking is structurally contracting.
BIS data shows that the number of active correspondent banking relationships worldwide fell roughly **22%** between 2011 and 2019 [1]. The decline is not regional. It is evident across advanced economies, emerging Asia, Latin America, the Middle East, and Sub-Saharan Africa [2]. As correspondent banking relationships disappear, the cost and friction of moving value rises. Stablecoins filled the gap because they offer four operator advantages: **speed**, with settlement in minutes rather than T+1 to T+5 days; **availability**, with rails that run continuously rather than around business days and cut-off times; **reach**, through licensed operators where banks have exited corridors; and **programmability**, with payment logic, compliance checks, and reporting attached to the on-chain leg. What the model does not solve is structural FX scarcity, weak currencies, or trade-finance gaps. Stablecoins move value faster; they do not create new dollars. The fiat sandwich is useful infrastructure, not a macroeconomic solution.
Compliance clears before value moves, not after.
In a properly designed fiat sandwich, KYC/KYB checks on the originator and beneficiary, sanctions screening against OFAC, EU, and local lists, and Travel Rule data assembly run before any stablecoin is minted or transferred [4]. Only after compliance clears does the on-ramp convert fiat to stablecoin. The on-chain leg carries value that has already been vetted. This is the opposite of how most peer-to-peer stablecoin transfers work today. What supervisors gain is corridor data they never had before: volume per corridor per day, settlement-time benchmarking, compliance-completion rate, AML signal detection, and dollarization early warning through the stablecoin inflow/outflow ratio [5]. None of this exists for informal stablecoin channels.
Six jurisdictions already regulate this as a payment service.
No jurisdiction needed to invent a new regime. ADGM expanded Regulated Activities to include fiat-referenced tokens; Singapore added stablecoin activities to the Payment Services Act; Brazil classified stablecoin activity into the FX perimeter; the UK launched a stablecoin sandbox through the FCA; the UAE placed payment tokens under central-bank supervision; and Chile integrated stablecoins into the payments perimeter through fintech-law work [6][7]. The pattern is simple: stablecoins used for payments belong under existing central-bank oversight. Function-based regulation, transit versus holding, determines which authority supervises, which license applies, and which controls are required. Getting the classification wrong produces the five-stage trap: ignore, ban, license trading, get stuck on payments, and lose activity to regulatory arbitrage.
The Model
A cross-border payment where users stay in fiat and the stablecoin exists only in the middle.
A fiat sandwich is a cross-border payment where sender and recipient both use fiat currency. The stablecoin exists only in the middle, as a settlement instrument in transit. Neither end user touches crypto. Neither end user needs a wallet. The stablecoin is the pipe between two fiat endpoints.
| Step | What happens | What the user sees |
|---|---|---|
| 1. Funding | Sender pays a licensed provider in local currency. | Normal local payment. |
| 2. On-ramp | Provider converts fiat into a stablecoin such as USDT or USDC. | Nothing. Handled by the operator. |
| 3. Transit | Stablecoin moves on-chain to the destination operator. | Nothing. Settles in seconds. |
| 4. Off-ramp | Destination operator converts stablecoin into local fiat. | Nothing. Handled by the operator. |
| 5. Disbursement | Recipient receives fiat in a bank account or mobile wallet. | Normal incoming payment. |
Five steps, minutes total.
The customer is buying a **payment outcome**, not a token experience. That distinction is the reason the model works for institutional and retail use cases that would never adopt crypto payments. The sender makes a normal local payment. The recipient receives a normal local payment. Everything that looks like crypto happens between regulated operators in the settlement layer.
Why this is not the same as "paying in crypto"
Two models exist in the market. They look similar from the outside but carry fundamentally different risk profiles. **Model A: Direct crypto usage.** User holds crypto. User spends crypto. Recipient may receive crypto. Exchange-rate and custody risk sit with the user. **Model B: Fiat sandwich.** User starts with fiat. Licensed institutions handle the conversion. Recipient ends with fiat. Crypto exposure is confined to the settlement layer, for minutes. Most regulatory confusion comes from treating Model B as if it were Model A. In Model B, the stablecoin is acting like a settlement instrument, closer to a SWIFT message with built-in value, rather than a consumer asset.
Why This Model Exists
Correspondent banking is structurally expensive, slow, and contracting.
The fiat sandwich exists because cross-border correspondent banking is structurally expensive, slow, and contracting. The number of active correspondent banking relationships worldwide fell roughly **22%** between 2011 and 2019 [1]. The decline is not regional. BIS data shows it across advanced economies, emerging Asia, Latin America, the Middle East, and Sub-Saharan Africa [2]. As these relationships disappear, the cost and friction of moving value across borders rises. Stablecoins filled the gap because they offer settlement finality in minutes, on rails that operate continuously [3].
| Pressure | What it means |
|---|---|
| ~22% | Global decline in active correspondent banks from 2011 to 2019 [1]. |
| 24/7 | Stablecoin rails operate continuously, unlike banking hours and corridor cut-off times [3]. |
Four reasons operators choose this architecture
**1. Speed.** Settlement in minutes instead of T+1 to T+5 days. For an importer paying a supplier, same-day finality means less capital lockup. **2. Availability.** Stablecoin rails operate 24/7/365. Correspondent banking operates on business days, business hours, with cut-off times that vary by corridor. **3. Reach.** Value can move across corridors where correspondent banking relationships have been cut. When a bank exits a corridor, the fiat sandwich provides an alternative settlement path through licensed operators. **4. Programmability.** Payment logic, compliance checks, and reporting can be attached to the on-chain leg. This is harder to do with SWIFT messages.
What the model does not solve
Stablecoins **move value faster**. They do **not create new dollars**. If a country has a structural shortage of external currency, the fiat sandwich can improve settlement mechanics. It cannot fix the macro imbalance. A fiat sandwich can compress spreads where licensed competition exists. It can provide an alternative settlement rail where correspondent banking is slow or unavailable. It can make informal flows supervisable when those flows move into licensed channels. It does not create new dollars. The fiat sandwich is useful infrastructure. It is not a macroeconomic solution.
The Compliance Layer
The dividing line between a useful hack and real infrastructure.
A fiat sandwich without compliance is just a faster informal rail. With compliance, it becomes something different: a cross-border payment architecture that institutions and regulators can actually work with. That is the dividing line between a useful hack and real infrastructure.
| Sequence | Control | When it happens |
|---|---|---|
| 1 | KYC/KYB checks | Before on-chain transfer. |
| 2 | Sanctions screening | Before on-chain transfer. |
| 3 | Travel Rule data assembled | Before on-chain transfer [4]. |
| 4 | On-chain transit | After compliance clears. |
| 5 | Aggregate reporting and audit trail | After settlement [5]. |
Compliance clears before value moves. Not after.
In a properly designed fiat sandwich, the compliance sequence runs **before** any stablecoin is minted or transferred: KYC and KYB checks on originator and beneficiary; sanctions screening against OFAC, EU, and local lists; and Travel Rule data assembled per FATF Recommendation 16 [4]. Only after compliance clears does the on-ramp convert fiat to stablecoin. The on-chain leg carries value that has already been vetted. This is the opposite of how most peer-to-peer stablecoin transfers work today.
What supervisors gain: corridor data they never had before
Licensed operators submitting aggregate reports give central banks visibility into information that is missing from informal stablecoin channels. | Data point | Why it matters | | --- | --- | | Volume per corridor per day | Balance-of-payments visibility [5] | | Average settlement time | Infrastructure performance benchmarking | | Compliance completion rate | Quality of operator implementation | | Flagged transactions | AML signal detection | | Stablecoin inflow/outflow ratio | Dollarization early warning | A regulator who brings flows into a supervised fiat sandwich gains information that was previously invisible [5].
The Policy Implication
Transit and holding are different economic functions, so they need different regulatory treatment.
The fiat sandwich is one of the clearest examples of why regulators need to separate **transit** from **holding**. If a stablecoin is used for minutes to settle a payment between two fiat endpoints, the policy question is different from a case where households use stablecoins as savings. Function-based regulation treats each behavior according to its actual risk profile.
| Function | Holding period | Regulatory frame |
|---|---|---|
| Transit | Minutes | Regulate as a payment service: fiat in, stablecoin in transit, fiat out. |
| Holding | Days to months | Regulate as deposit or FX holding risk: balance caps, no yield, and contained exposure. |
Six jurisdictions already regulate stablecoins as payment instruments under existing frameworks
No jurisdiction needed to invent a new regime. Each extended existing regulation. - **ADGM**: expanded Regulated Activities to include fiat-referenced tokens - **Singapore (MAS)**: added stablecoin activities to the Payment Services Act - **Brazil (BCB)**: classified stablecoins as FX instruments - **UK**: launched a stablecoin sandbox under the FCA - **UAE**: placed stablecoins under central-bank supervision through the Payment Token Service Regulation - **Chile**: integrated stablecoins into the payments perimeter through fintech-law work The pattern: stablecoins used for payments belong under **existing central-bank oversight**, not under a new crypto-specific regime [6][7].
The distinction between transit and holding is not semantics.
How a regulator classifies stablecoin activity determines which authority supervises it, which license applies, which risk controls are required, and whether institutional operators can participate. Transit points to central-bank or payment-service supervision. Holding points to deposit, FX, and savings-substitution controls. Getting the classification wrong produces the five-stage trap documented in the Tap Protocol: ignore, ban, license trading, get stuck on payments, and lose activity to regulatory arbitrage. Getting it right starts with recognizing that transit and holding are different economic functions [6].
Counter-Arguments & Limitations
Evidence And Sources
This raw HTML export preserves source visibility for crawler and contractor review. Indexing decision: index, follow.
- Correspondent Banking Data Report - BIS CPMI
- Cross-border payments: a catalyst for global integration - Bank for International Settlements
- The stable door opens: How tokenized cash enables next-gen payments - McKinsey
- Updated Guidance for VAs and VASPs - FATF
- Project Aurora - BIS Innovation Hub
- GENIUS Act; Payment Token Service Regulation - US Senate; Central Bank of the UAE
- FRT Framework; Payment Services Act - ADGM FSRA; Monetary Authority of Singapore