Bitcoin Swap Deposit Unconfirmed? Fee Rates, RBF and CPFP Explained (2026)
Why is my Bitcoin swap deposit still unconfirmed?
Almost always because the fee rate was too low for how busy the network was when you sent it. Bitcoin miners choose which transactions to put in the next block, and they prefer the ones that pay more per unit of size. A swap service like the one Swappr uses can usually see your deposit as soon as it's broadcast, but it waits for confirmations before it sends your coins, so a low-fee deposit leaves the whole swap waiting. The good news: an unconfirmed transaction isn't lost. You can usually speed it up with Replace-by-Fee (RBF) or Child-Pays-for-Parent (CPFP), or simply wait. This guide explains how to check what's happening, which fix fits your wallet, and what to watch for with the swap order itself.
Educational content, not financial advice. Swappr doesn't control Bitcoin fees or confirmation times. Check your own order's status before taking action.
Step 1: confirm the transaction exists
Copy the transaction ID (TXID) from your wallet and look it up in a block explorer. Our guide to tracking a swap with the TXID shows what to look for. You'll see one of three things:
- Unconfirmed, with a fee rate. The transaction is in the mempool, waiting. Compare its fee rate (sat/vB) with what the explorer currently suggests for the next few blocks.
- Not found. Your wallet may not have broadcast it, or it dropped out of the mempool. Don't send a second deposit yet; check the wallet first.
- Confirmed. The delay is on the swap side, not the network. Check your order status and our guide on how long a crypto swap takes.
Why the fee rate matters
Bitcoin fees are based on the size of the transaction, not the amount sent, and the fee per byte rises with demand for block space. When many people want to transact, transactions with a low rate get pushed back. A deposit sent with a "low" or "economy" setting during a busy period can wait hours or longer.
It also won't wait forever in most nodes' memory. In Bitcoin Core, the default mempool expiry is 336 hours (14 days); after that, nodes using the default drop the transaction and the coins become spendable again in your wallet. Other nodes can have different settings, so treat that as a rough upper bound, not a promise.
Fix 1: Replace-by-Fee (RBF)
RBF lets you broadcast a new version of the same transaction that pays a higher fee. Bitcoin Core's FAQ describes opt-in RBF as allowing transactions to be flagged as replaceable until they are confirmed in a block. The replacement pays a higher fee, which makes it more attractive to miners. Most wallets show it as "Bump fee" or "Speed up".
Historically, a transaction had to signal opt-in RBF to be replaceable. Bitcoin Core 28.0 changed the default of the mempoolfullrbf setting to on, so nodes running default settings now accept replacements whether or not the original signalled. Your wallet still decides whether it offers the button.
Important for swaps: keep the same destination and amount. A fee bump that changes the recipient address or reduces the amount sent creates a different payment, and the swap service may not match it to your order.
Fix 2: Child-Pays-for-Parent (CPFP)
If your wallet doesn't support RBF, you can sometimes spend the unconfirmed transaction's change output in a new transaction with a high fee. Miners look at the combined fee of the parent and child, so including the child means including the parent too. You need a change output that belongs to you; you can't use the deposit output, because it now belongs to the swap service's address. CPFP costs more in total, since you pay for two transactions.
Fix 3: wait, but watch the order
If the fee is only slightly low, waiting for a quieter period is often cheapest. The catch is the swap order. Swap services quote rates for a limited window, and fixed-rate orders in particular can expire if the deposit isn't received or confirmed in time. Our guide to fixed vs float rate swaps explains the difference. If the order expires, the deposit is normally handled through the service's refund or continue options; see what to do after an expired order.
Never send a second deposit to the same order to "push" the first one. Two payments can create two problems.
How to avoid a stuck deposit next time
- Check the current suggested fee rates before you send, especially during market spikes.
- Use a wallet that supports RBF, and leave it enabled.
- Avoid sending from many tiny inputs; consolidate when fees are low.
- Paste the deposit address once, then verify the first and last characters.
- Keep the TXID and order ID together until the swap completes.
What the swap service sees while you wait
From the service's side, your deposit goes through three stages: broadcast (visible in the mempool), confirmed (included in a block), and credited (enough confirmations for the service's rules). Only after the last stage does the outgoing transaction to your receiving address get sent. That's why an order page can show "deposit detected" for a long time without progress. If you bump the fee with RBF, the TXID changes, because it's a new transaction. Note the new TXID and keep it alongside the order ID; if you ever need to contact support, the replacement TXID is the one that matters.
If your wallet created the deposit from an exchange account rather than your own wallet, you usually can't use RBF or CPFP at all, because the exchange controls the transaction. In that case the exchange's support is the only route, which is one reason we suggest thinking twice before sending a swap deposit from an exchange.
FAQ
Can a stuck Bitcoin transaction be cancelled?
Not directly, but with RBF you can replace it with a version that pays you back instead, as long as the original hasn't confirmed. If it confirms first, the replacement is invalid.
Will Swappr see my deposit before it confirms?
The service can usually see a broadcast transaction, but it waits for confirmations before sending your coins, so the swap stays pending.
How long can an unconfirmed transaction stay pending?
It depends on fees and network demand. Bitcoin Core nodes with default settings drop it from their mempool after 336 hours (14 days).
Is CPFP or RBF cheaper?
RBF is usually cheaper because you pay for one transaction. CPFP adds a second transaction, but it works when your wallet can't replace the first.
Does bumping the fee change my transaction ID?
Yes. An RBF replacement is a new transaction with a new TXID. Keep the new one with your order ID, because it's the one the swap service will see confirmed. If support asks for proof of payment, send that replacement TXID.
Sources
- Bitcoin Core: Opt-in RBF FAQ (checked 2026-10-30)
- Bitcoin Core 28.0 release notes: mempoolfullrbf default (checked 2026-10-30)
- Bitcoin Core source: default mempool expiry (336 hours) (checked 2026-10-30)
- Bitcoin Developer Guide: transaction fees and change (checked 2026-10-30)