The short answer
To receive Bitcoin, generate a fresh supported payment request in a wallet you control or an authorized custodial account. To send, independently verify the destination, network, amount and fee before signing. Test with a small amount when appropriate, then verify actual receipt. Bitcoin payments usually cannot be canceled once confirmed.
First identify the payment rail
An on-chain Bitcoin payment uses a Bitcoin address or compatible payment URI. A Lightning payment generally uses an invoice or compatible Lightning payment request. The two may look similar in a QR code, but their protocols and settlement paths are different.
Before beginning, confirm which rail the recipient accepts, whether the wallet supports it, and whether the provider imposes deposit limits or special instructions. A QR code is a container for data, not proof that the destination belongs to your intended recipient.
- Do not paste an on-chain address into a Lightning-only field.
- Use a fresh address where supported for privacy.
- Check which service will credit the payment and when.
Receiving a payment safely
Open the receiving wallet or eligible account using a verified app. Create the payment request from inside it, rather than reusing one copied from a chat. Give the sender only the public receiving information needed for the payment; never share your secret recovery phrase.
On-chain incoming transactions may appear as unconfirmed before entering a valid block. Different recipients apply different confirmation policies. A custodial provider may credit later than the underlying blockchain. For Lightning, confirm the invoice was settled inside the receiving wallet.
- Check the receiving network and account status.
- Confirm the exact amount or invoice denomination.
- Record the reference and eventual confirmation.
Sending a payment carefully
Copy or scan the receiver's request, then verify its beginning and end and, where possible, the entire address on an independent trusted display. Be wary of clipboard malware that replaces a copied address. Check the amount unit: BTC, sats and dollars are different displays of value.
A wallet might estimate the network fee for you. Before approval, confirm the BTC amount going to the recipient, the fee, and the total debit. Larger payments benefit from a small initial transfer to verify the path, followed by an independent review before sending the remainder.
- Do not approve an unfamiliar address because a support agent asks.
- Avoid sharing screenshots containing sensitive transaction details.
- A test transfer reduces risk but does not replace final address verification.
What to do while waiting
For an on-chain payment, a transaction ID lets you inspect its confirmation status in a block explorer or through your own node. A mempool entry is not the same thing as a confirmed payment. Unconfirmed transactions may be delayed, replaced under applicable policies or dropped from a particular node's mempool.
For Lightning, use both wallet and merchant confirmation screens. If an invoice expires or a route fails, avoid blindly paying the same request again. Follow the receiving service's retry instructions to prevent accidental duplicate payments.
- Never use only a sender screenshot as proof of merchant settlement.
- Keep an invoice or transaction reference for support.
- Understand refund policies before buying nonrefundable goods.
Privacy and recordkeeping matter
A new on-chain address helps reduce obvious linkage between payments, but public transaction data can still be analyzed. Exchanges and merchants may associate addresses with a person's identity. Treat receiving addresses as public, not anonymous.
In the United States, spending Bitcoin may also have tax consequences if the coins appreciated. Preserve dates, quantities, dollar values and any fees alongside personal or business receipts without exposing wallet secrets.
- Use new receiving addresses where practical.
- Reconcile invoices to actual wallet activity.
- Separate payment records from recovery materials.
Three checks before Send
Use this original comparison to turn the explanation into a practical choice. These scenarios illustrate different constraints; the right answer depends on circumstances and current provider rules.
| Situation | What matters |
|---|---|
| Destination | Verify address or invoice and correct Bitcoin payment rail. |
| Amount and total fee | Read BTC or sats, recipient amount and total debit carefully. |
| Receipt | Confirm the actual recipient system has credited payment. |
Frequently asked questions
Can I reverse a Bitcoin transaction sent to the wrong address?
Confirmed Bitcoin transfers normally cannot be reversed by a central operator. Recovery depends on cooperation from the actual recipient, if identifiable.
How long does it take to receive Bitcoin?
On-chain blocks arrive unpredictably, averaging about ten minutes; providers may require more confirmations. Lightning usually aims for faster settlement.
Can I share my Bitcoin address publicly?
An address is not a secret key, but public sharing can expose payment and privacy information.
Sources and further verification
These sources support the protocol, operational, or regulatory foundations described above. Provider policies and laws can change; check their current versions before acting.
Editorial education, not personalized investment, legal, security, or tax advice. No purchase of Bitcoin is required to learn about it.