Receiving crypto on Trezor Wallet generates a deposit address through the companion application and verifies it against the hardware device screen before sharing it with the sender.
The address displayed on the device screen is cryptographically derived from the private key inside the Secure Element — it cannot be altered by software running on the connected computer.
| Receive Step | Platform | Critical Action |
|---|---|---|
| Select account | Wallet interface | Match account to asset and network |
| Generate address | Wallet interface | Click Receive → Show full address |
| Verify address | Hardware device screen | Compare against wallet interface |
| Share address | After device confirmation | Copy, share, or QR code |
| Monitor arrival | Wallet dashboard | Wait for required confirmations |
Receiving crypto is the process of generating a deposit address, verifying it on the hardware device screen to confirm it has not been manipulated, and sharing the verified address with the sender. The cold storage device never needs to be connected at the moment of receipt — funds arrive at the blockchain address regardless of whether the hardware signer is plugged in.
Bitcoin generates a fresh address for every new receive transaction — the HD wallet derives each from the same seed without reusing previous addresses. Ethereum, Solana, XRP, and most non-Bitcoin chains use a single fixed address per account.
Address verification protects against two attack categories: malware that substitutes addresses in the wallet interface, and phishing sites that display attacker-controlled addresses disguised as Trezor deposit screens. The hardware device derives receive addresses independently of the connected computer — the address on the device screen is always a valid address belonging to the wallet.
If the address displayed in the companion application does not match the device screen, the computer is infected with address-substitution malware and no addresses from that machine should be trusted until the malware is removed.
Connect and unlock, then Accounts → select the Bitcoin account (Taproot, SegWit, or Legacy SegWit).
Click Receive → Show full address, prompting device verification.
Compare every character against the wallet interface and press confirm on the device.
Share the address or QR code, then wait for 3-6 confirmations (~30-60 minutes) before treating funds as final.
Ethereum and all ERC-20 tokens share the same 0x address — receiving USDC, USDT, LINK, or any ERC-20 token requires no address configuration beyond the standard Ethereum receive flow. ERC-20 tokens appear automatically once received — no manual token addition is required. ETH itself is required in the account for gas to spend received tokens later.
Receiving USDC sent on the Polygon network into an Ethereum mainnet account results in funds on the wrong chain — the account network selector must match the sender’s network.
XRP uses a single fixed address per account, but centralized exchanges require a destination tag alongside the address to attribute the deposit to the correct user account. Note both the XRP address and Destination Tag, and enter both on the exchange withdrawal page. Sending XRP without a destination tag routes funds to the exchange’s master pool, requiring support to recover.
| Address Type | Format Prefix | Fee Efficiency | Default in 2026 |
|---|---|---|---|
| Taproot (P2TR) | bc1p… | Highest | Yes |
| Native SegWit (P2WPKH) | bc1q… | High | Legacy default |
| Legacy SegWit | 3… | Medium | Transitional |
| Legacy (P2PKH) | 1… | Lowest | Oldest format |
Taproot is the default new Bitcoin account type in Trezor Suite 2026 — it provides the lowest transaction fees and strongest on-chain privacy through Schnorr signatures. Use Native SegWit as the fallback if a sender’s platform doesn’t yet support Taproot.
Trezor generates a new Bitcoin receive address for every incoming transaction using HD wallet (BIP-32/BIP-44) derivation. Each fresh address is mathematically derived from the same master seed — all fresh addresses belong to the same account and all received funds are accessible through a single recovery.
| Behavior | Address Reuse | Fresh Address Per Transaction |
|---|---|---|
| Funds received correctly | Yes | Yes |
| Transaction privacy | Reduced — linked on-chain | Better — unlinkable |
| Recommended practice | No | Yes |
| Network | Recommended Confirmations | Time at Normal Fee |
|---|---|---|
| Bitcoin | 3-6 confirmations | 30-60 minutes |
| Ethereum | 12-35 (exchange-dependent) | 2-7 minutes |
| Arbitrum / Base | 1-2 | Under 1 minute |
| Solana | 1 | Seconds |
Coinbase requires 3 Bitcoin confirmations (~30 minutes), Kraken requires 6 (~60 minutes). EVM Layer 2 networks achieve finality in seconds to minutes.
| Scenario | Result | Recovery |
|---|---|---|
| USDC sent on Ethereum → Arbitrum selected | Arbitrum account shows zero | Switch to Ethereum account |
| ETH sent via BNB Chain → Ethereum selected | ETH-equivalent on BNB Chain | Create BNB account in Suite |
| USDT (Tron) sent to Ethereum address | Inaccessible in Trezor Suite | Requires third-party Tron wallet |
| XRP sent without destination tag | Arrives in exchange general pool | Contact exchange support with tx hash |
Connect the device, select the correct account, click Receive → Show full address, verify on the hardware device screen, press confirm, then share the verified address or QR code with the sender.
Trezor generates a fresh Bitcoin address for every receive transaction using HD wallet derivation, improving privacy by preventing on-chain linking. Ethereum, Solana, and XRP always use the same fixed address.
Select the Ethereum account → Receive → Show full address → verify on device screen → share. All ERC-20 tokens are received automatically at the same 0x address — no token-specific setup required.
Trezor Suite recommends 3-6 confirmations (~30-60 minutes at Normal fee). Most exchanges require the same before crediting deposits. EVM Layer 2 networks achieve finality in under one minute.
Select the XRP account → Receive → verify on device screen. Note both the address and Destination Tag — both are required when withdrawing from a centralized exchange.
