Memos, tags and destination fields
Some networks send many customers' deposits to one shared address and use a memo, tag or destination field to say which customer a payment belongs to. This page explains what the field does, why it exists, and what happens when it is omitted.
Block 02What the field actually does
The memo or tag is not a fee, not a password and not an amount — it is a label carried inside the transaction that lets the receiving system route the deposit to the right account. When the operator's system sees the deposit, it reads the identifier and credits the matching balance. The transaction itself, the amount and the destination address are all independent of the label; the label only answers the question the shared address cannot: whose is this?
Block 03If you omit the field
If you send to a shared address without the memo, the funds still arrive — the ledger records a valid transfer to the operator's address — but nothing in the payment says whose deposit it is, so it is not credited and sits unattributed. Recovery is possible but slow: you open a support case, prove the transfer was yours, and the operator matches it manually. It is one of the few crypto mistakes that is routinely recoverable, precisely because the funds are at the operator and not at a stranger, but it depends on a human on both ends.
Recoverable, but not automatic
An unattributed deposit is not lost to a stranger — it is at the operator, waiting for a human to match it to you. That is why this mistake is annoying rather than fatal, and why it still costs time.
Block 04What the field is called
The same idea goes by different names on different networks — a destination tag, a memo, a note, a comment, an identifier — and each network implements it a little differently. Some carry it as a required field for certain addresses; others treat it as optional. The name does not matter as much as recognising it: whenever a deposit form shows a second short field beside the address, that field is the identifier, and leaving it blank is the omission this page is about.
| Field shown | What it is | Consequence of omitting |
|---|---|---|
| Destination tag | Per-customer identifier | Deposit unattributed |
| Memo | Per-customer identifier | Deposit unattributed |
| Note / comment | Per-customer identifier | Deposit unattributed |
| None shown | Unique address per customer | Nothing to omit |
Block 05When there is no memo field
Many networks avoid the problem entirely by giving each customer a unique deposit address, so the address itself is the identifier and there is no separate field to forget. If the deposit form shows one address and no second field, there is nothing to omit — the attribution is built into the address. The trap only appears on networks that use shared addresses, and knowing which model an operator uses tells you whether the second field matters at all.
The second field is optional formatting.
On a shared address it is the only thing identifying the deposit as yours.
Block 06A memo checklist
The field is easy to handle once its purpose is clear.
- Is there a second field? If the deposit form shows one, it is required on that network.
- Is the address shared? A shared address is exactly when the identifier matters.
- Copy it exactly The identifier must match character for character, like an address.
- Keep the transaction id If a deposit goes unattributed, the tx id is what support needs to match it.
Why finality is a plain refusal
A memo is recoverable because the funds are at the operator. A wrong address is not. The irreversibility page explains why.
Affiliate disclosure and risk warning
Every affiliate link on this page and in the header is a sponsored link to a partner operator, and we may be paid if you open an account through it, at no extra cost to you. That link pays us; it does not make a transfer safer, it does not improve any decision, and it is never a recommendation to play or to move money. Nothing on this page is legal, financial or investment advice, and nothing here is a view on any coin, token or network. 18+ only. Gambling is a real risk of real loss, and a crypto transfer is a real transfer: it settles on a public ledger where there is no chargeback, no reversal and usually no way to recover funds sent to a wrong address or the wrong network. A deposit you make is not a bet, but it becomes money at risk the moment it is credited, and the price of the asset you hold can fall — sometimes to nothing — while it sits there. The mechanics explained here — how many confirmations a deposit needs, what a chain reorganisation can undo, why an address is screened, which fee belongs to the network and which to the operator, why a memo field matters and why finality is a probability rather than a guarantee — belong to the networks and the operators, not to any suggestion that you should use them. The rules that govern these products — whether crypto is accepted at all, which assets and networks are supported, whether the operator is licensed, what is owed on winnings, how deposits are screened and whether any of it is lawful for you — differ between countries, states and provinces, they change, and they depend on facts about you that a website cannot know. Nothing on this page is advice, a prediction or a valuation of any asset. Never stake money you cannot afford to lose, never borrow to play, and never chase losses with a larger stake. Gambling can cause serious financial harm, including debt and damage to relationships and mental health. Free and confidential support is available in most countries through national gambling-harm helplines, for players and for the people around them.