Sent Crypto but It Is Not Showing? Wrong Network vs Wrong Wallet Support

A crypto transfer can be fully confirmed on-chain and still look missing in the app you are staring at.

That does not automatically mean the coins vanished.

In practice, four problems get mixed together:

1. you sent the asset on the wrong network;
2. the destination wallet or exchange does not support that token/network the way you expected;
3. the transfer needed a memo or tag and did not get credited;
4. the funds are on-chain, but your current wallet interface is not showing them.

The first job is to figure out which problem you actually have before you do something worse, like retry the transfer or enter your recovery phrase into a random website.

Short answer

1. Start with the transaction hash, not the app balance

Before you assume anything is lost, find the transaction hash and open the relevant block explorer.

You want to confirm four boring details:

• the asset;
• the network;
• the destination address;
• whether the transaction is actually confirmed.

This matters because a wallet app can fail to display funds while the blockchain record is perfectly normal.

If the explorer shows the funds at the address you control, the next question is not "where did the crypto go?" It is "which wallet or exchange interface can actually read that network and asset correctly?"

2. Wrong network and unsupported wallet support are not the same thing

People often say "I sent it on the wrong network" when they really mean one of two different things.

Case A: the destination did not support that network

This is the dangerous version.

Coinbase's withdrawal guidance says you must confirm you are using the correct supported network before withdrawing, because funds sent to an unsupported or incorrect network may be permanently lost and Coinbase cannot recover them through the normal withdrawal flow.

Kraken's withdrawal guide says the same thing more bluntly: always choose the same network the receiving wallet uses, because incompatible-network withdrawals can cause permanent loss.

Binance's deposit guidance gives the same warning for inbound transfers: if you choose the wrong deposit network, funds might be lost and may not be recoverable.

If the destination platform did not support the network you used, do not send another test transaction until you know the platform's recovery policy.

Case B: the address is still yours, but your current wallet app does not support the asset view you expected

This is the more survivable version.

Coinbase's self-custody guidance for unsupported assets explains that the assets remain yours even if the current app no longer supports viewing or transacting with that network. Its documented solution is to import the recovery phrase into another self-custody wallet that supports that network.

Ledger's ERC20 support guidance also makes an important distinction: if you send ERC20 tokens using the wrong network type, they may not appear in the Ledger app view you expected. In other words, "not visible in this app" is not always the same as "gone forever."

That is why you should separate ownership from app support.

3. Exchange mistake: recovery may be possible, but it is not guaranteed

If the funds were sent to a centralized exchange, recovery depends on that exchange's tooling and policy.

Coinbase

Coinbase documents an asset-recovery service for certain unsupported assets and networks. When a transfer is eligible, Coinbase lets the customer enter the transaction details and send the recovered funds out to a self-custody wallet. Coinbase also warns that only certain assets and networks are eligible, that ineligible recovery attempts fail, and that fees can apply.

That means a wrong-network or unsupported-asset mistake is sometimes recoverable there, but not automatically and not for every asset.

Kraken

Kraken's deposit-recovery guidance is unusually specific. It lists common mistakes such as unsupported tokens, incorrect networks, missing memo/tag data, expired deposit addresses, and deposits to operational hot-wallet addresses. It also says recovery is not guaranteed and publishes a fee schedule for some recovery types.

Kraken even separates lighter cases from harder ones:

• a missing memo/tag may only require a network-fee recovery;
• unsupported tokens on supported networks can carry a larger manual-recovery fee;
• unlisted assets on unsupported networks can be even harder and more expensive.

That is useful because it tells you the outcome depends partly on how compatible the mistaken transfer still is with Kraken's infrastructure.

Binance

Binance's incorrect-deposit FAQ says missing or wrong memo/tag deposits can use a recovery flow, and some unlisted-token mistakes may show a self-service retrieval option. It also warns that recovery is not guaranteed, and that sending to a wrong address that does not belong to Binance is outside what Binance can fix.

So the practical rule for exchange mistakes is:

check the exchange's official recovery path first, because the answer may be "supported recovery," "manual paid recovery," or "not recoverable."

4. Self-custody mistake: sometimes the fix is a different wallet interface, not a refund request

If you sent funds to an address controlled by your own recovery phrase, the blockchain does not care which app you prefer.

What matters is whether the same keys can be accessed through a wallet that supports the asset and network correctly.

That is why Coinbase's unsupported-asset wallet guidance tells users to import the recovery phrase into another self-custody wallet that supports the network. The assets remain on-chain. The problem is interface compatibility.

This is also why some Ledger users think a transfer failed when the issue is really that:

• the token lives under an ETH/EVM account they have not opened properly;
• the wallet app needs the relevant account added first;
• the current app view does not show that token/network combination the way they assumed.

If the destination was your own wallet address, compare the explorer result with the receive address you expected. If they match, your odds are better than if the destination was an exchange address on an unsupported network.

If the balance is still confusing after recovery or import, read Restored Hardware Wallet but Balance Is Zero?, because wallet-view problems and transfer problems can overlap.

5. Missing memo or tag is a different problem from a wrong network

A missing memo/tag can look like a lost transfer even when the network itself was correct.

Kraken and Binance both document this explicitly: some assets need a memo, tag, or payment ID so the exchange can route the deposit to the correct user account. Without it, the funds may arrive at the exchange infrastructure but not get credited to your balance automatically.

That is why sending XRP, XLM, TON, or similar assets to an exchange deserves an extra pause.

Use this rule:

• wrong network = the chain itself may be incompatible;
• missing memo/tag = the chain may be correct, but the platform cannot match the deposit to you.

Both are expensive mistakes, but they are not the same troubleshooting path.

6. What not to do while you troubleshoot

When people panic, they create a second disaster.

Do not:

• keep resending small amounts blindly;
• trust Telegram, Discord, or search-ad "recovery experts";
• enter your seed phrase into a website because a forum post suggested it;
• assume the cheapest network option is interchangeable with the receiving wallet's network;
• confuse "same ticker" with "same chain" for USDT, USDC, ETH-wrapped assets, and exchange deposit options.

If you suspect the destination address itself may be wrong, stop and review Address Poisoning Scams and Clipboard Hijacking in Crypto before trying again.

7. How to reduce the chance of this happening again

The best prevention is boring:

1. start from the destination wallet or exchange deposit page;
2. read the network label in full;
3. check whether a memo/tag is required;
4. send a small test first;
5. only then move the larger amount.

Our guide on How to Move Crypto from an Exchange to a Hardware Wallet Safely walks through that process in more detail.

If you are choosing a long-term wallet after this scare, the main decision is still usability vs verification discipline. A mobile-first wallet such as Tangem can make receiving feel simpler, while Ledger and Trezor can be stronger fits when you want device-screen verification. None of them make network labels optional.

If you still need a wallet shortlist after the recovery issue is resolved, use the Wallet Finder or compare best crypto wallet options for beginners.

Bottom line

A missing balance after a crypto transfer is not one diagnosis.

Sometimes the funds are truly stuck because the destination platform did not support the network. Sometimes the exchange offers a recovery tool. Sometimes the coins are still yours, but your current wallet app is the wrong window into them.

The safest order is:

check the explorer, confirm the network, confirm the destination type, use only official recovery paths, and never expose the recovery phrase just because the first app view looks empty.