Use this Foundation Passport support page when Envoy cannot detect the hardware wallet, pairing does not complete, or Passport disappears during setup or signing.
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 wallet not detected problem is commonly a pairing record, camera permission, wrong QR screen, firmware state, locked device, or wrong Bitcoin wallet context issue.
Common wallet topics include Foundation Passport wallet not detected, Envoy recognition problem, pairing record issue, device prompt problem, QR pairing issue, or fake Foundation Passport app warning.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
Use broader connection checks if detection is one part of the problem.
OpenIf detection works but signing does not, focus on QR and PSBT flow.
OpenIf Passport is detected but funds are missing, troubleshoot account and address display.
OpenFirmware state can affect whether Envoy recognizes the device.
OpenDetection and pairing should not require seed phrase entry.
OpenReturn to Foundation Passport support for broader troubleshooting help.
OpenReport non-private Envoy and Passport detection 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
Check the app source and official Foundation access path before pairing. Fake apps and setup pages can look normal until they ask for seed words.
Step 2
Detection can fail when Envoy expects a pairing QR but Passport is showing a signing QR, setup prompt, firmware screen, or account confirmation.
Step 3
Allow camera permission, restart Envoy, unlock Passport, and refresh stale pairing attempts only when you understand the effect.
Step 4
If Envoy detects the wallet but the Bitcoin balance looks wrong, use balance troubleshooting instead of repeating setup.
Confirm app version, active wallet, camera access, selected Bitcoin account, and whether the account is watch-only, imported, or paired to Passport.
Charge and unlock the device, review the current screen, and follow device prompts without entering the recovery phrase online.
If detection stopped after an app or firmware update, retry verified pairing before resetting or restoring the wallet.
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 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.
“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.
“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 blocked camera permission, stale pairing records, wrong device screen, old app or firmware state, or using the wrong wallet context.
No. Detection problems are usually local app, device, or pairing issues. Check public addresses and Bitcoin account context separately.
No. Detection should not require typing recovery words into a website, chat, unverified app prompt, or support form.
Phone model, Envoy version if known, Passport screen state, current step, error text, and screenshots without private information.
Use official Foundation Passport support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.