Selling bitcoin and getting paid by SEPA transfer

Between the moment you click "sell" and the moment money shows up on your statement, six distinct things happen. Each has its own clock, and none of them depends on the other five. That is why two identical sales can be paid eight minutes apart or nineteen hours apart without anything having gone wrong.

This article walks through those six steps in order, and what makes each one take time.

1. The quote, and what it locks

A quote starts from the BTC/EUR mid-market rate — the midpoint between the best bid and the best ask on reference venues. It is not a rate anyone can actually trade at; it is a reference point. Every platform then applies a spread. What separates providers is not whether that spread exists, it is whether it is shown as its own line or folded into the rate.

On Fiatside the quote shows four lines: the mid-market rate applied, the network cost, our margin, and the fee of the payout rail you picked. Those lines sum to exactly the gap between the gross amount you deposit and the net you receive. Each line is documented on the fee schedule.

The part that matters most is the lock duration. For bitcoin the rate is frozen for fifteen minutes from order creation. That number is not arbitrary: it matches the typical time for a transaction sent with sensible fees to get its first confirmation. For a stablecoin such as USDT the window is thirty minutes, because the price risk during the wait is structurally smaller.

If your deposit lands after the window expires nothing is lost: the order is re-quoted at the current rate and you have to accept the new amount before any payout leaves. That mechanism is covered in Headline rate versus effective rate.

2. The on-chain deposit

You get a deposit address dedicated to that order. On Bitcoin no extra data is required: no memo, no tag, no reference. That simplicity is specific to Bitcoin and most UTXO chains; it does not exist on XRP or TON, where a forgotten memo turns a deposit into an incident, as described in The missing memo.

What you control at this step is the transaction fee you attach to your send. An underpriced transaction can sit for hours in the mempool — the queue of transactions not yet included in a block. It is not lost, it is waiting. But it often waits past the rate lock window.

Two practical consequences:

• Do not use your wallet's lowest fee setting for a send you want confirmed within fifteen minutes.
• If your wallet supports RBF (replace-by-fee), you can raise the fee on an already broadcast transaction. That is the only way to speed up a Bitcoin send after the fact.

3. Confirmations

A Bitcoin transaction is treated as settled once a certain number of blocks are stacked on top of it. We require two confirmations for BTC. A Bitcoin block appears on average every ten minutes, so two confirmations mean roughly twenty minutes on average — with wide variance, because the interval between blocks follows an exponential distribution: waiting thirty minutes for one block is unremarkable, and so is seeing three in five minutes.

Why two and not one? Because a transaction included in a block can still disappear if that block is orphaned, that is, if a competing chain of the same height wins. It is rare, but it happens. Each additional confirmation makes that scenario exponentially less likely. The confirmation count required per network is published on each asset page, for example Sell bitcoin, and the term itself is defined in the glossary.

4. Compliance checks

While confirmations accumulate, the order goes through regulatory checks. Two separate things happen there.

First, identity verification, whose depth depends on your cumulative amount over a rolling period. The exact tiers are published on the identity verification page. A first small sale generally requires fewer documents than a several-thousand-euro one.

Second, analysis of the on-chain origin of funds. Addresses that received funds directly from a sanctioned service, a mixer or an identified theft trigger a manual review. This is not a commercial decision: a provider converting digital assets into legal tender carries its own liability here. The full policy is on the AML policy page.

5. Sending the transfer

Once confirmations are in and checks have passed, the transfer goes out. At this point two very different rails share the everyday name "SEPA transfer".

SEPA Instant (the SCT Inst scheme) settles in seconds, 24 hours a day, seven days a week, bank holidays included. There is no cut-off. The practical limit is the per-payment ceiling applied by the beneficiary's bank, often 100,000 EUR but sometimes far lower depending on the institution.

Classic SEPA (the SCT scheme) works in batches, on business days only. An order issued after the cut-off goes out in the next business day's batch. An order issued on a Saturday goes out on Monday. That mechanism is detailed in Why your SEPA transfer arrives tomorrow.

Since January 2025 the European instant payments regulation has required euro-area payment service providers to be able to receive instant transfers, and since October 2025 to be able to send them. In practice nearly every euro-area IBAN can therefore receive instantly — but an IBAN outside the euro area, for instance a Swiss or British euro account, remains outside the scope of that obligation.

6. The credit on your account

The last link is not ours. Between the beneficiary bank receiving the funds and your app showing them, a few minutes can pass. Some banks display the amount immediately, others wait for their own refresh cycle.

Two causes of rejection at this stage, both avoidable:

• The beneficiary name does not match. Since verification of payee became general in the euro area, a mismatch between the name entered and the actual account holder raises an alert, and sometimes a rejection. The name must match your verified ID.
• The IBAN is syntactically valid but inactive. An IBAN check digit can be verified mathematically, which catches typos, but not a closed account. A transfer to a closed account bounces back within a few business days.

The honest total

Here are the orders of magnitude, assuming sensible transaction fees and no manual review.

| Step | SEPA Instant | Classic SEPA | | --- | --- | --- | | Quote and order creation | < 1 min | < 1 min | | First Bitcoin confirmation | ~10 min | ~10 min | | Second confirmation | ~10 min | ~10 min | | Automated checks | < 1 min | < 1 min | | Sending and settlement | seconds | next business batch | | Realistic total | 20 to 30 minutes | 20 min to 1 business day |

The dominant factor is therefore not the blockchain: it is the rail you choose and the hour you place the order. A Friday 6pm deposit paid over classic SEPA arrives on Monday. The same deposit paid over SEPA Instant arrives at 6:25pm on Friday.

What actually stretches the timing

In decreasing order of frequency, among operations that take longer than expected:

1. Transaction fees set too low. By far the leading cause. The transaction sits in the mempool and misses the rate window.
2. An incomplete verification file. A blurry ID photo or a proof of address older than three months restarts the cycle.
3. An IBAN belonging to someone else. Third-party payouts are not accepted: the destination account must be in the verified seller's name.
4. A manual source-of-funds review. Rare, but it adds anywhere from a few hours to a few business days depending on the documents requested.

Going further

The complete guide to selling crypto covers these steps for every asset and every rail, not just BTC to SEPA. If your question is about cost rather than timing, Headline rate versus effective rate explains how to compare two fee schedules without reading the wrong number. And if you wonder why some popular payment methods appear nowhere on this site, the answer is in Why some payment methods cannot receive funds.