Knowing how to send Bitcoin safely matters because a Bitcoin transaction cannot be undone. Once it is confirmed, no bank, support team or exchange can pull it back. The good news is that almost every loss comes from a handful of avoidable mistakes: a wrong address, a fee set too low, or a rushed copy and paste. This guide walks through the checks that prevent them, in the order you meet them when you press send.
1. Know the address you are sending to
Bitcoin has several address formats. Modern wallets can send to all of them, but they differ in how much space the transaction takes, and therefore in fees when spending from them.
| Starts with | Name | Typical fee impact |
|---|---|---|
bc1q… | Native SegWit (Bech32) | Low; the default in most wallets |
bc1p… | Taproot (Bech32m) | Low, similar to native SegWit |
3… | Nested SegWit or multisig (P2SH) | Medium |
1… | Legacy (P2PKH) | Highest when spending from it |
The fee you pay depends mostly on the inputs you spend, so holding coins in a bc1 address keeps future fees down. ThinSwap accepts all four formats as a receiving address, so you can use whichever your wallet provides.
2. Check the address properly
Clipboard malware is a real threat: it watches for crypto addresses you copy and silently replaces them with the attacker’s. The fake address looks plausible at a glance.
- After pasting, compare the first and last five or six characters with the original, and a few in the middle.
- Prefer scanning a QR code or using your wallet’s address book for repeat payees.
- Never take an address from a chat message you did not expect, or from a screenshot that someone sends you.
- If you use a hardware wallet, confirm the address on the device screen, not just on your computer.
3. Choose a sensible fee
Bitcoin fees are measured in satoshis per virtual byte (sat/vB). Miners pick the transactions that pay the most per byte, so the fee you need depends on how crowded the mempool is at that moment, not on how much you send. Sending 0.001 BTC or 1 BTC can cost the same.
- Look at the current recommended rates on a mempool explorer such as
mempool.spacebefore sending. - For something urgent, choose a rate that targets the next block or two. If you can wait, a lower rate saves money.
- Be careful with very low fees during busy periods: a transaction can sit unconfirmed for hours or longer.
Replace-by-fee (RBF)
Many wallets let you send with RBF, which allows you to rebroadcast the same transaction with a higher fee if it gets stuck. If your wallet supports it, keep it enabled; it is the easiest fix for an underpaid fee. Some wallets also support child-pays-for-parent, where the receiver speeds things up by spending the unconfirmed output with a higher fee.
4. Send a test transaction for large amounts
For a new address or a large amount, send a small test first and wait until it arrives. It costs one extra fee but proves that the address is right and that the receiver can see the funds. When you send to a swap order with an exact amount, a test is not practical, so check the address even more carefully and follow the order’s instructions.
5. Understand confirmations
Bitcoin blocks arrive about every ten minutes on average, though the gap varies a lot. A transaction first appears in the mempool as unconfirmed, then gets its first confirmation when a miner includes it in a block. Each later block adds one more. Many services want between one and six confirmations before treating a payment as final. Read more in how many confirmations BTC, ETH and TRON need, and learn to track a payment yourself with how to check a transaction on a block explorer.
Sending BTC to a ThinSwap order
If you are swapping Bitcoin, for example with BTC to USDT or BTC to ETH, the process adds one important rule: send the exact amount.
- Create the order with the amount and the address where you want to receive the other coin.
- Copy the deposit address and the exact BTC amount shown, including all decimals. The decimals identify your order.
- If you are withdrawing from an exchange that deducts a fee from the amount, add that fee so the exact figure arrives.
- Set a fee rate that will confirm in reasonable time. A stuck transaction delays the whole swap.
- Keep the order page open and note the order ID.
ThinSwap watches the blockchain automatically. Your BTC is seen in the mempool first and the order shows Confirming; it is treated as received once it has one block confirmation, then moves to Sending and Completed. Your rate is locked for 30 minutes after creating the order, which is why a reasonable fee matters. If the lock expires and you had already sent, the team reviews it manually and either sends at the current rate or refunds. The quote already includes the 0.4% service fee and the network fee for the coin you receive. Orders go from 20 USD to 1,000,000 USD in BTC terms and usually complete within 5 to 30 minutes in total. You can see all Bitcoin pairs on the swap BTC page.
If you sent and the order does not show your deposit, paste your TXID on the order page so it can be matched.
Quick safety checklist
- Address checked at the start, middle and end.
- Fee chosen from the current mempool, with RBF on when possible.
- Test sent first for new, large payments.
- Exact amount used for swap orders.
- TXID saved until the payment is confirmed.
Putting your Bitcoin to use
Bitcoin is also a way to pay for big-ticket experiences. If you travel, you can rent a luxury car in Dubai with crypto and settle the booking straight from your wallet.
Frequently asked questions
What happens if I send Bitcoin to the wrong address?
Bitcoin transactions cannot be reversed. Unless the owner of that address returns the coins voluntarily, they are lost, which is why checking the address is essential.
My Bitcoin transaction is stuck. What can I do?
If you sent with replace-by-fee enabled, bump the fee from your wallet. Otherwise you may need to wait for the mempool to clear or use child-pays-for-parent if available.
How long does ThinSwap need for a BTC deposit?
ThinSwap sees your transaction in the mempool and treats it as received after one block confirmation, which is about ten minutes on average but can vary.