Use this Foundation Passport QR signing support page when unsigned PSBT QR codes will not scan, signed QR data will not broadcast, or approval details do not match what you expected.
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 QR signing problem is usually caused by scan direction, screen brightness, camera focus, wrong Bitcoin account, transaction data size, firmware state, or an unsafe signature request.
Common wallet topics include Foundation Passport QR signing problem, PSBT QR scan failure, unsigned transaction QR, signed QR broadcast issue, Bitcoin transaction approval problem, or fake Foundation Passport signing warning.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
If QR signing fails during app/device connection, start with connection checks.
OpenIf Envoy cannot recognize Passport before signing, troubleshoot detection.
OpenIf the transaction is for an account not visible in Envoy, check account display.
OpenFirmware state can affect QR signing and device readiness.
OpenQR signing and pairing troubleshooting should never require seed phrase entry.
OpenReturn to Foundation Passport support for QR, Envoy, and recovery help.
OpenReport non-private QR signing 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
Follow the expected PSBT flow: Envoy or wallet software shows unsigned transaction data for Passport to scan, then Passport shows signed data for the app to scan and broadcast when appropriate.
Step 2
Increase brightness, clean screens and camera lenses, avoid reflections, hold steady, and keep the entire QR code visible.
Step 3
Reject the request if the destination, amount, fee, change output, or account context does not match your intent.
Step 4
If signing fails because the wrong account or address type is selected, fix account context before retrying approvals.
Check camera permission, selected wallet, Bitcoin account, transaction status, and whether the app is waiting for signed QR data.
Confirm the device is unlocked, showing the intended scan or signed QR screen, and displaying transaction details you recognize.
If QR signing failed after an app or firmware update, verify official firmware state, app version, pairing record, and Bitcoin account context before restoring or resetting.
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.
“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.
“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.
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 QR direction, glare, low brightness, camera focus, cropped QR codes, app permissions, wrong account, or firmware/app state.
The signed data may not match the selected Bitcoin account, the transaction may be stale, or the app may need a safe refresh before broadcast.
No. Reject unexpected destinations, amounts, fees, change details, or signature requests and investigate before trying again.
No. QR signing should not require sharing or entering recovery words, private keys, PIN, passwords, or remote access.
Use official Foundation Passport support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.