The choices on a hardware wallet’s first-start screen do different jobs. Separating a new wallet, recovery and an optional passphrase helps you catch mistakes before any funds move.
A hardware wallet setup is not finished when a balance screen appears. A device can work normally while its backup has been copied incorrectly or the selected receiving account is not the one you intended. The useful question is what you have actually verified before moving funds.
This guide covers personal hardware wallets that use recovery words. KriptoMeta compared manufacturer documentation on 15 October 2026; it does not claim a hands-on device test or a live transfer. If you are still choosing a product, start with the custody and compatibility checks for choosing a wallet. Here, the task is to prepare a chosen device for use, rather than rank competing models.
1. Verify the app and the device’s origin separately
Start from the manufacturer’s independently verified official address. Avoid installing from a search advertisement or a QR code added to the package. Open the instructions for your exact model, then check the packaging, seals and device as specified. Different manufacturers do not share one packaging standard or first-start behaviour.
The official Trezor Safe 5 setup includes device authentication after the application and firmware steps. Do not transplant that sequence to a different model. If device or firmware authentication reports a warning, stop instead of disabling the protection to proceed. Reach support through a channel you have verified independently.
Do not fund a device supplied with a preset PIN or completed recovery words. A seller who says it was configured to save you time has not shown that you alone control the keys. Intact packaging is not a substitute for the model’s other checks, and no single check rules out every supply-chain risk.
If the download address looks suspicious, use our phishing and fake-site checks to examine the domain and requested permissions.
2. Separate creating a wallet from restoring a backup
Choose the new-wallet route when creating independent keys for the first time. Use recovery when restoring access to an existing hardware wallet. Both options may appear on the same screen, but they have different outcomes: one creates a new key arrangement, while the other brings an existing arrangement back.
Importing recovery words from a phone wallet does not erase copies that may previously have existed online. Ledger’s software-to-hardware migration explanation distinguishes fresh keys from importing an old backup. Moving assets into the newly generated account requires on-chain transactions. Check network support and costs before sending an entire balance.
3. Give the PIN, backup and passphrase different jobs
| Detail | Purpose | Does not replace |
|---|---|---|
| PIN | Protects local access to the device | The backup needed after device loss |
| Recovery words | Restore access to keys in a compatible setup | Checking the network and account configuration |
| Passphrase | Derives a different wallet using an extra secret where supported | An account password that support can reset |
Set the PIN through the trusted setup process. The distinction in Ledger’s PIN documentation is straightforward: unlocking a device and recovering its wallet are different tasks. Changing the PIN does not invalidate a leaked copy of the recovery words.
Record the words offline, in the order displayed for your model. Do not translate them, photograph them or paste them into a web form for verification. Our seed phrase storage guide covers the separate decisions about materials, location and access. Do not change the word count to match instructions for another device.
Understand how a passphrase differs from a PIN before enabling it. It is optional, not a mandatory step for beginners. Using it adds responsibilities for supported characters, exact spelling and recovery. An additional security feature should not become an additional secret you cannot reliably retain.
4. Check the backup without wiping the device
Use the official backup check where the product supports it. For example, Check wallet backup on Safe 5 tests the recorded backup without resetting the wallet; its menu is under Settings → Device → Wallet backup. Words are entered on the device. Other models can have different entry procedures, so follow the documentation for the hardware in front of you.
If the check fails, preserve your only working access. Resolve the word order or recording problem through the official process before funding the wallet. Sharing words with a screen-sharing helper, chatbot or online “seed checker” is not a backup test.
When a passphrase is in use, checking the recovery words is not enough. Trezor’s passphrase verification method separately checks that reopening the wallet returns to the same account. Keep the network, account and any address type consistent. An unexpected empty balance is a reason to investigate the passphrase, account selection and enabled networks, not a prompt to deposit more funds.
5. Compare the receive address with the device display
Select the intended asset and network, then show the receive address through the hardware wallet’s verification screen. Compare every character against the address on your computer or phone. Do not pick a destination from transaction history or familiar-looking first and last characters. Ledger’s receiving-address guidance explains why the connected computer’s display needs that comparison.
The same address format on several EVM networks does not make the sender’s network choice irrelevant. The receiving setup must support the asset on the selected network. See the network, minimum and fee checks for a crypto transfer for the sending workflow. A hardware wallet cannot automatically reverse a transfer made over the wrong network.
6. Decide what a small test will establish
Start with a small amount you can afford to lose, while accounting for the sender’s minimum and fees. The test is more than seeing a balance increase: the asset, network, device-verified recipient and on-chain record should agree. Tracking the transaction by its TXID distinguishes a pending entry from a confirmed transfer. The network record alone does not prove you control the recipient’s keys.
Consider a hypothetical setup. Alex sends a small amount of ETH to an Ethereum account generated on the device. The explorer shows the intended recipient, and the wallet app displays the receipt. Alex reconnects the device and verifies the same account’s address again. That repeats the receiving-address check. Testing an outgoing transaction would be a separate action, requiring the destination and fee to be checked on the device. Receiving, sending and restoring from backup are different tests; a success in one does not stand in for the others. No live fee or universal test amount is assumed here.
| Result | What you learned | Still to check |
|---|---|---|
| Backup check passed | The entered backup matches the device’s backup | Passphrase, account and network selection |
| Addresses matched | The selected account’s address was verified on the device | The network selected by the sender |
| Test funds arrived | That transfer reached its destination | The safety of future signatures or applications |
What should your setup record contain?
Keep a private record of the model, official app, backup standard, networks and account types that may matter during recovery. Add the date of your checks. You do not need to gather all secrets into that note; if you take screenshots, keep recovery words, PINs and passphrases out of them.
Hardware signing does not make every application permission safe. When you start using Web3 apps, review the scope of token spending approvals. Confidence in a completed setup should not turn into a habit of approving every request that follows.
