# How to receive Bitcoin: addresses, amounts and arrival checks

To receive an on-chain Bitcoin payment, give the payer a receiving address from the correct wallet and network, plus the agreed amount. Share the address or payment request, never spending secrets. The wallet can be offline while the network records a payment. Check the actual output and confirmation status afterward; a screenshot or sender notification is not the payment itself.

Evidence: [Bitcoin for Individuals](https://bitcoin.org/en/bitcoin-for-individuals); [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet)

Canonical: https://degreesofsatoshi.com/encyclopedia/how-to-receive-bitcoin/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Share:** A receiving address or supported payment request ([Bitcoin for Individuals](https://bitcoin.org/en/bitcoin-for-individuals))
- **Keep secret:** Keys, seed and required recovery secrets ([Securing your wallet](https://bitcoin.org/en/secure-your-wallet))
- **Check:** Network, destination, amount and chain status ([Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html))

## Create a destination you can recognize

Open the intended wallet account and choose its receiving function. A fresh address helps distinguish receipts. If a hardware wallet supports address verification, compare the application’s address with the device display before sharing it. This checks the wallet’s own destination; it does not authenticate an outside person.

On-chain addresses and Lightning requests are different payment instructions. Agree on the route before copying anything. A service account may also impose deposit policies separate from Bitcoin’s transaction rules.

Evidence: [Wallets](https://developer.bitcoin.org/devguide/wallets.html); [Trezor’s Trusted Display](https://trezor.io/guides/trezor-devices/trezor-fundamentals/trezor-s-trusted-display-verify-every-address-on-your-device); [URI Scheme](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0321.mediawiki); [Invoices](https://docs.btcpayserver.org/Users/invoices/)

## Follow one payment through the ledger

Suppose you request 50,000 satoshis. The relevant check is an output paying 50,000 satoshis to the script represented by your address. The payer may also create change, so the total transaction output value need not equal your receipt.

A payment appearing as pending has not yet been included in the observed chain. After inclusion, the containing block counts as the first confirmation. The appropriate acceptance policy depends on the payment’s circumstances; a fixed count is not an unconditional guarantee.

Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html)

## Receiving and noticing are separate events

An on-chain output can be created while your phone or signing device is off. When the wallet reconnects and discovers the transaction, its display catches up. The backup must still preserve the keys and any policy information needed to spend.

If an explorer shows the expected payment but the wallet does not, investigate synchronization, account selection and discovery. Do not disclose a seed to someone claiming they need it to release an incoming payment.

Evidence: [Wallets](https://developer.bitcoin.org/devguide/wallets.html); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet)

## Questions

### Does the sender need my private key?

No. The payer needs a supported destination and the agreed amount. Your private keys or recovery phrase are spending authority and are unnecessary for creating an ordinary payment to you.

Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet)

### Does receiving an on-chain payment require my device to be online?

No. The network can record an output while the wallet is offline. Your application needs a current chain view to discover and display it later; Lightning receiving has different operational requirements.

Evidence: [Wallets](https://developer.bitcoin.org/devguide/wallets.html); [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md); [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md)

## Claims and scope

### how-to-receive-bitcoin-quick-answer

To receive an on-chain Bitcoin payment, give the payer a receiving address from the correct wallet and network, plus the agreed amount. Share the address or payment request, never spending secrets. The wallet can be offline while the network records a payment. Check the actual output and confirmation status afterward; a screenshot or sender notification is not the payment itself.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### how-to-receive-bitcoin-fact-share

Share: A receiving address or supported payment request

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### how-to-receive-bitcoin-fact-keep-secret

Keep secret: Keys, seed and required recovery secrets

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### how-to-receive-bitcoin-fact-check

Check: Network, destination, amount and chain status

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Bitcoin for Individuals](https://bitcoin.org/en/bitcoin-for-individuals) — Bitcoin.org. Receiving and sending payments across compatible wallet applications. Locator: Mobile payments made easy; Works everywhere, anytime. Retrieved: 2026-10-02T18:53:53.645Z.
- [Transactions](https://developer.bitcoin.org/devguide/transactions.html) — Bitcoin developer documentation. Inputs, outputs, authorization, change, coinbase exceptions and fee accounting. Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse. Retrieved: 2026-10-02T18:53:53.759Z.
- [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html) — Bitcoin developer documentation. Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated. Locator: Requesting Payments; Verifying Payment; Issuing Refunds. Retrieved: 2026-10-02T18:53:53.958Z.
- [Securing your wallet](https://bitcoin.org/en/secure-your-wallet) — Bitcoin.org. Backup scope, online exposure, offline signing, custody and software update practices. Locator: Be careful with online services; Backup your wallet; Encrypt your wallet; Offline wallet for savings; Hardware wallets; Keep your software up to date. Retrieved: 2026-10-02T18:53:53.659Z.
- [Wallets](https://developer.bitcoin.org/devguide/wallets.html) — Bitcoin developer documentation. Wallet types, generated keys, deterministic wallets and offline signing. Locator: Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets. Retrieved: 2026-10-02T18:53:53.756Z.
- [Trezor’s Trusted Display](https://trezor.io/guides/trezor-devices/trezor-fundamentals/trezor-s-trusted-display-verify-every-address-on-your-device) — Trezor. Manufacturer explanation of device display checks and the limits of a host-computer screen. Locator: Trusted display article: on-device verification steps and limits of what the device verifies. Retrieved: 2026-10-02T18:53:56.900Z.
- [URI Scheme](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0321.mediawiki) — Bitcoin Improvement Proposals. Successor payment URI scheme and wallet-dependent payment instructions. Locator: General rules for handling (important!); General Format; Query Keys; Transfer amount; Forward compatibility; Backward compatibility. Retrieved: 2026-10-02T18:53:54.108Z.
- [Invoices](https://docs.btcpayserver.org/Users/invoices/) — BTCPay Server. Checkout states, paid-late/over/partial exceptions and confirmations as distinct events. Locator: Invoice statuses; Invoice details; Refunding an invoice; Archiving invoices. Retrieved: 2026-10-02T18:53:56.741Z.
- [The payment cycle](https://raw.githubusercontent.com/lightninglabs/docs.lightning.engineering/0456e1627b2579ac18108cb921fe609f87c8b009/the-lightning-network/multihop-payments/the-payment-cycle.md) — Lightning Labs. Invoice-first Lightning flow, routes and settlement preimages. Locator: Introduction: sender and receiver interaction; Create invoice; Make the payment; Check the payment; Other payment types. Retrieved: 2026-10-02T18:53:57.281Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “How to receive Bitcoin: addresses, amounts and arrival checks.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/how-to-receive-bitcoin/