The number of Bitcoin confirmations required for a BTC exchange is set by the receiving service, not by a universal Bitcoin rule. One platform may process a deposit after the first block confirmation, while another may require several confirmations based on the amount, operational risk controls, and the specific exchange direction. The decisive number is the confirmation threshold displayed for the current order or deposit address.
A Bitcoin transaction receives its first confirmation when miners include it in a block. Each block added afterward increases the confirmation count and makes replacing that transaction’s history progressively harder. Bitcoin’s developer documentation uses one, two, and six confirmations as risk reference points, but these examples do not require every exchange to adopt the same threshold. [1]
What the Confirmation Count Means
| Observed state | What it means | What to do |
|---|---|---|
| Not broadcast | The wallet has not produced a verifiable transaction ID, or the transaction has not reached the network. | Do not wait for exchange crediting yet. Check the sending wallet. |
| 0 confirmations | The transaction has been broadcast but is not included in a block. | Monitor the transaction ID and do not create a duplicate payment unless the wallet or service provides a documented recovery procedure. |
| 1 confirmation | The transaction is included in a block. Double-spend risk is lower than at zero confirmations, but the exchange may still be waiting. | Compare the observed count with the order’s required threshold. |
| Several confirmations | Additional blocks have been built on top of the block containing the transaction. | Continue waiting if the required number has not been reached. |
| Required threshold reached | The blockchain condition specified by the service has been met. | Check whether the order status has changed to credited, processing, completed, or an equivalent state. |
Confirmations measure blocks, not guaranteed elapsed time. A transaction can remain unconfirmed when demand for block space is high or when its fee rate is less competitive than other pending transactions. Even after the required number is reached, internal processing or a compliance review may delay the next order state. Reaching the threshold is therefore a necessary blockchain milestone, but it may not be the only condition for completion.
State Map: From Exchange Request to Verified Result
- Task: exchange BTC.
- Transition condition: the selected order explicitly accepts BTC deposits through the Bitcoin network.
- Check: confirm the asset, exchange direction, and currently available network before creating the order.
- Stop if it does not match: BTC on Bitcoin is not interchangeable with a tokenized or wrapped version of BTC on another blockchain.
- Input data: deposit instructions received.
- Transition condition: the order shows a complete BTC address, an amount or permitted amount range, and the applicable order terms.
- Check: compare the address displayed in the order with the address entered in the wallet. Review the first and last characters and, where possible, the entire string.
- Stop if it does not match: the address changed unexpectedly, came from an email or message rather than the active order, or does not appear valid in the wallet.
- Verification: amount, fee, and confirmation rule reviewed.
- Transition condition: the amount expected at the destination remains compatible with the order after considering how the wallet deducts the miner fee.
- Check: determine whether the wallet adds the fee separately or subtracts it from the entered amount. Record the required confirmation count shown for the order.
- Stop if it does not match: the destination would receive less BTC than required, the quote or order has expired, or the confirmation requirement is not visible or understood.
- Action: BTC transaction authorized.
- Transition condition: the asset, Bitcoin network, address, amount, fee treatment, and active order details have all been checked.
- Check: perform one final comparison before approving the wallet transaction.
- Stop if it does not match: any field differs from the verified order instructions. After authorization and broadcast, the sender cannot rely on a conventional payment cancellation process.
- Waiting: transaction broadcast.
- Transition condition: the wallet provides a transaction ID, or txid.
- Check: open the txid in a reputable Bitcoin block explorer and verify the receiving address, transferred amount, and confirmation count. A transaction ID is the identifier used to locate transaction data; Bitcoin Core also exposes confirmation information for transactions. [2]
- Stop and diagnose if it does not match: the explorer shows another destination, an unexpected amount, a conflict, or no transaction after the wallet claims it was broadcast.
- Confirmed result: required confirmations reached.
- Transition condition: the explorer count is equal to or greater than the threshold specified by the exchange order.
- Check: verify that the service has recognized the deposit and moved the order to the appropriate processing or completed state.
- Stop and contact support if it does not match: the threshold has been reached but the deposit remains unrecognized, the order has expired, or the credited amount differs from the blockchain record.
- Recovery scenario: route did not complete as expected.
- Transition condition: enough information exists to identify the failed state without sending another transaction.
- Check: preserve the order identifier, txid, address, amount, wallet status, screenshots of the order terms, and the observed confirmation count.
- Stop: do not resend BTC, disclose a seed phrase, or follow recovery instructions from unsolicited messages. Recovery may depend on technical feasibility and compliance checks and cannot be guaranteed.
Checks to Complete Before Sending BTC
Asset and network
Select BTC and the Bitcoin network specified by the receiving order. The ticker alone is not enough: some interfaces also list tokenized BTC products on other networks. Sending through a network that the recipient does not support can prevent automatic crediting and may make recovery difficult or impossible. Current pairs, networks, and exchange directions should be checked before each operation rather than inferred from an earlier order.
Deposit address and additional fields
A standard on-chain BTC transfer is routed to a Bitcoin address. Do not add a Memo or Tag merely because other cryptocurrencies use one. If the receiving interface displays any additional identifier or special instruction, pause and confirm how it must be used before sending. Clipboard malware, substituted QR codes, and phishing pages can replace a legitimate address, so compare the final wallet screen with the active order rather than with a copied message.
Amount and miner fee
The Bitcoin miner fee is paid to process the network transaction; it is distinct from any exchange pricing or service fee shown in the order. Wallets differ in how they present this deduction. If the order expects a defined deposit amount, check the actual recipient output rather than assuming the entered amount will arrive unchanged. Do not invent a fee manually without understanding the wallet’s fee estimator or replacement options.
Required confirmations
Use the order-specific requirement. Six confirmations are often cited in Bitcoin technical material as a conservative reference for payments exposed to greater double-spend risk, while one confirmation already means inclusion in a block. This is a security model, not a promise that a particular exchange will always demand six confirmations. [1]
- Record the required count before sending.
- Track the txid independently in a Bitcoin explorer.
- Compare block confirmations, not only the wallet’s estimated completion time.
- Keep the order open until its instructions and validity conditions are clear.
- Expect additional processing if the operation enters a compliance review.
Once these checks match the intended route, open the exchange form and verify the current BTC direction and deposit requirements.
How to Diagnose a Delayed or Incorrect Transaction
| What you observe | Likely state | Safe next step |
|---|---|---|
| No txid in the wallet | The transaction may not have been created or broadcast. | Check the wallet’s transaction history and connection status. Do not assume that funds were sent. |
| Txid exists but an explorer cannot find it | Broadcast may have failed, propagation may be limited, or the identifier may be incorrect. | Copy the txid directly from the wallet and check again. Use only wallet-supported broadcast or recovery procedures. |
| Transaction is visible with 0 confirmations | It is pending in the network and has not entered a block. | Review the wallet’s fee and replacement status. Avoid creating a separate duplicate transfer. |
| Confirmations are below the exchange threshold | The blockchain requirement is not yet satisfied. | Continue monitoring. The exchange cannot count blocks that have not yet been added. |
| Threshold reached but order is still pending | Internal recognition, order validation, amount matching, or compliance processing may remain. | Confirm the address and amount, then provide the order ID and txid through the service’s official support channel. |
| Wrong address or unsupported network | The transaction no longer follows the intended route. | Stop sending additional funds and contact the actual recipient or service. Blockchain confirmation does not guarantee recoverability. |
| Explorer shows a conflicting or replaced transaction | The original unconfirmed transaction may no longer be the transaction expected to confirm. | Identify the transaction currently recognized by the wallet and provide both identifiers to support if an order is involved. |
If support review is necessary, share public transaction data and order details only through an official channel. A legitimate diagnostic process does not require disclosure of a wallet seed phrase or private key. Rules and compliance requirements can differ by exchange direction and country, so current conditions should be confirmed before the order is created.
When the BTC Exchange Route Is Complete
The route is technically complete when the correct transaction is included in the Bitcoin blockchain, reaches the confirmation threshold stated in the order, is recognized by the receiving service, and the order displays its confirmed outcome. A wallet’s “sent” status alone is not sufficient, and a high confirmation count cannot correct a wrong address, wrong network, or mismatched amount.
Some uncertainty may remain after the blockchain threshold is reached: the service may still need to match the deposit, complete internal processing, or request information under its compliance procedures. Keep the txid and order identifier until the final amount and order status are verifiable. Do not send a second payment merely because the first transaction is delayed.