Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Bitcoin basics · Entry 176

How to receive Bitcoin: addresses, amounts and arrival checks

AI-assisted research · separate automated verificationCorrections

Theme
Bitcoin basics
Sources
9 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for How to receive Bitcoin: addresses, amounts and arrival checks
FactDetailSource
ShareA receiving address or supported payment request[1]
Keep secretKeys, seed and required recovery secrets[4]
CheckNetwork, destination, amount and chain status[3]
01

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.

02

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.

03

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.

Direct answers

Questions people ask

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.

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.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Share: A receiving address or supported payment request

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Keep secret: Keys, seed and required recovery secrets

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Check: Network, destination, amount and chain status

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

On the Send and check a Bitcoin payment path · Learn next: Bitcoin payment requests and QR codes: what a scan actually tells you

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Bitcoin for IndividualsBitcoin.org

    Receiving and sending payments across compatible wallet applications.

    Locator: Mobile payments made easy; Works everywhere, anytime · Retrieved: 2026-10-02T18:53:53.645ZOpen source
  2. TransactionsBitcoin 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 · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.759ZOpen source
  3. Payment ProcessingBitcoin developer documentation

    Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated.

    Locator: Requesting Payments; Verifying Payment; Issuing Refunds · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.958ZOpen source
  4. Securing your walletBitcoin.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.659ZOpen source
  5. WalletsBitcoin 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 · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.756ZOpen source
  6. Trezor’s Trusted DisplayTrezor

    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.900ZOpen source
  7. URI SchemeBitcoin 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 · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.108ZOpen source
  8. InvoicesBTCPay 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.741ZOpen source
  9. The payment cycleLightning 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 · Version / scope: Pinned Lightning Labs documentation revision; LND/Loop implementation scope · Retrieved: 2026-10-02T18:53:57.281ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/