Sent Crypto Without a Memo or Destination Tag? What to Do Next

A missing memo or destination tag is one of the most frustrating crypto mistakes because the transfer can be confirmed on-chain while your exchange balance still shows nothing.

That does not always mean the funds are gone.

But it does mean you need to stop guessing and follow the exchange's official recovery path before you make the situation worse.

Short answer

Why memos and destination tags exist

Many exchanges use one shared deposit address for some assets and rely on a memo, destination tag, or payment ID to route the deposit to the right customer.

Coinbase says this extra field is required for certain assets because it lets the platform route deposits from one shared address to the correct account. Kraken gives the same practical warning: omitting or entering an incorrect tag or memo can prevent a deposit from being credited.

That is why this problem shows up most often with exchange deposits for assets such as XRP, XLM, ATOM, EOS, STX, HBAR, and similar chains.

First: separate a memo mistake from a network mistake

These are not the same problem.

• Missing memo/tag: the blockchain transfer may be valid, but the receiving exchange cannot automatically assign it to your account.
• Wrong network: the receiving platform may not support the chain you used at all.

If you are not sure which mistake happened, start with the block explorer and compare:

1. the asset;
2. the network;
3. the destination address;
4. whether a memo/tag field was used.

If you need the broader troubleshooting path, read Sent Crypto but It Is Not Showing? Wrong Network vs Wrong Wallet Support.

What Coinbase says to do

Coinbase's memo and destination-tag guidance is clear on two points:

• when sending to Coinbase, you must include both the correct address and the correct memo or destination tag when required;
• when sending from Coinbase to another platform that requires a memo/tag, failure to include it can mean the destination does not receive the funds properly.

Coinbase also says memos generally are not needed when sending to a private self-custody wallet, because that address belongs uniquely to you.

For a bad inbound transfer to Coinbase, the practical move is to contact Coinbase support and have the transaction hash ready. Coinbase Exchange also warns that deposits missing a required memo may not be recognized.

What Kraken says to do

Kraken's recovery documentation is more explicit than most exchanges.

Kraken lists missing or incorrect tag/memo as a standard deposit-recovery category, says recovery is not guaranteed, and publishes the usual fee range by recovery type. For missing or incorrect memo/tag cases, Kraken says the recovery may only require a network-fee charge, which is better than the larger fees attached to unsupported-token cases.

Kraken's practical sequence is:

1. identify the mistake;
2. contact support with the TxID, asset, amount, deposit address, and time;
3. provide screenshots or other documentation if requested.

That is useful because it tells you this is often a support-and-verification problem, not necessarily a permanent-loss problem.

What Binance says to do

Binance has a dedicated wrong or missing tag/memo recovery flow.

Its support documentation says tag/memo recovery is generally for:

• deposits into Binance accounts with a wrong or missing tag/memo;
• coins or tokens that are already listed on Binance;
• networks where a single shared address uses a memo to distinguish users.

Binance also warns about two important limits:

• recovery can involve a fee, usually the relevant crypto transaction fee;
• after review, the recovered deposit is generally returned to the original sender address rather than simply credited however you prefer.

If you withdrew from Binance to another platform and used the wrong memo/tag there, Binance says to contact the receiving platform instead.

When a missing memo is less serious than it looks

A lot of panic comes from treating every missing-balance problem like a total loss.

A memo mistake can be more recoverable than a true wrong-address or wrong-network mistake because the funds may have reached infrastructure the exchange already controls. The problem is account matching, not necessarily chain ownership.

That is still not a reason to relax. If you used the wrong memo or destination tag, there is a worse-case scenario where the exchange cannot confidently assign the funds to you, or the deposit may have been associated with another account. That is why speed matters: open the official recovery path quickly and keep the transaction details ready.

What not to do

Do not:

• send another transfer just to "see if it works";
• trust Telegram or Discord recovery helpers;
• enter your seed phrase into a website that promises exchange deposit recovery;
• assume that because the address was right, the exchange will fix everything automatically;
• confuse a missing memo with a wallet problem if the destination was an exchange.

If the original transfer may also involve a copied or poisoned address, review Address Poisoning Scams and Clipboard Hijacking in Crypto before making another attempt.

How to avoid this next time

Use the slow checklist:

1. start from the receiving exchange's deposit page, not from an old screenshot;
2. read the asset and network label in full;
3. check whether the page shows a memo, destination tag, or payment ID;
4. copy both the address and the memo/tag when required;
5. send a small test first.

This matters most when moving funds from an exchange into another exchange account or from a wallet into an exchange deposit address. If you are moving into self-custody instead, the safer long-term habit is to start from the wallet receive flow and verify everything before you withdraw. Our guide on How to Move Crypto from an Exchange to a Hardware Wallet Safely walks through that process.

Bottom line

A missing memo or destination tag is not the same as a wrong-network disaster.

It often means the exchange cannot automatically match a real deposit to your account. That is bad, but sometimes recoverable.

The safest path is simple: check the explorer, confirm the chain, use only the receiving platform's official memo/tag recovery path, and keep the transaction hash ready.