Receiving crypto into self-custody begins before the sender presses Withdraw. The asset, blockchain network, Ledger account and deposit address must describe the same destination, and the address shown on the computer must match the address independently derived and displayed by the Ledger device. This guide explains that full workflow: create the correct account, verify every character on the Secure Screen, defend against clipboard replacement and address poisoning, make a test deposit, confirm the result on-chain and troubleshoot assets that were sent through the wrong network or to an address controlled by an older recovery phrase.
Last reviewed: October 26, 2026. Ledger product names, applications, supported networks, account behavior and interface labels can change. Exchange withdrawal procedures and blockchain recovery options also differ. Confirm current instructions in official Ledger documentation and the sender’s official interface. This independent guide is educational, is not affiliated with Ledger and does not guarantee recovery of incorrectly sent assets.
1. What is a Ledger receive address?
A receive address is a public blockchain destination derived from the keys protected by the Ledger device. Other people and services can use it to send assets to the corresponding account. Sharing the address does not reveal the private key and does not authorize spending.
The address is specific to an account and blockchain context. A familiar token name is not enough: the sender and recipient must agree on the actual network.
2. Receiving does not require a signature
The sender creates and signs the blockchain transaction. The receiving Ledger device does not need to be online when the network confirms it. Assets are recorded on the blockchain, not stored physically inside the hardware wallet.
The device is nevertheless essential during setup because its Secure Screen can verify that the receiving address shown by the connected computer is genuinely derived from the keys held by that Ledger.
3. Why verify an address on the Ledger device?
A compromised computer could replace the address displayed by an application with one controlled by an attacker. The Ledger device derives and displays the address in its isolated environment. Comparing the two screens can expose that manipulation before the address is shared or pasted into an exchange.
Ledger’s security guidance says to trust the address shown on the device display. A matching address on both screens establishes a stronger origin check than copying from the computer alone.
4. Secure Screen versus connected screen
| Display | Role | Main risk |
|---|---|---|
| Ledger Secure Screen | Displays an address derived by the device | User approves without reading the full value |
| Ledger Wallet desktop/mobile screen | Coordinates the receive workflow and copying | Connected device may be compromised |
| Exchange withdrawal form | Defines the actual destination and network | Paste replacement or wrong network selection |
| Transaction history | Shows past public activity | Poisoned or unrelated address copied as destination |
5. How the recovery phrase relates to the address
The Secret Recovery Phrase is the root backup for the private keys and accounts derived from it. The correct Ledger device can display addresses for the phrase currently loaded on that device. A different phrase produces a different set of accounts even if account names look identical in the application.
Never type the phrase into Ledger Wallet, an exchange, a website, a browser extension or a support chat. Legitimate receive-address verification happens on the device without revealing recovery words.
6. Prepare a trusted environment
Use the authentic, updated Ledger Wallet application on a device you control. Verify that the Ledger hardware passes the genuine check and that no unexpected remote-control or screen-sharing session is active. Close unnecessary applications before copying financial data.
If clipboard behavior, browser redirection or unexplained warnings suggest malware, stop. Do not “test” a suspicious computer with real funds.
7. Create the correct blockchain account
Install the appropriate blockchain app on the Ledger device through the official manager, then add the corresponding account in Ledger Wallet. Account labels are local organizational aids; verify the actual asset and network rather than trusting a custom name such as “Main Wallet.”
For tokens, the receiving address may belong to the network’s native account. For example, supported ERC-20 tokens use an Ethereum account address. Other networks require their own account context.
8. Asset and network are separate choices
A token such as USDT or USDC can exist on several blockchains. The ticker may look identical while the network, fees and recovery path differ. The exchange’s withdrawal network must match the blockchain account selected in Ledger Wallet.
| Asset example | Possible network | Required match |
|---|---|---|
| BTC | Bitcoin | Bitcoin account and Bitcoin withdrawal network |
| ETH | Ethereum | Ethereum account and Ethereum network |
| USDT | Ethereum, Tron, BSC and others | Exact token network supported on both sides |
| USDC | Ethereum, Solana, Base and others | Exact account and withdrawal network |
| BNB | BNB Smart Chain | BSC account and BSC route |
| XRP | XRP Ledger | XRPL address and sender’s required fields |
9. Do not choose the cheapest network automatically
A lower withdrawal fee does not prove compatibility. Exchanges may offer wrapped or bridged versions of an asset on networks that differ from the account the user intended to fund. Select the chain first, then consider fees.
If Ledger Wallet does not support the intended asset/network display, research current official support before sending. Do not assume that every EVM-looking address creates the same user experience.
10. Open the Receive flow
- Open the authentic Ledger Wallet application.
- Select Receive.
- Choose the intended asset and blockchain account.
- Connect and unlock the Ledger device.
- Open the requested blockchain app on the device.
- Allow Ledger Wallet and the device to display the address.
- Compare the complete value before approving.
11. Why the device must be connected for verification
Ledger Wallet may be able to show an address from previously synchronized account data without the hardware connected. Ledger warns that such an address is unverified in the current session. It may still belong to the account, but the user has not obtained the strongest protection against a compromised computer display.
For a meaningful deposit, connect the device and verify the address on its Secure Screen.
12. Open the correct blockchain application
The device application tells Ledger which blockchain derivation and protocol are being used. If the software requests the Ethereum app, do not substitute Bitcoin or another app merely to advance the screen. Investigate unexpected prompts.
Keep device apps and Ledger Wallet updated through official channels before the transfer window, then verify ordinary account access.
13. Compare the full address
Scroll through and compare every segment shown on the Ledger device with Ledger Wallet. Long addresses are inconvenient by design; checking only the first and last characters creates the exact shortcut exploited by poisoning attacks.
Break the value into consistent groups and read in the same direction on both displays. Take your time. Do not photograph the device screen as a substitute for comparison.
14. What if the two addresses do not match?
Reject the address on the Ledger device and stop the workflow. Do not copy, share, whitelist or test the mismatched value. Close Ledger Wallet, disconnect safely and investigate the computer, cable, application authenticity and device state.
A mismatch is not solved by trusting the more convenient screen. Contact official Ledger support through its verified website if the cause remains unclear, without sharing the recovery phrase.
15. Approve only after the comparison
Approval confirms that the user reviewed the address. It does not send funds and does not whitelist the destination on an exchange. Copy the verified address only after approval, and keep the device display available for the next comparison where practical.
16. Copying the address safely
Use the application’s Copy function rather than manually typing a long address. Immediately paste it into a temporary visible field within the trusted workflow and compare it with the device display. Avoid clipboard-sync tools, remote desktops and messaging drafts.
Clear temporary clipboard data after the transfer where the operating system supports it, understanding that clearing cannot undo malware exposure.
17. Verify again after pasting into the exchange
The withdrawal form is the value that matters to the sender. Compare the entire pasted destination with the Ledger device, not only with the earlier computer copy. This second check can detect clipboard replacement between Copy and Paste.
Also confirm the selected network, asset and amount before submitting. Address validation by the exchange does not guarantee that the destination is yours.
18. QR codes reduce typing, not verification
A QR code can encode the address for a mobile sender, but the code is generated on a connected display that may be compromised. Scan it, then compare the decoded destination against the Ledger Secure Screen before confirming.
Do not assume that a camera preview showing familiar first and last characters is enough.
19. What is clipboard jacking?
Clipboard-jacking malware monitors copied data and replaces a cryptocurrency address with one controlled by an attacker. The replacement may share a similar prefix or suffix. Ledger Wallet may show a mismatch warning when copied and pasted values differ, but users should perform their own complete comparison.
If an address changes after copying, do not use the device for financial activity. Disconnect it from sensitive workflows and investigate or rebuild the environment.
20. What is address poisoning?
In an address-poisoning attack, a scammer creates an address that visually resembles a real counterparty or one of the user’s addresses. The attacker sends a tiny or zero-value transaction so the fake address appears in transaction history. The victim later copies it without full verification.
The attack does not need to break Ledger’s private-key protection. It targets the human habit of using history as an address book.
21. Zero-value transfers are not trusted contacts
A zero-value token event can appear to come from or go to an address without representing a genuine transfer authorized in the normal way. Treat unsolicited dust and zero-value entries as untrusted blockchain data.
Ledger Wallet may filter some suspicious activity, but interface filtering is not a substitute for generating a fresh verified receive address.
22. Never copy a deposit address from transaction history
History can contain sender addresses, exchange hot-wallet addresses, smart contracts, old accounts and poisoned lookalikes. It cannot prove that an entry is the correct current destination. Generate the address through Receive and verify it on the device.
23. Exchange address allowlists
An allowlist can reduce the chance of a rushed future entry, but the first enrollment is a high-impact action. Verify the full address on the Ledger device, confirm the network and use the exchange’s waiting period and MFA controls.
A label such as “Ledger” does not validate the stored value. Recheck after device recovery, account changes or uncertainty about which recovery phrase controls the destination.
24. Send a small test deposit first
Ledger recommends a small test before moving a large amount. The test should be meaningful enough to observe after fees but small enough that a mistake is limited. Confirm the exchange’s minimum withdrawal and the network’s economics.
Do not send the main amount until the test has the required confirmations and appears under the intended Ledger account.
25. Verify the test transaction independently
Record the public transaction hash from the sender and open an appropriate trusted blockchain explorer through a verified route. Confirm the network, destination, amount and status. Then compare the result with Ledger Wallet.
A transaction hash is public evidence, not a recovery secret. Still avoid publishing it unnecessarily when privacy matters.
26. Wait for the right confirmation state
Different blockchains and exchanges use different confirmation thresholds. A pending transaction is not a reason to resend immediately. Check whether it is broadcast, included in a block or still undergoing exchange processing.
Network congestion and exchange batching can delay display without changing ownership.
27. Send the main amount using the verified route
Use the same verified address and network after the successful test when the workflow and privacy plan permit it. Recheck the destination after pasting and review exchange withdrawal details again. Avoid changing devices, accounts or networks between the test and main transfer without repeating verification.
28. Why a Bitcoin receive address changes
Bitcoin and other UTXO-based accounts can generate a new receive address after prior use to improve privacy. These addresses belong to the same account through its derivation structure. A new address in Ledger Wallet does not automatically mean the wallet changed.
Generate and verify the current address for each new receipt rather than relying on a screenshot or old message.
29. Can an old Bitcoin address still receive funds?
Ledger documentation states that previously generated Bitcoin addresses remain usable when they belong to the same account. Reuse can reduce privacy by linking payments, so a fresh verified address is generally preferable.
If account ownership is uncertain after a recovery or device reset, verify control before sending more funds.
30. Address reuse and privacy
Repeated deposits to one public address can make balances and payment relationships easier to correlate. This does not normally expose the private key, but it can expose financial behavior. Follow the wallet’s normal address-generation model and avoid publishing addresses alongside personal identity.
31. The deposit is confirmed but not visible
First verify the public transaction on the correct explorer. If the destination matches and the transaction is confirmed, check that Ledger Wallet has the correct account, token and network. Update or synchronize the application and add the appropriate supported account where necessary.
Do not reset the Ledger device or enter the recovery phrase into a random recovery tool merely because the portfolio view is delayed.
32. Internal and batched exchange transactions
Some exchanges batch withdrawals or use smart-contract internal transactions. Ledger’s Coinbase withdrawal guidance notes that certain Ethereum batches may not appear in every interface view even when funds are safe. The explorer and correct account can provide additional context.
Confirm current software behavior and transaction type before attempting any recovery action.
33. Wrong EVM network, same-looking address
Ethereum-compatible networks often use the same hexadecimal address format. If an asset was sent through another EVM network, the private key may still control that address, but the balance exists on the network actually used. Add the supported account for that chain and verify the transaction there.
Recovery can require the native gas asset of the actual network. Do not move tokens until the path is understood and official guidance supports it.
34. Wrong non-EVM network
Sending through incompatible blockchain families can be harder or impossible to recover. Address-format acceptance by an exchange is not proof of recoverability. Stop experimenting and gather the transaction hash, asset, network and destination for official support.
Never give support the Secret Recovery Phrase. Legitimate investigation can begin with public transaction information.
35. Assets sent to a smart contract address
A contract may not expose a function that returns accidentally transferred assets. Control of a related wallet does not imply control of the contract’s behavior. Identify the verified contract and contact the responsible project through official channels, understanding that recovery may not be possible.
36. Address from an older recovery phrase
Ledger Wallet can retain an account that was created under a previous Secret Recovery Phrase. If the device now contains a different phrase, the account may remain visible while the current device cannot spend its funds or reproduce its address verification.
If the old phrase or a device still containing it exists, follow a controlled recovery workflow on genuine hardware. If neither remains, access may be impossible.
37. Determine which phrase controls an account safely
Do not compare recovery words with a website. Use Ledger’s official Recovery Check workflow where appropriate to verify the phrase currently associated with a device, and label accounts carefully after restoration. Never reset the only working device before confirming the backup.
38. Do not expose the phrase during troubleshooting
Scammers exploit missing deposits by offering “synchronization,” “validation” or “manual recovery” websites. Ledger Support does not need the 24 words and does not offer phone support according to its current contact guidance.
Anyone asking for the phrase, private key or remote access can take the assets. End the conversation and contact Ledger through the verified support page.
39. Troubleshooting decision table
| Symptom | Likely area | Safe first step |
|---|---|---|
| Device and app addresses differ | Display, application or device integrity | Reject and stop |
| Pasted address changed | Clipboard compromise | Do not send; investigate device |
| Confirmed transaction, empty account | Wrong account, network or token view | Check hash on the actual network |
| New Bitcoin address | Normal UTXO privacy behavior | Verify new address on device |
| Funds on another EVM chain | Wrong network selection | Add supported network account |
| Address belongs to old phrase | Recovery lineage | Locate verified old backup/device |
| Completed transfer to stranger | Wrong recipient | Contact recipient if known; transaction is generally irreversible |
40. What to tell Ledger Support
Provide the Ledger model, Ledger Wallet version, asset, intended network, actual network, public address, transaction hash, account type and steps already attempted. Redact unnecessary identity or balance information.
Do not send recovery words, PIN, private keys, full exchange credentials or remote-control access. Ledger’s official contact page is the starting point.
Ledger receive-address checklist
- Authentic, updated Ledger Wallet application.
- Genuine, unlocked Ledger device.
- Correct blockchain app installed and open.
- Correct asset and account selected.
- Sender and recipient use the same network.
- Full address matches the Ledger Secure Screen.
- Pasted exchange destination was compared again.
- Address was not copied from transaction history.
- No clipboard mismatch or malware warning appeared.
- Network fee savings did not override compatibility.
- Small test deposit completed first.
- Transaction hash, destination and confirmations checked.
- Main transfer repeated the verified workflow.
- No recovery phrase was entered into software or support.
Frequently asked questions
How do I verify a Ledger receive address?
Select Receive and the correct account in Ledger Wallet, connect and unlock the device, open the requested blockchain app and compare the full address on both screens before approving.
Why must I verify the address on the Ledger device?
The connected computer can be compromised. The device independently derives the address and displays it on its isolated Secure Screen.
Can I receive crypto while my Ledger is offline?
Yes, the blockchain can receive funds without the device online. Connect the device before sharing a new address so its origin can be verified securely.
Is an unverified address safe?
It may belong to the synchronized account, but Ledger warns that using an address not checked on the device carries additional risk. Verify meaningful deposits on the hardware screen.
Why did my Bitcoin receive address change?
UTXO wallets commonly generate fresh addresses after use for privacy. They can belong to the same Ledger account.
Can I reuse an old Bitcoin address?
Previously generated addresses normally remain valid for the same account, but reuse reduces privacy. Generate and verify a fresh address where practical.
What is Ledger address poisoning?
It is a scam that inserts a lookalike address into transaction history through tiny or zero-value activity, hoping the user later copies it without verification.
Why should I not copy from transaction history?
History can contain poisoned addresses, senders, contracts and unrelated exchange wallets. It is not a verified address book.
What if the pasted address changes?
Do not send. Treat the computer as potentially compromised, disconnect it from the workflow and investigate clipboard malware.
What if I selected the wrong withdrawal network?
Check the public transaction on the actual network. EVM-to-EVM mistakes may be recoverable by adding the correct supported account, while incompatible networks may be difficult or impossible to recover.
Why is confirmed crypto not showing in Ledger Wallet?
Check the actual network, transaction type, account and token visibility. A confirmed explorer record at the controlled address means the portfolio interface may need the correct account or synchronization.
Should I send a test transaction first?
Yes, particularly for a new address, network or large transfer. Verify the test’s arrival and confirmations before sending the main amount.
Final takeaway
A Ledger device protects private keys, but receiving safely still depends on correct public information. The asset, network, account and address must align, and the Secure Screen is the trusted place to verify that the displayed address belongs to the device.
Generate rather than retrieve, compare rather than glance, test before transferring a large balance and investigate on-chain evidence before changing recovery settings. Most address failures become dangerous when a user rushes past one of those boundaries.
Official Ledger resources
- Ledger Support — Crypto Sent to the Wrong Address or Network: wrong EVM networks, old Bitcoin addresses, clipboard replacement, poisoned history and older recovery phrases.
- Ledger Academy — Hardware Wallet Security Best Practices: Secure Screen address verification and small test transfers.
- Ledger Academy — Address Poisoning Attacks: lookalike addresses, transaction interception and full-address verification.
- Ledger Support — Withdraw From Coinbase to a Ledger Account: matching networks, generating a deposit address and testing the withdrawal.
- Ledger Support — Send Crypto Assets: current transfer workflow, network selection, fees and test transactions.
- Ledger Academy — Zero-Value Transfer Scam: fake lookalike addresses placed in transaction history.
- Ledger Support — Contact Ledger Safely: verified support channels and warnings that support never needs the recovery phrase.