Quick overview
This article explains, in plain technical terms, how to receive and send cryptocurrency with a hardware wallet and how to confirm transactions on the device itself. I’ll walk through step-by-step actions you should take, the checks to perform on the device screen, and special cases like NFTs and smart-contract approvals. Think of your seed phrase like the master key to a safe deposit box — the device is the lock and the app is the receptionist.
I believe clear muscle-memory steps reduce mistakes. Short steps first. Then the checks.
Who this guide is for
- Crypto holders using a hardware wallet for self-custody who need practical, everyday instructions.
- People sending or receiving Bitcoin, Ethereum and common tokens (including NFTs) safely.
- Users considering multisig or air-gapped signing in the future.
Who should look elsewhere? If you prefer fully custodial services (an exchange or custodial wallet) this guide might be overkill. But if you own your private keys and want practical safeguards, this is for you.
For setup basics, see the getting started guide: Getting started. For seed phrase fundamentals, read Seed phrase basics.
How to get an address (Step-by-step)
How do I get an address on my hardware wallet? Follow these steps.
- Unlock your hardware wallet with your PIN.
- Open the companion app on your desktop or mobile (or a compatible third-party wallet). If you need the companion app, see download the companion app.
- In the app, choose the account for the cryptocurrency you want to receive and click "Receive" or similar.
- The app will show an address. Immediately verify that same address on your device screen. The device must display the full address for manual verification.
- If both match, copy the address from the device display (not from clipboard when possible) and share it with the sender.
Why verify? Because malware can swap addresses on the host computer or phone. The hardware wallet’s secure element isolates private-key operations so that the address shown on the device is the authoritative one.
See details on multiple accounts and address types: Multiple accounts and wallets and Privacy, addresses & UTXO.
How to receive crypto safely (Step-by-step)
- Request a single-use address from your wallet app.
- Verify the address on the device screen. Short addresses are dangerous (they can be truncated) — always scroll to view the full address.
- Confirm the chain and token type (e.g., Bitcoin vs an ERC-20 token). Sending the wrong chain to an address can be irreversible.
- For tokens, verify the contract address in the app (if shown) or use the token’s official channels to confirm.
A short test transfer is a smart move for high-value incoming transfers. It costs a small fee and proves that the sender routed funds correctly.
How to send from your hardware wallet (Step-by-step)
Here’s a general send flow (what I follow every day):
- Open the companion app or a compatible third-party wallet and select "Send."
- Paste or type the recipient address. Double-check it visually (and on the device) — never rely on paste alone.
- Enter the amount. Check token decimals for tokens (some have different decimals).
- Set the network fee (fee priority). For account-based chains (like Ethereum), confirm base fee and priority fee; for UTXO chains (like Bitcoin), check sats/vByte if available.
- Initiate the transaction in the app, then look at the transaction summary on the device. The device shows the final data that will be signed.
- Carefully verify: recipient address, amount, and fee. Also verify whether the transaction is a simple transfer or a smart-contract interaction (see next section).
- Approve on the device to sign. The app will broadcast the signed transaction to the network.
In my testing, the most common slip is not verifying the on-device address and assuming the app display is correct. Don’t do that.
Confirming transactions on the device
How do I confirm a transaction on my hardware wallet? Confirming means verifying and approving what you see on the device screen.
- Read every line the device shows. Short addresses may be truncated; use the device controls to scroll.
- Confirm the amount and currency symbol.
- Confirm the recipient address (the first and last characters should match what you expect). Ask: does this address belong to the intended recipient?
- Check the network fee. A low fee can leave the transaction stuck.
- For smart-contract transactions, the device may show only a summary. When in doubt, reject and inspect the transaction in the companion app or a block explorer.
Remember: approval on the device is the final gate. If you approve a bad transaction, the device can't reverse it. But if you deny, nothing broadcasts.
Special cases: NFTs, tokens and smart-contract interactions
Sending an NFT? Watch these extra items:
- Verify the contract address and token ID. Token metadata may not display fully on-device. (Yes, that’s annoying.)
- When receiving NFTs, make sure the account supports that chain and token standard. See NFT transfers for marketplace specifics.
- For smart-contract approvals (token allowances), prefer setting limited allowances instead of unlimited where possible.
And always test with a small transfer if the asset is valuable.
Connection methods and security trade-offs (table)
| Connection |
Convenience |
Security notes |
| USB (wired) |
High |
Wired reduces exposure to wireless attacks. The device still verifies transactions on-screen. |
| Bluetooth |
High mobile convenience |
Wireless pairing adds an attack surface. Keep firmware up to date and unpair in public places. |
| NFC |
Quick tap |
Short range limits exposure but still requires on-device verification. |
| Air-gapped (QR/SD) |
Low convenience |
Highest isolation: signing offline prevents network-based attacks. See air-gapped signing guide. |
Common mistakes and quick security checklist
Common mistakes I see repeatedly:
- Failing to verify addresses on the device.
- Reusing an address for privacy-sensitive transactions.
- Approving contract interactions without confirming details.
- Buying a device from an unofficial seller (supply chain risk).
Quick checklist before approving any send:
- Does the address on the device match the intended recipient? (Yes/No)
- Is the amount correct? (Yes/No)
- Is the fee reasonable for the network? (Yes/No)
- Is this a simple transfer or a contract call? (Transfer/Contract)
If any answer is No, stop and investigate. But don’t panic — rejecting simply aborts the action.
For firmware safety and verification steps, see firmware updates & verification.
Troubleshooting: stuck or unconfirmed transactions
If a transaction is unconfirmed:
- For UTXO chains, consider Replace-By-Fee (RBF) if enabled by your wallet.
- For account-based chains, use the wallet’s "speed up" or set a higher gas price (if supported by the app).
- If the transaction never left your computer because you didn’t approve on device, simply retry.
If the device disconnects mid-process, reject and restart both device and app. See our troubleshooting guides: Troubleshooting common errors and Device not recognized.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes. If you have your seed phrase (recovery phrase) backed up correctly, you can restore your private keys to a new compatible hardware wallet or a trusted software wallet that supports the same standard (e.g., BIP-39), assuming you understand derivation paths.
Q: What happens if the company that made my hardware wallet goes bankrupt?
A: The hardware vendor’s status doesn’t affect your private keys. With your seed phrase and compatible tools, you can restore and access funds. That said, community-maintained tools and open standards help long-term recoverability.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth is convenient for mobile use but adds an extra attack surface. If you use Bluetooth, keep firmware current, confirm on-device details, and unpair in public spaces. For maximum isolation, use USB or air-gapped signing.
Conclusion & next steps
Daily sending and receiving with a hardware wallet is straightforward once you build good habits: always verify addresses and amounts on the device, understand the network fee, and be cautious with contract approvals. What I've found in months of testing is that the single best habit is simple: read the device screen every time.
Want to read setup steps or backup strategies next? Check the getting started guide and backup pages: Getting started and Backup & recovery. For advanced signing workflows, see air-gapped signing and third-party compatibility.
If you want a quick printable checklist, the Transaction confirmation checklist above works well as a pocket reference.
Stay practical, and verify on-device.
