What Happens When a Bitcoin Transaction Gets Stuck

You are waiting on a customer's bitcoin payment. The wallet shows the transaction as "pending." An hour passes. Then two. The confirmation count stays at zero. This situation has a name: a stuck transaction. Understanding why it happens, and what your options are, helps you respond without panic and sets the right expectations with customers before it ever occurs.

How the Bitcoin Mempool Creates a Queue

Every bitcoin transaction that gets broadcast to the network lands first in something called the mempool, short for memory pool. Think of it as a waiting room. Miners pick transactions out of that waiting room and bundle them into blocks roughly every ten minutes. The catch is that each block holds a limited amount of data, so miners prioritize by fee rate, measured in satoshis per virtual byte (sat/vB). Transactions paying higher fee rates get seated first; lower-fee transactions wait longer.

Under normal conditions, the mempool clears fairly quickly. A well-sized fee means your transaction confirms in the next block or two. However, when network activity spikes, such as during a price rally, a popular NFT launch, or an automated wave of consolidation transactions, the mempool can swell to tens of thousands of pending transactions. At that point, a transaction priced at last week's average fee rate can sit for hours or days before a miner picks it up.

The fee rate a sender attaches is chosen at broadcast time, usually by the wallet software based on recent block data. If the network gets busier after the transaction is sent, that fee rate may no longer be competitive. The transaction is not lost; it is simply waiting in line behind higher-paying ones.

For a deeper look at how the confirmation process works from start to finish, see how bitcoin payments work step by step and how long a bitcoin payment takes to confirm.

What "Unconfirmed" Means for Your Business

An unconfirmed bitcoin payment carries real risk for a merchant. Until a transaction reaches at least one confirmation, it has not been settled on the blockchain. A technically sophisticated bad actor could, in some circumstances, attempt to double-spend an unconfirmed transaction by rebroadcasting a conflicting version with a higher fee. This is not common, but it is a known attack vector.

Most small-dollar in-person sales have tolerated zero-confirmation acceptance for years because the economic incentive to double-spend a $25 coffee is low and the window is short. For higher-value sales, though, the general guidance is to wait for at least one confirmation before releasing goods, and more confirmations for larger amounts.

This is why the operational question matters: when a customer's payment is unconfirmed, what do you do? The answer depends on the dollar amount, how long the transaction has been waiting, and whether your setup gives you any tools to act.

For guidance on checking payment status before you ship, see how to verify a bitcoin payment before you ship.

The Two Standard Remedies: RBF and CPFP

When a transaction stalls, there are two on-chain mechanisms that can accelerate it. Neither is exotic; both are widely supported across modern wallets and are worth knowing even if you never use them yourself.

Replace-By-Fee (RBF)

RBF allows the original sender to rebroadcast the same transaction with a higher fee rate, signaling to miners to replace the original with the updated version. For a customer whose payment is stuck, this means opening their wallet, locating the pending transaction, and choosing something like "boost" or "replace-by-fee" if their wallet supports it. The new broadcast carries a higher sat/vB rate, and miners will prefer it over the original.

From a merchant's perspective, RBF is something your customer needs to initiate. You cannot do it yourself because you did not originate the transaction. What you can do is recognize an RBF-enabled transaction (most wallets flag this) and understand that the final confirmed version may have a slightly different transaction ID than the one first shown. Your payment processor or wallet should reconcile this automatically.

Child-Pays-For-Parent (CPFP)

CPFP works from the recipient side. If you have received the unconfirmed funds in a wallet you control, you can create a new transaction spending those unconfirmed outputs. This child transaction carries a high enough fee that, when miners calculate the combined fee rate of the parent and child together, it becomes worth their while to confirm both. In effect, the child subsidizes the parent.

CPFP is more relevant for technically minded merchants running their own nodes or using non-custodial wallets with CPFP support. If you are using a managed payment processor, they typically handle fee acceleration automatically without any action on your part.

What US Merchants Should Do Operationally

When a customer's on-chain payment is stuck, a practical sequence looks like this:

Set a wait threshold first. Decide in advance how long you will wait on an unconfirmed payment for a given order size before taking action. A common pattern is 30 to 60 minutes for routine purchases and up to 24 hours for higher-value orders. Document this policy so your staff handles it consistently.

Check a block explorer. Services like mempool.space let you paste a transaction ID and see exactly where it stands: its fee rate, the current mempool fee-rate environment, and an estimated time to confirm. This takes 30 seconds and tells you whether the transaction is likely to clear in the next hour or whether it has been outpriced by the current queue.

Contact the customer. If the transaction looks genuinely stuck, reach out early. Let the customer know you can see the payment is pending and that you are monitoring it. Give them the option to bump the fee through their wallet (RBF if supported) or to wait. Most customers appreciate the transparency and most stuck transactions do eventually confirm, though "eventually" can mean days during extreme congestion.

Do not ship high-value goods on zero confirmations. This is worth stating plainly. No matter how impatient the customer or how routine the order feels, releasing inventory before any confirmation on a significant purchase is an operational risk. A 30-minute delay for one confirmation is a reasonable policy and most customers accept it once it is explained.

Use a managed processor for volume. If you process bitcoin payments regularly, a managed processor handles fee estimation, RBF monitoring, and stuck-transaction acceleration behind the scenes. Processors like BitPay use their own backend infrastructure to watch the mempool and rebroadcast or accelerate transactions without requiring merchant intervention. The tradeoff is that you are relying on their settlement timeline rather than direct blockchain confirmation, but for most retail businesses that tradeoff is acceptable.

Lightning as an Alternative for Small Payments

The stuck-transaction problem is specific to on-chain bitcoin. The Lightning Network, a second-layer payment channel protocol built on top of bitcoin, settles payments in seconds and has no mempool queue. For small-dollar transactions, especially point-of-sale situations where waiting for blockchain confirmation is impractical, Lightning is worth evaluating.

If a customer sends a Lightning payment, it either succeeds immediately or it fails and the funds return automatically to the sender, with no stuck state. The tradeoff is that Lightning requires both parties to have Lightning-capable wallets and some familiarity with the channel infrastructure.

A side-by-side comparison of the two rails is covered in on-chain vs Lightning: which bitcoin payment rail to use.

Frequently Asked Questions

Can a stuck bitcoin transaction expire or disappear?

Yes, eventually. Most nodes drop unconfirmed transactions from their mempool after 14 days (Bitcoin Core's default). When that happens, the funds effectively return to the sender's wallet because the transaction was never confirmed. The sender can then rebroadcast with a higher fee. Nothing is lost, but the payment did not go through, so you would need to invoice again or have the customer retry.

As a merchant, can I do anything to unstick a customer's payment?

If the funds are already sitting in your wallet as an unconfirmed incoming transaction, you may be able to use CPFP to accelerate it by spending those unconfirmed outputs at a high fee rate. Not all wallets support this. If you are using a managed processor, contact their support team; many have manual acceleration tools. If you have no control over the originating wallet, the main lever is asking the customer to use RBF from their end.

How do I know if a transaction is actually stuck versus just slow?

Look up the transaction on a mempool explorer. If the current median fee rate on the network is significantly higher than what the transaction is paying, it is likely stuck. If the transaction fee is within range and the mempool is just deep, it may confirm within hours. The explorer will usually show an estimated confirmation time based on current conditions.

Does a stuck transaction affect my IRS or tax reporting?

For US tax purposes, a bitcoin payment is generally recognized when it is received and under your control. An unconfirmed transaction has not settled, so it is reasonable to treat it as unconfirmed for income purposes until it clears. Tax treatment of cryptocurrency transactions is an area where rules have been evolving; confirm current IRS guidance and speak with a qualified tax professional for your specific situation.

Do payment processors protect me from stuck transactions automatically?

It depends on the processor. Managed processors like BitPay typically absorb the mempool risk on your behalf: you get notified of payment and the processor handles confirmation monitoring and, in some cases, fee acceleration. Check your processor's documentation for exactly how they handle unconfirmed payments and what their confirmation threshold is before funds are credited to your account.