Forgot a Crypto Memo or Destination Tag: Where the Funds Sit

Why an exchange asks for a memo or destination tag

A typical Bitcoin or Ethereum address is unique: the network already knows whom to credit. For XRP, XLM, ATOM, EOS, TON, and several other networks, a large exchange often uses one deposit address for thousands of customers. To tell your transfer from someone else's, the platform issues an extra label: a Destination Tag on XRP, a Memo on Stellar and Cosmos-style networks, a comment/memo on TON. On-chain, the tag is a hint for the platform's ledger, not a second address.

XRPL documentation is explicit: source and destination tags do not change how the ledger books the payment; they tell an off-ledger system whom to credit. If the exchange enabled a require-tag setting, the network may reject a payment with no tag. If it did not, the transfer can succeed while crediting a customer balance remains a manual support task. That is not theft and not a network failure.

Most mistakes come from the interface: copying only the address, missing the second field, reusing an old tag from notes, or mixing a tag from another network. A normal ERC-20 or TRC-20 deposit to a unique address does not need a memo — do not assume every coin has that field. How to read the transfer itself is in what a TxID is and how to read a blockchain explorer.

First steps if the transfer already went out

1. Do not send a second deposit "to see if it arrives" — that is a separate amount and a separate review.
2. Find the TxID in the sending wallet's history; without the hash, the exchange is searching a shared-address stream blind.
3. Open the network explorer and save a screenshot: sender, recipient, amount, confirmation status, and the memo/tag field (empty or wrong).
4. Open one official ticket with the receiving exchange: network, amount, time, TxID, account ID, explorer screenshot.
5. Put in the subject that the deposit has a missing or incorrect memo/tag — large platforms often route that as its own request type.
6. Do not hand over a seed phrase or pay a middleman who promises to credit faster than support.

Then wait for manual matching. Large exchanges publish procedures for deposits with a wrong or missing tag; a small cash desk may have no such process at all. Credit, a return to the sender, or a refusal is the platform's decision, not an automatic right. While the ticket is open, do not create duplicates. If a balance that was credited is now frozen, that is a different checklist: frozen crypto: what to do.

What the chain shows versus what the account shows

In the explorer the transfer succeeded: the coins are at the exchange deposit address. In the account there is no balance, because the internal system matches incoming transfers by tag, not by sender address. The funds sit on the omnibus address until staff match the TxID to your account or run a return under the platform's rules.

Do not confuse this with an AML pause: here the platform often does not know whose deposit it is, rather than disputing the coins' risk. Do not confuse it with theft either: you did not give up a key; you sent to the correct address without a field the exchange treats as required. If support is quieter than that platform's usual window, escalate with the same TxID rather than rewriting the story. Ticket and restriction support sit in exchange account unfreezing; examples without promised outcomes are in case studies.

How not to repeat the mistake

• Copy the address and tag from the current deposit session, not from old notes: tags can be reissued.
• Match the network: an XLM memo is not an XRP destination tag.
• On an unfamiliar network with two fields, a test amount before the main transfer is reasonable.
• Do not search for a "universal memo" — the tag is personal.

If the transfer went to someone else's personal address rather than an exchange, an exchange ticket will not help: the recipient is whoever owns the address in the TxID. Then the only conversation is with them. An exchange is not obliged to hunt a third-party payment that never arrived at its deposit address.