Plan a Bitcoin send from address to confirmation

Confirm the recipient's Bitcoin route

Get the current receiving instructions from the destination wallet or service. For an ordinary onchain Bitcoin payment, both sides need to support the Bitcoin network. Check the complete address against those instructions and confirm the intended amount. If the recipient is an exchange, review its deposit minimum and confirmation requirement as well.

A withdrawal menu can show several routes beside a familiar asset label. Choose the route the recipient actually accepts. A cheaper option is useful only when it reaches the correct destination in the expected form. Resolve any network mismatch before preparing the transaction.

Budget for the payment and its fee

Bitcoin network fees are paid in BTC. The fee reflects the transaction's virtual size and its fee rate; it is not simply a percentage of the amount being sent. Bitcoin Core's fee estimation documentation describes confirmation targets as estimates based on virtual transaction size.

Review the recipient amount, fee, and total debit together. If the wallet offers an option to subtract the fee from the payment, establish what the recipient will actually receive. For an exchange withdrawal, distinguish the service's stated charge from any blockchain fee visible later. Use the current preview instead of assuming that a previous transfer establishes today's cost.

Understand what you are approving

A Bitcoin wallet can select several spendable outputs to fund one payment. Surplus value can return to the wallet as change, so an explorer's transaction total may exceed the intended payment amount. Check the recipient output and rely on the wallet's review to identify change before signing.

For a new destination, consider a small test when the cost and deposit rules make it practical. Confirm actual receipt before preparing the rest, and review the later address and amount again. Read the guide to Bitcoin fees, confirmations and change for examples of how the transaction fits together.

Follow the transaction through to receipt

Save the transaction ID after submission and check it on the intended Bitcoin network. Broadcasting and block inclusion are different events. Confirmations accumulate after inclusion, and their timing varies. Bitcoin.org's payment guidance explains why an unconfirmed payment should not be treated as final and why block timing is unpredictable.

For a hosted deposit, compare the blockchain status with the service's own crediting rule. If it remains pending, the pending transfer troubleshooting guide helps separate the sender's withdrawal status, the network record, and the recipient's processing. Avoid creating a second independent payment while the first outcome remains unclear.

Common Bitcoin send questions

Can a higher fee guarantee arrival?

No. A fee target can affect the likelihood of earlier block inclusion, but it cannot guarantee a deadline or correct an incompatible destination. Account for the recipient's processing requirements too, and check that timing expectations are realistic before sending.

What should I keep for a transfer query?

Keep the transaction ID, selected network, receiving address, recipient amount, and the destination instructions you used. If a wallet replaces an unconfirmed transaction, retain the new ID alongside the old one. Share only relevant public transfer details through the provider's established support channel; recovery phrases and private keys are never needed for a routine status check.