Bitcoin Payment Stuck Unconfirmed? Here's How to Fix It
Bitcoin Payment Stuck Unconfirmed? Here's How to Fix It
BitDeals.com is reader-supported. We may earn a commission when you buy through links on our site, at no extra cost to you. It never changes what we recommend.
You paid. Your wallet says "sent." The block explorer shows the transaction exists. And forty minutes later, the merchant still has not shipped anything, because the transaction has zero confirmations and looks like it might sit there all night.
This is the second most common way a Bitcoin payment goes wrong, after paying the wrong amount. It is also the most alarming, because it looks like your money vanished. It did not. Here is what is actually happening and what you can do about it.
Why it's stuck: you underbid an auction
Nothing is broken. Your transaction is in the mempool — the waiting room where broadcast transactions sit before a miner picks them up.
Miners have limited space in each block and choose what to include by fee rate, measured in satoshis per virtual byte (sat/vB). It is a continuous auction. If you attached a fee of 3 sat/vB and the market is clearing at 25 sat/vB, your transaction is simply not competitive, and it will keep not being competitive until either demand falls or you change the bid.
That is the whole mechanism. Your transaction can sit unconfirmed for hours or days if the fee is below what miners are taking (Breet). Eventually it may confirm when the mempool clears overnight or on a weekend — or it may be dropped from mempools after about two weeks and the coins reappear in your wallet as if you had never sent them.
Two more things worth knowing before you touch anything:
Your coins are not lost. They are either going to confirm or come back. There is no third outcome.
Do not send the payment again. If the first transaction confirms later, you have paid twice, and recovering the second payment is a support ticket, not a click.
Step one: look before you act
Open a block explorer, paste your transaction ID (txid), and check two things: the fee rate you actually paid, and the current mempool clearing rate. Mempool visualizers show you which fee tiers are confirming right now.
If your fee is only slightly below the clearing rate and the mempool is emptying, waiting is often the correct move and costs nothing. If you are far below it, or the backlog is growing, you need to bump the fee. Here are the two ways to do that.
Fix 1: Replace-by-Fee (RBF)
RBF replaces the original transaction with a new version that spends the same inputs and attaches a higher fee. Miners take the more profitable version; the original is discarded (BloFin).
When you can use it: only if the original transaction was flagged as replaceable when it was broadcast, and only if you are the sender. Most modern wallets set the RBF flag by default, but not all do — and once a transaction is broadcast without it, you cannot add it retroactively.
How it usually looks: find the pending transaction in your wallet, choose "Bump fee," "Increase fee," or "Replace by fee," and set a rate at or slightly above the current clearing level. Wallets with RBF support include Electrum, Bitcoin Core, Green and Phoenix.
One thing to watch: the replacement changes the transaction ID. If you already gave the merchant a txid, send them the new one, or their system may keep watching a transaction that will never confirm.
RBF is the cleaner fix and the one to reach for first.
Fix 2: Child Pays for Parent (CPFP)
If RBF is unavailable — the transaction was not flagged, or you are the receiver waiting on someone else's slow payment — CPFP is the fallback.
You create a second transaction (the "child") that spends an output of the stuck one (the "parent"), and you attach a fee large enough to make the combined package attractive. Miners evaluate the pair together, so to collect the child's fat fee they have to confirm the parent as well (Bitcoin Insider).
When to use it: when RBF is not an option, or when you are the recipient and want an incoming payment to land. This is the reason CPFP exists — it is the only fee bump available to the person on the receiving end.
What it costs: more than RBF. You are paying for two transactions' worth of block space instead of one, and the child's fee has to cover the parent's shortfall on top of its own. Wallets with CPFP support include Electrum and Sparrow.
The catch: you need a spendable output from the stuck transaction. If you sent the full balance to the merchant with no change output back to yourself, you have nothing to spend, and CPFP is off the table for you — though the merchant can still use it on their end.
Fix 3: transaction accelerators (last resort)
Some mining pools, including ViaBTC and F2Pool, run accelerator services that will include a submitted transaction in a block they mine. Some offer a limited free tier; most charge.
Treat these as a genuine last resort. Free tiers are rate-limited and often full. Paid ones can cost more than the fee bump would have. And they only help if the pool actually mines a block soon, which is probabilistic. Use them when RBF and CPFP are both unavailable and you need the payment through today.
What to tell the merchant
Do this in parallel with the fix, not after it.
Email the merchant with the invoice or order number and the transaction ID. Tell them the payment was broadcast, is unconfirmed due to network fees, and that you are bumping the fee. That converts you from "customer who did not pay" into "customer whose payment is in flight," which is a completely different conversation.
Two mechanics matter here. First, the fifteen-minute rate window most Bitcoin checkouts use governs when the payment must be broadcast, not when it must confirm — a payment sent inside the window at a locked rate is generally treated as made on time even if the confirmation takes hours. Second, if you have to replace the transaction with RBF, send the new txid, because the merchant's processor is watching the old one.
If the transaction ultimately drops out of the mempool and the coins return to your wallet, the order simply was not paid. Generate a fresh invoice and start over. That is annoying, not costly.
Preventing it: four habits
Let the wallet set the fee, and take the "priority" tier when it matters. Manually lowballing the fee to save $1.40 on a $300 purchase is how most stuck payments happen. On a time-sensitive merchant invoice, pay the fast rate.
Check the mempool before you send. Ten seconds on a mempool visualizer tells you whether tonight is a 5 sat/vB night or a 60 sat/vB night. Non-urgent transfers are much cheaper on a quiet weekend.
Use a wallet with RBF on by default. This is the single highest-value setting in this entire article, because it turns a stuck payment from a crisis into a two-click fix. Check your wallet's settings now, while nothing is broken.
Consolidate your UTXOs when fees are cheap. A wallet holding many small received amounts has to combine several of them to make a payment, which makes the transaction physically larger and therefore more expensive at any given sat/vB rate. Doing that consolidation deliberately on a quiet night is far better than discovering it mid-checkout with a countdown running. This is the same reasoning behind our advice on paying from a hardware wallet — cold storage accumulates exactly this kind of fragmentation.
The structural fix
The pattern behind almost every failed Bitcoin payment we have written about — expired invoices, underpayments, and now stuck transactions — is the same: people are trying to pay a merchant directly out of storage, on the merchant's clock.
The arrangement that removes all three failure modes is boring and it works. Keep savings in cold storage. Keep a small spending balance in a hot wallet you top up deliberately, when you are not under a timer, from a wallet with sensible fee defaults and RBF enabled. Then paying a merchant is a thirty-second operation from a wallet designed for exactly that, with a fee bump available if the network gets busy.
Moving your own coins between your own wallets is not a taxable disposal in the US, so this costs you nothing at tax time and makes your records cleaner, not messier.
If the cold-storage half of that is not set up yet, that is the piece to fix first. We have reviewed most of the field — Ledger and Trezor are where we send people first. [INSERT AFFILIATE LINK]
Get the BitDeals Digest. One email, a few times a week: what moved Bitcoin, what it means if you spend it, and the deals actually worth taking. No price predictions, no hype. [Subscribe here.]
Nothing in this article is investment or tax advice. Network conditions change constantly — check current fee rates before sending.
Comments