# Bitcoin received but missing from your wallet: what to check

A confirmed Bitcoin payment missing from a wallet display can be a discovery or synchronization problem rather than a lost payment. First match the network, destination and amount; then check the wallet’s chain progress, account and recovery settings. A visible public output does not establish that the open wallet holds its spending keys. Do not share a seed with an explorer or support stranger.

Evidence: [Wallets](https://developer.bitcoin.org/devguide/wallets.html); [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/); [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Securing your wallet](https://bitcoin.org/en/secure-your-wallet)

Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-not-showing-in-wallet/
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

- **First comparison:** Exact destination and network ([Transactions](https://developer.bitcoin.org/devguide/transactions.html); [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/))
- **Discovery:** An address gap can hide later used addresses ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Multi-Account Hierarchy for Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0044.mediawiki))
- **Authority:** Seeing an output is different from signing it ([Wallets](https://developer.bitcoin.org/devguide/wallets.html))

## Establish which payment is missing

Inspect the recipient output, not just the transaction’s total. Confirm you are viewing the expected network and account. A wallet can display pending, trusted, immature or watch-only balances separately, so one screen may not equal all value associated with its addresses.

Suppose an explorer shows 40,000 satoshis to the expected script at a recorded block. That proves a historical receipt in that chain view, not that the output is still unspent or that your current application can authorize it.

Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [getbalances RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/getbalances/)

## Compare chain progress before changing recovery data

A local node still processing older blocks may not have reached the payment. Core exposes block height, header height and an estimated verification progress. A wallet rescan searches available local blocks for relevant transactions; it does not recreate a missing key.

Check the wallet’s documented rescan and synchronization procedure. On a pruned node, old block bodies may need to be obtained again before a historical scan can succeed.

Evidence: [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/); [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/); [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp); [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md)

## Check account derivation and the discovery window

A correct-looking mnemonic can still be used with the wrong passphrase, derivation path, address type or account. BIP-39 normalizes its mnemonic and passphrase before deriving a seed; a different normalized passphrase gives another wallet rather than a useful wrong-wallet warning.

BIP-44 discovery stops after a defined unused-address gap. A later used address can be missed if addresses were generated outside the normal discovery pattern. Investigate with the wallet’s documented settings and known public addresses, not by uploading recovery secrets.

Evidence: [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki); [Mnemonic code for generating deterministic keys](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0039.mediawiki); [Multi-Account Hierarchy for Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0044.mediawiki); [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)

## Questions

### Does a zero balance after recovery mean the bitcoin is gone?

No. An incorrect account, derivation convention, normalized passphrase or incomplete address search can show a different or incomplete wallet. Compare known receiving addresses and transaction records before reaching that conclusion.

Evidence: [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki); [Mnemonic code for generating deterministic keys](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0039.mediawiki); [Multi-Account Hierarchy for Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0044.mediawiki)

### Will a blockchain rescan recover a lost seed?

No. Rescanning finds transactions relevant to key or script information already available to the wallet. It cannot derive missing spending secrets from the public chain.

Evidence: [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/); [Wallets](https://developer.bitcoin.org/devguide/wallets.html)

## Claims and scope

### bitcoin-payment-not-showing-in-wallet-quick-answer

A confirmed Bitcoin payment missing from a wallet display can be a discovery or synchronization problem rather than a lost payment. First match the network, destination and amount; then check the wallet’s chain progress, account and recovery settings. A visible public output does not establish that the open wallet holds its spending keys. Do not share a seed with an explorer or support stranger.

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

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

### bitcoin-payment-not-showing-in-wallet-fact-first-comparison

First comparison: Exact destination and network

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

### bitcoin-payment-not-showing-in-wallet-fact-discovery

Discovery: An address gap can hide later used addresses

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

### bitcoin-payment-not-showing-in-wallet-fact-authority

Authority: Seeing an output is different from signing it

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

## Sources

- [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.
- [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/) — Bitcoin Core. Network identity and sync-status fields; progress is an estimate. Locator: Result: chain, blocks, headers, verificationprogress, initialblockdownload. Retrieved: 2026-10-02T18:53:55.851Z.
- [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) — Electrum. Electrum-specific sweep/import distinctions, seed recovery scope and address discovery. Locator: Does Electrum trust servers?; Can I import private keys from other Bitcoin clients?; Can I sweep private keys from other Bitcoin clients?; What is the gap limit?; How do I upgrade Electrum?. Retrieved: 2026-10-02T18:53:56.378Z.
- [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.
- [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.
- [Multi-Account Hierarchy for Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0044.mediawiki) — Bitcoin Improvement Proposals. Hardened account paths and external-chain discovery gap rule. Locator: Path levels; Account discovery; Address gap limit. Retrieved: 2026-10-02T18:53:54.097Z.
- [getbalances RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/getbalances/) — Bitcoin Core. Wallet balances are divided by trust and spendability-related categories. Locator: Result: mine, watchonly, trusted, untrusted_pending, immature. Retrieved: 2026-10-02T18:53:55.000Z.
- [rescanblockchain RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/rescanblockchain/) — Bitcoin Core. Rescan local blocks for wallet-related transactions within a height range. Locator: Description; Arguments; Result. Retrieved: 2026-10-02T18:53:55.698Z.
- [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp) — Bitcoin Core. Definitions of reindex/chainstate rebuild and node configuration switches. Locator: SetupServerArgs: assumevalid, reindex, reindex-chainstate, prune, listen, server; prune/reindex-chainstate compatibility check. Retrieved: 2026-10-02T18:53:55.958Z.
- [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) — Bitcoin Core. Wallet, block, chainstate and index files have different recovery purposes. Locator: Data directory location and chain-specific paths; Data directory layout: blocks/, chainstate/, wallets/; Multi-wallet environment and backupwallet guidance. Retrieved: 2026-10-02T18:53:55.926Z.
- [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) — Bitcoin Improvement Proposals. Deterministic key derivation, backup scope and public/private child derivation. Locator: Motivation; Extended keys; Security. Retrieved: 2026-10-02T18:53:54.013Z.
- [Mnemonic code for generating deterministic keys](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0039.mediawiki) — Bitcoin Improvement Proposals. Entropy and checksum table, intended computer-generated randomness and NFKD seed derivation. Locator: Generating the mnemonic; From mnemonic to seed. Retrieved: 2026-10-02T18:53:54.120Z.

## Revision history

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

## Cite this entry

Degrees of Satoshi editorial project. “Bitcoin received but missing from your wallet: what to check.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-not-showing-in-wallet/