Crypto payments · English

Track a Bitcoin replacement transaction without double-paying

Follow an opt-in replace-by-fee payment from the original transaction ID to its replacement, with fee, change and recipient checks that reduce duplicate-payment risk.

September 17, 2026SignalBet Guide Editorial TeamQuality gate 100/100
Mr Boss in official black-and-gold SignalBet artwork, accompanying “Track a Bitcoin replacement transaction without double-paying”.
01

Treat replacement as one payment history

When an unconfirmed Bitcoin transaction is replaceable, a wallet may create a higher-fee replacement. The new transaction identifier can make the first payment appear to vanish, but sending a separate ordinary transaction can create a true duplicate. Keep both identifiers in one lineage.

Bitcoin Core's bumpfee documentation says the command replaces an opt-in RBF wallet transaction, retains its inputs, increases the fee and may reduce or create change while returning a new transaction identifier. Keep the original and replacement transaction identifiers in one lineage instead of treating them as unrelated payments. For Verify opt-in status, preserve original txid beside replaceable status and do not close the question until wallet is independently checked. Confirm which identifier the recipient or service currently recognizes.

Verify opt-in status

A fee bump is designed for a wallet transaction that was marked replaceable. Check the wallet's transaction detail and record the explicit status. Record whether replaceability was enabled before considering a fee change. A useful replacement lineage sheet links broadcast time to confirmations, names the origin of Capture the original economics and explains why recipient amount is still relevant. The working row is original txid, replaceable status, wallet, broadcast time and confirmations; its heading is verify opt-in status, and its place in the larger record is replacement lineage sheet.

Do not assume every unconfirmed transaction can be replaced. Compare the old fee, new fee and any reduced change output in the same unit. When replaceable status and confirmations disagree, retain both observations, recheck Verify opt-in status and postpone any decision that depends on Capture the original economics. Check the wallet's transaction detail and record the explicit status. For this verify opt-in status decision, compare original txid, replaceable status, wallet, broadcast time and confirmations with replacement lineage sheet and retain the dated mismatch instead of forcing agreement.

Capture the original economics

The initial transaction has a recipient amount, fee, input set and change output. Record those values before asking the wallet to construct anything new. Compare the old fee, new fee and any reduced change output in the same unit. When replaceable status and confirmations disagree, retain both observations, recheck Verify opt-in status and postpone any decision that depends on Capture the original economics. The working row is recipient amount, original fee, inputs, change and fee rate; its heading is capture the original economics, and its place in the larger record is replacement lineage sheet.

Without the baseline, a reduced change output can look like a changed payment amount. Do not create a second ordinary payment to solve an uncertain first payment. The reviewer should reproduce wallet from broadcast time, identify the unit attached to original txid and see the collection time for recipient amount. Record those values before asking the wallet to construct anything new. For this capture the original economics decision, compare recipient amount, original fee, inputs, change and fee rate with replacement lineage sheet and retain the dated mismatch instead of forcing agreement.

Review the proposed replacement

The replacement normally pays an additional fee and includes all original inputs. Compare recipient outputs line by line and identify where the extra fee comes from. Do not create a second ordinary payment to solve an uncertain first payment. The reviewer should reproduce wallet from broadcast time, identify the unit attached to original txid and see the collection time for recipient amount. The working row is new fee, new rate, recipient outputs, change reduction and added inputs; its heading is review the proposed replacement, and its place in the larger record is replacement lineage sheet.

Reject a proposal that changes an intended recipient or amount without explanation. Confirm which identifier the recipient or service currently recognizes. Finish the row by stating who will verify Capture the original economics, which source governs replaceable status and what change would make confirmations obsolete. Compare recipient outputs line by line and identify where the extra fee comes from. For this review the proposed replacement decision, compare new fee, new rate, recipient outputs, change reduction and added inputs with replacement lineage sheet and retain the dated mismatch instead of forcing agreement.

Link both identifiers

Explorers and recipients may temporarily show different states for the original and replacement. Store the new txid as a child of the original and note which one is active. Confirm which identifier the recipient or service currently recognizes. Finish the row by stating who will verify Capture the original economics, which source governs replaceable status and what change would make confirmations obsolete. The working row is parent txid, replacement txid, mempool status, confirmation and observation time; its heading is link both identifiers, and its place in the larger record is replacement lineage sheet.

Do not describe the replaced identifier as a second lost payment. Keep the original and replacement transaction identifiers in one lineage instead of treating them as unrelated payments. For Verify opt-in status, preserve original txid beside replaceable status and do not close the question until wallet is independently checked. Store the new txid as a child of the original and note which one is active. For this link both identifiers decision, compare parent txid, replacement txid, mempool status, confirmation and observation time with replacement lineage sheet and retain the dated mismatch instead of forcing agreement.

Reconcile the receiving account

A service may credit only after its own confirmation policy and transaction matching. Send the current identifier and chronology through authenticated support if credit remains missing. Keep the original and replacement transaction identifiers in one lineage instead of treating them as unrelated payments. For Verify opt-in status, preserve original txid beside replaceable status and do not close the question until wallet is independently checked. The working row is service reference, accepted txid, confirmation count, credit status and ticket; its heading is reconcile the receiving account, and its place in the larger record is replacement lineage sheet.

Do not broadcast another payment while the replacement lineage is unresolved. Record whether replaceability was enabled before considering a fee change. A useful replacement lineage sheet links broadcast time to confirmations, names the origin of Capture the original economics and explains why recipient amount is still relevant. Send the current identifier and chronology through authenticated support if credit remains missing. For this reconcile the receiving account decision, compare service reference, accepted txid, confirmation count, credit status and ticket with replacement lineage sheet and retain the dated mismatch instead of forcing agreement.

Read the bumpfee fields before changing a fee

The Bitcoin Core reference explains the input, fee, change and identifier behavior of a replacement transaction. The reviewer should reproduce wallet from broadcast time, identify the unit attached to original txid and see the collection time for recipient amount. Record whether replaceability was enabled before considering a fee change. Use SignalBet guides only to clarify Verify opt-in status or original txid; the named source remains responsible for replaceable status and wallet.

It does not operate a user's wallet, guarantee mempool acceptance or define a receiving service's credit policy. Finish the row by stating who will verify Capture the original economics, which source governs replaceable status and what change would make confirmations obsolete. Compare the old fee, new fee and any reduced change output in the same unit. That limit keeps broadcast time distinct from confirmations and prevents Capture the original economics from being stretched into a claim about recipient amount.

Resolve the lineage before taking another action

A complete sheet identifies the active transaction, preserved recipient output and final confirmation or service response. A useful replacement lineage sheet links broadcast time to confirmations, names the origin of Capture the original economics and explains why recipient amount is still relevant. Do not create a second ordinary payment to solve an uncertain first payment. A completed replacement lineage sheet should leave Verify opt-in status traceable, wallet bounded and Capture the original economics ready for its next dated review.

Fee pressure is not a reason to gamble with a larger deposit; pause until the first transfer and its cost are fully understood. Adults 18+ who meet local law should treat gambling as optional entertainment rather than income or debt recovery, protect essential money, set cash and time limits before play, never borrow or chase losses, and use the responsible-play centre for blocking, time-out, self-exclusion and confidential support. When replaceable status and confirmations disagree, retain both observations, recheck Verify opt-in status and postpone any decision that depends on Capture the original economics. Confirm which identifier the recipient or service currently recognizes.

Source: Bitcoin Core bumpfee RPC documentation ↗