Bitcoin Core finalizepsbt RPC: Completion and Extraction Guide

This guide explains Bitcoin Core finalizepsbt RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Pre-finalisation intent

Decode and approve the base64 input before finalising. Verify the frozen unsigned transaction, UTXOs, scripts, sighash modes, partial signatures and fee bounds. Finalisation should never be the first point at which a human sees recipients or total wallet impact.

Finalizer role

The RPC converts enough partial data into final scriptSig and final scriptWitness fields for inputs it can complete. It does not invent missing signatures or authorisation. An input left incomplete must remain visible and block extraction or broadcast.

Extract control

extract defaults true. When the transaction is complete, that setting returns raw network hex rather than a PSBT; false keeps a finalised PSBT. Select the mode explicitly in automation so a default cannot unexpectedly move secret-bearing metadata or raw transaction data across the wrong boundary.

Result branching

Require complete true before treating the result as ready for further validation. Expect psbt when not extracted and hex when extracted. Validate presence and mutual expectations of these fields and reject ambiguous, missing or version-mismatched response shapes.

Final transaction review

Decode extracted hex and compare every input, sequence, output, amount, locktime and transaction identifier lineage with the approved unsigned transaction. Recalculate fee and virtual size and run local policy acceptance checks before handing it to a separately authorised broadcaster.

Metadata after extraction

Extraction intentionally strips the workflow down to a network transaction. Preserve an encrypted audit copy or hashes of the approved PSBT according to policy before extraction, because derivation, signer and proprietary metadata will not travel with the broadcast transaction.

How specialists test it

Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.

Conclusion

finalizepsbt transforms enough signing data into final scripts and optionally raw transaction hex. Safety depends on explicit result branching, final decoded-intent review and a separate broadcast authority.