Crypto Payment Stuck as Unconfirmed for Hours: What to Check
If a crypto payment your business is waiting for has been stuck at "unconfirmed" for more than a few hours, the most common cause is that the sender used a low transaction fee, and network congestion is delaying confirmation. The transaction is not lost yet, but you need to identify whether it will confirm eventually or whether it will drop from the mempool entirely.
Check the Transaction Status on a Block Explorer
Copy the transaction hash from your payment processor or wallet interface. Paste it into a public block explorer for the relevant blockchain (for Bitcoin, use mempool.space or blockstream.info; for Ethereum, use etherscan.io). The explorer will show the current fee rate, the number of confirmations (usually zero for a stuck transaction), and the transaction's status in the mempool.
If the explorer shows the transaction as "unconfirmed" with a low fee (e.g., below 5 sat/vB on Bitcoin), it is competing for block space. If the fee is extremely low - below 1 sat/vB - the transaction may never confirm unless the sender replaces it.
Evaluate the Chances of Confirmation
Transactions with fees at or above the current network's "minimum relay fee" will eventually confirm when network traffic clears, but that can take hours or days. On Bitcoin, fees below the mempool's "low priority" threshold (typically under 2 - 3 sat/vB during normal conditions) may never confirm because miners prioritize higher-fee transactions.
For Ethereum, check the gas price in gwei. If the gas price is below 20 - 30 gwei during high congestion, the transaction may remain pending indefinitely. The sender can cancel or replace it by sending a new transaction with a higher gas price.
What the Sender Needs to Do
You cannot speed up a stuck transaction from your side. Only the sender can take action. Contact them and ask if they used a wallet that supports Replace-by-Fee (RBF). RBF allows the sender to broadcast a new version of the same transaction with a higher fee. On Bitcoin, if the original transaction had RBF enabled (look for "RBF: yes" on the block explorer), the sender can increase the fee.
If RBF was not enabled, the sender may need to wait for the transaction to drop from the mempool (typically after 2 - 14 days, depending on node settings) and then resend it with a higher fee. Alternatively, they can use a "child-pays-for-parent" (CPFP) strategy: spend the unconfirmed output to a new address with a high fee, incentivizing miners to confirm both transactions.
When the transaction might be lost
A transaction is not truly lost until it is removed from the mempool of most nodes. If the sender's wallet does not support RBF and the fee was below the current minimum relay fee, the transaction will eventually be discarded. After that, the funds return to the sender's wallet automatically - no one else can claim them.
If the transaction has been pending for more than 72 hours with no movement and the fee is extremely low (e.g., 1 sat/vB or less on Bitcoin), it is likely abandoned. Advise the sender to check their wallet for a "cancel" or "replace" option. If none exists, they may need to import the private key into a wallet that allows fee bumping.
What your business should do internally
Do not ship goods or provide services based on an unconfirmed transaction. Unconfirmed payments can be double-spent or reversed. Your payment processor or BTCPay Server should already be configured to require a certain number of confirmations (typically 1 for small payments, 3 - 6 for larger ones). If you are manually checking, wait for at least one confirmation before considering the payment complete.
If you use a hosted payment processor, check their policy on stuck transactions. Some processors have a "force confirm" feature after a set timeout, but this is rare and should not be relied upon.
Prevent future stuck payments
Add a note to your invoice page or checkout flow recommending that customers use wallets with RBF enabled and set fees at or above the current network average. For Bitcoin, suggest they check mempool.space for the "high priority" fee rate before sending. For Ethereum, recommend gas prices above 30 gwei during normal conditions.
If you process many payments, consider switching to the Lightning Network for Bitcoin or a Layer 2 solution for Ethereum. These networks offer near-instant confirmation and negligible fees, eliminating the stuck-transaction problem entirely. However, they require separate setup and liquidity management, which is covered elsewhere on this site under Lightning payment rails.
Final check before escalation
If a transaction remains unconfirmed after 48 hours and the sender has not acted, ask them to provide the transaction ID and confirm that the amount and address are correct. A small number of stuck transactions are caused by the sender accidentally using a low fee on a large transaction that requires higher priority. In rare cases, the transaction may be stuck because the sender's wallet is not broadcasting it properly - using a different wallet or a block explorer's "broadcast" feature can fix this.
If none of these steps resolve the issue after a week, the transaction is effectively dead. The sender will need to resend the payment. Consider waiving any fees or delays on your side as a courtesy, since the problem is not the sender's fault if they followed your recommended fee guidelines.
Not financial advice. unidexai.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.