Use this Foundation Passport support page when Passport and Envoy will not connect, QR handoff stalls, or the Bitcoin hardware wallet is not ready for 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
Foundation Passport not connecting is usually caused by Envoy app permissions, stale pairing state, wrong QR direction, locked device state, firmware readiness, or an unsafe fake support path.
Common wallet topics include Foundation Passport not connecting, Envoy pairing problem, QR scan failure, Bitcoin hardware wallet connection issue, device readiness problem, or fake Foundation Passport support warning.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
If pairing starts but Envoy cannot see Passport, use detection checks.
OpenIf connection fails during signing, troubleshoot QR handoff and PSBT review.
OpenFirmware prompts can affect pairing and device readiness.
OpenIf pairing works but Bitcoin balance is missing, check account display.
OpenDo not reset or restore until recovery phrase safety is clear.
OpenReturn to Foundation Passport support for setup, firmware, QR signing, and balance help.
OpenReport non-private Foundation Passport connection 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
Open Envoy only from a verified source, confirm the active Bitcoin wallet account, and avoid pairing links from ads, messages, comments, or support chats.
Step 2
Close and reopen Envoy, unlock Passport, check camera permissions, and retry the pairing or signing flow before resetting, restoring, or reinstalling.
Step 3
Clean the phone camera and Passport screen, raise brightness, avoid glare, keep the whole QR visible, and confirm the app and device are on matching screens.
Step 4
If connection stopped after an update, use official update guidance and never type recovery words into an update page or support form.
Check app version, camera permission, selected wallet, Bitcoin account, pairing record, and whether another wallet context is active.
Confirm Passport is unlocked, charged, on the expected screen, and not blocked by setup, firmware, or confirmation prompts.
If the issue appears only during transaction signing, review PSBT QR direction, device scan, signed QR return, and final broadcast separately.
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 Envoy permissions, stale pairing state, QR scan problems, locked device state, firmware prompts, or using the wrong Bitcoin wallet context.
Do not reset until recovery phrase safety is clear and Envoy, camera, QR, firmware, and device-state checks have been tried.
No. Connection troubleshooting should not require sharing recovery words, private keys, PINs, passwords, or remote access.
Device model, Envoy version if known, phone model, connection step, exact error, and screenshots without private information. Never include seed words.
Use official Foundation Passport support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.