Use this Foundation Passport balance troubleshooting page when Bitcoin balances, transaction history, or receiving addresses do not appear as expected in Envoy after transfer, restore, update, or pairing.
Independent wallet security guidance. This site is not Foundation Passport.
Foundation Passport help topics
Wallet security
Quick issue summary
Ledger and Trezor support teams should never ask for a recovery phrase, seed phrase, private key, or remote access to a wallet.
Recently Reported Issues
A Foundation Passport balance not showing problem is often caused by Bitcoin account sync delay, wrong account or address type, pending transaction, passphrase context, restore mismatch, or stale Envoy display state.
Common wallet topics include Foundation Passport balance issue, Bitcoin balance not showing, missing transaction, wrong account, address type mismatch, app sync delay, or balance missing after restore.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
If funds look missing after restore, check recovery and account context safely.
OpenIf balances changed after update, check Envoy sync and pairing state.
OpenIf Envoy cannot see Passport, solve detection before balance checks.
OpenIf Envoy cannot refresh through the paired wallet flow, start with connection checks.
OpenFake Foundation Passport recovery helpers often claim they can reveal missing Bitcoin.
OpenReturn to Foundation Passport support for broader balance and app help.
OpenReport non-private Bitcoin account and app symptoms to PhraseWallet.
OpenEnvoy app troubleshooting is safest when you separate display, sync, device, firmware, and recovery phrase concerns before changing wallet settings. Use official Foundation Passport support links for device-specific instructions.
Use these checks to separate ordinary setup friction from wallet safety risk before you reset, restore, reinstall, or open wallet support portals.
Use a data-capable cable, confirm computer permissions, avoid untrusted browser prompts, and check whether the official app recognizes the device before restoring anything.
Handle firmware updates only through verified official software. A firmware prompt should not require typing seed words into a website, chat, or support form.
Zero balance or missing transactions can come from the wrong account, network, passphrase, derivation path, sync delay, or exchange withdrawal still pending.
Keep the phrase offline and private. Do not photograph it, paste it into support, or use a recovery check page from an ad, email, DM, or search result.
Read the device screen carefully before approving. If the destination, network, fee, or contract request is unexpected, reject and investigate first.
Avoid remote access, paid recovery, messaging-app helpers, fake live chat pages, and anyone asking to be added to your wallet or computer.
Start with the most common causes before resetting the wallet, restoring from a recovery phrase, or trusting a support message.
Step 1
Compare the expected receiving address and transaction status with the active Envoy Bitcoin account before changing wallet settings.
Step 2
Review selected wallet, account, address type, and passphrase context. A different setup can show a valid but empty wallet view.
Step 3
Restart Envoy, allow sync to finish, and avoid reinstalling, resetting, or restoring before backup readiness is clear.
Step 4
If funds appear but transactions cannot sign, use QR signing troubleshooting instead of repeating balance checks.
Check selected wallet, Bitcoin account, address, sync status, transaction status, and whether a watch-only view or paired hardware wallet is active.
If Passport signs for a different address set, review passphrase, account path, and restore context without sharing recovery words.
Do not approve unexpected signatures or enter seed words while trying to make a missing balance appear.
Expected flow
A zero balance often reflects display, network, account, sync, passphrase, or restore context rather than a final conclusion about funds. Work from account discovery to address verification before restore or reset steps.
Check the coin, network, account type, public address, and Envoy app sync state.
If the wallet was restored, add or rediscover accounts before judging the balance screen.
A different recovery phrase, hidden wallet, passphrase, account type, or derivation path can show a different address set.
Blockchain indexing, token lists, or app refresh state can lag after firmware updates, restores, or network changes.
Use official help with public details and screenshots only, never recovery words or private keys.
Experiences may vary depending on wallet brand, device state, app version, network congestion, firmware status, and how the wallet was originally backed up.
What users commonly report: Some restores initially show empty wallets until the correct network, account path, passphrase context, or token/account view is selected.
For official Foundation Passport help, downloads, updates, or contact options, use Foundation Passport's official portal and verified official channels. This page helps you prepare safe, non-private context before opening support portals.
No legitimate wallet guidance should need your recovery phrase.
A recovery phrase controls wallet restoration. Treat it as private self-custody information and review how phrases work before using any wallet.
Community reports
Foundation Passport troubleshooting reports often involve Envoy pairing, QR signing, firmware prompts, Bitcoin account display, recovery planning, and fake support warnings. These examples avoid private wallet data and focus on the support pattern.
These examples are informational and reflect common user-reported wallet issues. Never share your recovery phrase, seed phrase, private keys, PIN, or wallet backup with anyone. Official wallet support should never ask for your recovery phrase.
“Foundation Passport shows an empty or delayed balance after the app or firmware update.”
Users often report temporary balance delays after firmware or app updates until the device reconnects, account discovery runs, and the correct network or token view refreshes.
“The restore finished, but Foundation Passport is showing different addresses or no expected funds.”
Some restores initially show empty wallets until the right account type, passphrase context, derivation path, network, or imported account view is selected.
“Foundation Passport QR signing stopped working after an app update or reconnect.”
QR-signing problems commonly involve app pairing records, camera focus, unsigned transaction QR content, firmware validation, signed QR broadcast, or a network mismatch.
“A support message said it could fix Foundation Passport if I shared my seed phrase or screen.”
Fake support often appears during update, restore, missing-balance, and QR-signing stress. No legitimate wallet support flow should ask for recovery words, private keys, PINs, or remote access.
Report wallet issue
Submit a non-secret wallet problem for moderated review and safer routing. PhraseWallet is independent and this is not official wallet support or emergency recovery assistance.
Never enter your recovery phrase, private key, password, PIN, or payment details.
Common wallet issues
Use these maintained support paths to move from a symptom to the right setup, recovery, troubleshooting, or security help without sharing private wallet data.
Related problems
If this page is close but not exact, check these nearby support topics so the next step matches the failure pattern.
Use the Foundation Passport support hub for Envoy pairing, QR signing, firmware, recovery, balance, and fake support warning paths.
Open helpPSBT scan direction, camera focus, firmware state, and transaction review can block Foundation Passport signing.
Open helpAvoid cloned downloads, seed phrase validators, remote access helpers, and messages asking for private wallet data.
Open helpOfficial wallet support should never ask for your recovery phrase, seed phrase, private keys, PIN, wallet backup, screen sharing, or remote access. Verify downloads, QR tools, and update prompts on the official wallet site before acting.
FAQ
Common causes include wrong Bitcoin account, address type mismatch, app sync delay, pending transaction, restore mismatch, or passphrase context.
Not always. Check the public address, transaction status, selected account, and restore context before concluding funds moved.
No. Balance visibility troubleshooting should not require recovery words, private keys, PIN, passwords, or remote access.
Public transaction hash if you are comfortable, receiving address context, Envoy version if known, device screen state, and error text. Never include seed words.
Use official Foundation Passport support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.