A customer sends you a bank transfer on Monday morning. By early afternoon, a stablecoin balance appears on-chain. From the outside it looks like one step. Underneath, that money crossed four different systems — a bank rail, a compliance layer, a liquidity venue, and a blockchain — each with its own clock, its own rules, and its own ways of running late.
Understanding those four stages is the difference between watching a pending transfer with dread and knowing exactly which part of the pipeline it's sitting in. Here is the whole journey, in order — and then the return trip, which behaves differently than most people expect.
Stage 1 — Fiat arrives on a bank rail
However modern the platform on top, fiat still enters through the rails banks have always used, and the rail sets the tempo for everything after it:
- SEPA (euros, EEA) — standard credit transfers usually settle same business day; SEPA Instant settles in seconds where both banks support it.
- Faster Payments (pounds, UK) — typically near-instant, around the clock.
- ACH (US dollars, domestic) — batch-based, usually same or next business day.
- SWIFT (cross-border wires) — one to three business days, sometimes more, because the payment may hop through several correspondent banks, each applying its own cut-off times and its own compliance review.
Two details cause most of the avoidable delays at this stage. The first is cut-off times: a wire instructed at 5 p.m. on Friday effectively doesn't start moving until Monday. The second is name and reference matching — if the sender's name doesn't match the account holder on file, or a required payment reference is missing, the transfer lands in an exceptions queue instead of the account. Neither is a platform problem; both are fixable by the sender.
Stage 2 — Screening decides when funds become usable
Cleared is not the same as available. Before incoming fiat can be converted, it passes through the compliance layer: sanctions and PEP screening on the sender, and transaction monitoring that compares the payment against the account's expected behaviour — the volumes, counterparties, and geographies declared at onboarding.
The important word is expected. A payment that fits the declared profile clears the checks automatically, usually in seconds. What earns a manual review is deviation: an amount far above the account's history, a first-time counterparty in a higher-risk corridor, a pattern that resembles structuring. Well-built monitoring is risk-based precisely so that the routine majority never waits behind the unusual minority.
Stage 3 — Conversion is the fast part
Once funds are cleared and screened, converting fiat to a stablecoin takes seconds. The platform sources a rate from its liquidity providers, quotes it with a short validity window, and executes on confirmation. This stage almost never causes delay — but it's where the real cost lives.
The number to compare across providers is not the headline rate but the effective cost: the gap between what you paid and the mid-market rate at that moment, plus any stated conversion fee. Two platforms advertising "great rates" can differ meaningfully once the spread is included, and on recurring volume that difference compounds into a real line item.
Stage 4 — Settlement lands on-chain
The final leg is the one people actually watch: the stablecoin arriving at its destination. Speed and cost here belong to the network, not the platform. The same USDC settles in seconds for negligible fees on a fast chain and takes noticeably longer during congestion on a busy one — so the choice of network at withdrawal is a genuine decision, not a formality.
One error at this stage is worth calling out because it's the only one in the whole pipeline that can be irreversible: sending to a wrong or incompatible address. Bank rails have recall procedures; blockchains do not. Address validation and test transactions for first-time destinations exist for exactly this reason.
The return trip: why off-ramping feels slower
Converting stablecoins back to fiat runs the same pipeline in reverse — but the experience differs, and it's worth understanding why. On the way in, the slow bank rail comes first, so by the time you're watching the platform, the waiting is mostly done. On the way out, the bank rail comes last: the crypto leg and conversion finish in seconds, and then the payout sits inside a SEPA, FPS, ACH, or SWIFT settlement window while you watch.
Receiving banks also apply their own scrutiny to incoming funds, independent of anything the sending platform does. The off-ramp isn't actually slower end to end — the waiting has simply moved to the part you can see.
Where the time actually goes
| Stage | Typical time | What causes delays |
|---|---|---|
| Bank rail in | Seconds – 3 business days | SWIFT correspondent hops; Friday cut-offs; sender name or reference mismatch |
| Screening & monitoring | Seconds – hours | Payment deviates from declared profile; verification documents out of date |
| Conversion | Seconds | Effectively never — the cost lives here, not the time |
| On-chain settlement | Seconds – minutes | Network congestion; the one irreversible risk is a wrong address |
| Bank rail out (off-ramp) | Same day – 3 business days | Rail settlement windows; receiving bank's own review of incoming funds |
Three habits that keep the pipeline fast
- Prefer local rails over SWIFT wherever a currency corridor allows it — this single choice removes the largest and least predictable delay in the system.
- Keep your verification profile current. When volumes grow or new counterparties appear, updating your declared activity before the change hits the account means monitoring sees an expected pattern instead of an anomaly.
- Send with clean details. Matching sender name, correct reference, verified destination address — the boring hygiene that keeps a transfer out of every exceptions queue along the way.
None of this makes the pipeline visible in the app, and it shouldn't have to be. But when a transfer takes longer than expected, the answer is almost always one of these five rows — and almost never the conversion itself.
This article is for general information only and is not financial, legal, or tax advice. Product availability, fees, and features depend on verification, account type, jurisdiction, and applicable regulatory requirements, and may change over time.