Quick summary
If you store XRP with a Nano X hardware wallet you’ll meet one specific UX quirk more than once: the destination tag. Think of the destination tag like an apartment number for an XRP address — sometimes it’s required, sometimes it isn’t. In my testing the device verifies addresses on-screen (so you can confirm the receive address) and the companion apps provide a destination-tag field. But mistakes happen. This guide shows how to receive, how to send (with the tag), and how to troubleshoot old error threads such as "ledger ripple wallet can recieve but not send 2018".
(Image placeholder: 
What is an XRP destination tag?
A destination tag is a numeric identifier used by some custodial services and platforms to route an incoming XRP payment to a specific sub-account. It’s not part of the base address — it’s an extra field attached to the transaction. Without it, funds sent to a pooled platform wallet may land in the wrong internal account (or require manual recovery).
Short, concrete analogy: address = building; destination tag = apartment number. No apartment number? Mail may not reach the recipient.
Receiving XRP on a Nano X — step by step
How to accept XRP into a Nano X-secured account. These are the steps I use in routine testing.
- Open the XRP/Ripple app on the Nano X (device must be unlocked).
- Open your companion wallet (desktop or mobile) and navigate to the XRP account.
- Click "Receive" to display the address and — if supported — a destination tag field.
- Verify the entire receive address on the Nano X screen itself, character by character. (This prevents man-in-the-middle attacks.)
- If the sender requires a destination tag, provide the numeric tag shown by your account or enter one you control.
- Wait for confirmations on the ledger and verify the deposit in the companion app.
Tip: when withdrawing from a centralized platform, copy both the destination address and the tag exactly. And always confirm the address on the device screen before finalizing.
Related setup info: first-time-setup and nano-x-setup.
Sending XRP from a Nano X — step by step & checks
Follow these steps to send XRP from the Nano X safely.
- Connect and unlock the Nano X; open the XRP app on-device.
- In the companion wallet, choose "Send" and paste the recipient address.
- If the recipient requires a destination tag, enter it in the dedicated field. Double-check that field — it’s easy to miss.
- Review fees and ensure the account has sufficient balance (including account reserve if the recipient needs activation).
- Verify the full address (and tag if shown) on the Nano X’s screen before approving the transaction.
- Approve on-device to broadcast the signed transaction.
Why verify on-device? Only the device’s display is the authoritative view of the public key/address you’re spending from. If the companion app is compromised, the on-screen verification is your last defense.
Common issues (including the "can recieve but not send" threads)
You may find old community posts saying "ledger ripple wallet can recieve but not send 2018" or queries like "ripple wallet not opening ledger." What caused those reports and how to fix similar problems today?
- Historical problem: In some cases around 2018 users reported they could receive but not send. That often traced to outdated firmware, deprecated companion apps, or a mismatch between the XRP app and the wallet client.
- Troubleshooting steps I use now:
- Update firmware via the official manager (how-to-update-firmware-steps).
- Reinstall the XRP app in the companion application.
- Try a different host (desktop vs mobile) or a different browser mode (WebHID vs WebUSB). See legacy-chrome-app for older Chrome OS setups.
- Check the device connection: cable, OTG adapter, or Bluetooth pairing for Nano X.
If the companion wallet doesn’t open the XRP app on the device ("ripple wallet not opening ledger"), reboots and reconnects often help. If it still fails, consult troubleshooting guides: troubleshooting-not-detected and troubleshooting-general.
Destination tag best practices and recovery scenarios
- Always ask the recipient whether they require a tag. Centralized exchanges and custodial platforms commonly require one.
- If you forget the tag when sending to a centralized platform, contact their support immediately. Recovery is possible but often slow and requires proof.
- For self-custody wallets (your own address), tags are typically unnecessary.
Table: Common cases and tag behavior
| Use case |
Destination tag required? |
If missing |
| Centralized exchange / custodial platform |
Often yes |
Manual recovery may be required (support ticket) |
| Personal self-custody wallet |
No |
Funds land in your account directly |
| Payment processors or pooled accounts |
Often yes |
Funds may be credited to a pool and need routing info |
Chromebook, mobile and desktop compatibility notes
Keyword: "ledger xrp chromebook" and similar searches are common. Chromebook support varies by model and OS version. Practically:
- Chrome OS with up-to-date browser APIs may support WebUSB/WebHID wallet connections. (Check the companion app documentation.)
- If the browser path fails, use the desktop or mobile companion app. For Nano X Bluetooth can simplify mobile connectivity; USB OTG works too.
If you hit compatibility friction, see connectivity-security and legacy-chrome-app.
Security: passphrase, seed phrase backups, and firmware
Two short, concrete points from my experience:
- Passphrase (the so-called 25th word) changes which addresses derive from your seed phrase. Use it only if you fully understand the recovery implications; a lost passphrase means lost funds.
- Keep a physical backup: metal plate backups survive fire and water far better than paper. Consider Shamir backup (SLIP-39) if you need split-key recovery.
Always backup your seed phrase during setup and verify it. Before any firmware update back up your seed phrase and confirm you can restore using restore-recovery. Firmware updates fix bugs and improve security; update only via the official manager and verify release notes: see how-to-update-firmware-steps.
Who this hardware wallet is for — and who should look elsewhere
Who it’s for:
- People who want mobile-friendly self-custody with on-device verification and passphrase support.
- Holders who regularly move small to medium amounts of XRP and want a balance of security and convenience.
Who should look elsewhere:
- Users who require fully air-gapped signing workflows every time (no Bluetooth and no USB). If you need strict air-gapped only setups, consider other models or additional tools.
- People who prefer multi-account custodial features without managing tags — a custodial platform may be easier (but it’s not self-custody).
If you want multisig or advanced custody strategies, read multisig-setup-compatibility and multisig-setup.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes — with your recovery seed phrase you can restore to another compatible hardware wallet or supported software wallet. See restore-recovery.
Q: What happens if the company goes bankrupt?
A: Your private keys and seed phrase are yours. Hardware wallet makers going out of business doesn’t erase funds if you have your seed phrase. Still, test recovery on another supported wallet ahead of time (a small test amount).
Q: Is Bluetooth safe for a hardware wallet when sending XRP?
A: Bluetooth adds a wireless layer and a small attack surface. For day-to-day use many users accept that trade-off for convenience; others prefer USB-only workflows. Choose according to your threat model. See connectivity-security.
Conclusion & next steps
Destination tags are a small part of XRP that cause outsized confusion. Verify addresses on-device, never skip the tag if a recipient requests one, and keep firmware and companion apps up to date. In my testing these steps cut down mistakes dramatically.
Want guided setup or more troubleshooting? Check the full device setup guides and firmware pages: nano-x-setup, how-to-update-firmware-steps and troubleshooting-general.
