Overview
Receiving crypto is usually passive: someone broadcasts a transaction to an address you control and a blockchain records it. Sending requires the device to sign a transaction, the wallet software to construct it correctly, and the network to accept and confirm it. Small gaps in any of those steps produce frustrating situations where the ledger wallet can receive coins but cannot send them.
I believe most readers are here because they saw a balance and then hit a Send button that failed. In my testing I’ve seen the same patterns repeatedly: unconfirmed inputs, missing native coin for fees, app mismatches, and connectivity issues (among others). Below I walk through the common causes, step-by-step fixes, and examples you can apply right away.
Why you can receive but not send
Here are the frequent root causes, with practical fixes.
Unconfirmed Bitcoin (mempool / UTXO issues)
Symptom: Your account shows incoming BTC but the wallet reports unconfirmed outputs or the transaction fails when attempting to spend.
Why it happens: Bitcoin uses UTXOs (unspent transaction outputs). If the UTXO you received is still unconfirmed (in the mempool), many wallets won’t allow spending it yet. That can be visible as "ledger wallet shows unconfirmed bitcoin" in searches.
Fixes:
- Wait for confirmations (usually the most reliable fix).
- If the original outgoing transaction is stuck due to low fee, check whether it was marked RBF (replace-by-fee). If so, you can bump the fee.
- Consider a child-pays-for-parent (CPFP) strategy from a wallet that supports it.
Related: see our guide on transaction failures and stuck transactions and bitcoin issues.
Insufficient native balance or chain reserves (XRP, ETH, SOL)
Symptom: You receive a token and see a balance, but the wallet won’t let you send. For example, searches sometimes read like "ledger ripple wallet can recieve but not send" (yes, that typo appears often).
Why it happens: Many blockchains require you to hold a minimum amount of the native coin to pay fees or to meet a network reserve. On some chains (XRP being a common example) there’s also an account reserve that prevents outgoing transfers until there’s sufficient native balance.
Fixes:
- Check the native coin balance required for fees or reserves. If insufficient, send a small amount of the native coin to the account so the device can sign and broadcast the outgoing transaction.
- For ERC-20 tokens, remember you must hold ETH for gas even if you have plenty of the token.
See a focused guide on ripple/xrp issues and ethereum / ERC-20 issues.
App, firmware, and account mismatches
Symptom: The device shows a balance but refuses to sign transactions or Ledger Live (or another manager app) reports errors.
Why it happens: The coin app on the device or the companion app on your computer/phone may be out of date. Or the account you’re viewing was created with a different derivation path or passphrase (the optional 25th word). If you used a passphrase when receiving, the device may be showing a different account than the one controlling the private keys.
Fixes:
Token transfers, gas, and smart-contract constraints
Symptom: You can receive an ERC-20 or SPL token but can’t send it.
Why it happens: Tokens rely on the chain’s native asset to pay gas. Also, some smart-contract tokens require an approval step or interact with contracts that increase gas complexity.
Fixes:
Connectivity, broadcasting, and wallet-state problems
Symptom: The device signs the transaction but it never shows up on the network, or the app times out.
Why it happens: USB/OTG or Bluetooth connections can fail. Companion apps may be out of sync with network nodes. Or the transaction construction failed client-side.
Fixes:
- Try a different USB cable, port, or host (desktop vs mobile). See usb-otg-bluetooth.
- Reopen the companion app and try again.
- If signing succeeds but the tx isn’t broadcasting, export the signed raw transaction carefully and rebroadcast via a block explorer or trusted node only if you understand the risks.
How to send from ledger: step-by-step checklist
- Confirm incoming transaction is confirmed on a block explorer (get the txid).
- Check native balance for fees/reserve; add native coin if needed.
- Update device firmware and the coin app. (firmware updates)
- Verify passphrase/hidden wallet status. (passphrase-25th-word)
- Reinstall the coin app if it behaves oddly. (apps-manager)
- Try sending a small test amount first.
- If a transaction is stuck, research RBF/CPFP or use our transaction failures guide.
- If everything else fails, follow the troubleshooting flowchart. (troubleshooting-flowchart)
And yes, testing with a small amount saves headaches.
Worked examples (progressive complexity)
Example 1 — Unconfirmed Bitcoin:
- Issue: "ledger wallet shows unconfirmed bitcoin" after a transfer. Action: wait for 1–6 confirmations; if stuck, check if original sender used low fees and ask them to enable RBF or use CPFP.
Example 2 — XRP receive but cannot send:
- Issue: "ledger ripple insufficient funds" frequently occurs because the account lacks the minimum native balance for an outgoing transaction. Action: send a small amount of native XRP to cover reserve + fee, then retry the send.
Example 3 — ERC-20 token stuck:
- Issue: Token balance visible but sending fails due to zero ETH for gas. Action: send a small ETH amount, then retry the token transfer.
These are simple, repeatable fixes. In my experience the majority of "can't send" tickets resolve with one of these steps.
Short comparison: Receiving vs Sending problems
| Symptom |
Typical cause |
Quick fix |
| Receive OK, cannot send |
Unconfirmed UTXO / insufficient native coin / wrong account |
Wait for confirmations / top up native coin / check passphrase |
| Send fails to broadcast |
Connectivity or companion app error |
Try new cable/host / update app |
| Transaction stuck in mempool |
Low fee or missing RBF/CPFP |
Bump fee (RBF) or perform CPFP |
Prevention & best practices
- Always keep firmware and companion apps updated. Small updates fix subtle signing bugs.
- Keep a small reserve of native coins in each account that you plan to use for outgoing transactions.
- Record whether you used a passphrase (25th word). Losing that record often looks like a balance that cannot be spent.
- Avoid buying hardware wallets from unofficial resellers (see buying safely resellers).
But don’t overcomplicate your setup unless you need multisig—most users are safer with a single hardware wallet plus good seed backup.
FAQ (real user questions)
Q: "Can I recover my crypto if the device breaks?"
A: Yes — recover from your seed phrase to another hardware wallet or a trusted software wallet. See recover from seed.
Q: "What if I see 'insufficient funds' when trying to send XRP?"
A: Verify the native coin minimum reserve and add a small amount of native XRP. See ripple-xrp-issues.
Q: "Is Bluetooth safe for a hardware wallet?"
A: Bluetooth increases the attack surface versus USB, but modern devices use secure channels. For high-value transfers I prefer USB (and sometimes air-gapped workflows).
Q: "Ledger cannot send funds — what next?"
A: Work through the checklist above, then consult troubleshooting-index and error codes index.
Conclusion & next steps
If you can receive but not send, start by checking confirmations and the native coin balance. Then move through firmware, app, and passphrase checks. What I’ve found is that patience plus a methodical checklist solves most cases.
Still stuck? Follow the troubleshooting flowchart or consult the specific guides linked above (Bitcoin, XRP, ERC-20). If the problem persists after those steps, collect the transaction IDs, device firmware version, and exact error text before reaching support — that information speeds up diagnostics.
For more setup and repair procedures see the setup guide, seed phrase management, and transaction failures. Good luck — and remember, small test transactions save big mistakes.
