Bitcoin transaction pending? Fees, RBF and CPFP explained

A pending Bitcoin transaction is not automatically a lost payment. First distinguish a withdrawal that your exchange has not broadcast from an on-chain transaction waiting for confirmation. Then check whether your wallet offers a supported fee-bump option. Sending another payment blindly can create a second payment rather than fix the first.

Bitcoin mainnet · Source-checked October 11, 2026 · Educational guide based on documentation, not a live wallet test. Lightning payments and other networks are outside this guide.

First: whose “pending” message are you reading?

An exchange withdrawal screen and the Bitcoin network describe different stages. If your service has not supplied a transaction ID, check its withdrawal status through its official app or support channel. You cannot increase the network fee of a transaction you do not control. If it supplies an ID, compare the network status with the app’s status before deciding what to do.

An explorer can help you inspect an ID, but it is a third party: your lookup can expose your interest in that transaction. A missing result from one explorer alone does not establish that a payment was cancelled. Never provide recovery words, a private key or a passphrase to inspect a transaction.

Fee rate is not the amount of bitcoin you sent

Bitcoin fees depend on transaction size and competition for block space. Wallets commonly express the rate in satoshis per virtual byte (sat/vB). A transfer’s value is not enough to calculate its fee. Your wallet’s estimated confirmation time is an estimate, not a deadline. See Trezor’s fee documentation.

RBF: replace the unconfirmed transaction

Replace-by-fee creates a competing version that spends overlapping inputs and offers a higher fee. It is not a second independent payment. For example, Trezor Suite documents a Speed up option for pending Bitcoin sends. Availability and requirements depend on your wallet and the transaction; do not assume every pending transfer has this button.

Use your wallet’s official procedure and review the new fee and transaction details before signing. A recipient may need the replacement transaction ID to track the payment. Paying more does not guarantee inclusion by a particular time. If the transaction is already confirmed, RBF is no longer a way to change it.

CPFP: spend an output to help both transactions confirm

Child-pays-for-parent creates a new transaction that spends an output of the unconfirmed parent. The child offers enough fee to make the combined package attractive to miners. Someone must control an eligible output and have software that supports the operation; being the recipient of a custodial exchange deposit does not necessarily give you that control. Bitcoin Optech explains the mechanism.

The key distinction: RBF replaces a transaction; CPFP adds a dependent transaction. With CPFP, assess the fee and size of the package, not just the child’s headline rate. Neither technique restores a lost wallet backup or reverses a confirmed theft.

A short decision checklist

1. Identify the network and whether the payment was broadcast.
2. Check the transaction’s current status, not just an old notification.
3. If unconfirmed, identify who controls it and which fee-bump options the wallet actually supports.
4. Review the full additional cost before choosing urgency over waiting.
5. If confirmed but not credited, check the receiving service’s requirements rather than sending again.

A slow payment and lost signing keys are different problems. If your device or backup is missing, use our hardware-wallet recovery triage instead. Do not reset a device or share a backup to resolve a fee delay.

No paid accelerator recommendation, affiliate link or guaranteed confirmation time. This guide explains the choices; it does not initiate transactions or ask for wallet information.