A crypto transfer can reach the correct platform address and still miss your account because one routing field was absent or wrong. Before you press Send, take the asset, network, current recipient address, and any displayed tag, memo, or comment from one fresh receiving screen. This crypto destination tag checklist shows when to stop, how X-address and M-address exceptions work, and what proof to save if credit fails.
Summary: Treat the receiver’s asset, network, address, and extra identifier as one route bundle. Copy every displayed field without guessing, then approve the transfer only if the wallet preview preserves that bundle. A successful blockchain transaction is not the final result: wait for account or order credit. If the identifier was missed, stop sending and give the receiving platform one complete evidence packet.
A destination tag or memo is an extra routing label. Some exchanges use one deposit address for many customers, then use that label to assign a payment to the right balance. TON interfaces may call it a Comment or Message. The current receiving screen decides whether you need one.
The rule is not “XRP, XLM, and TON always need a memo.” The receiver may show a separate ID, put it inside the address, or require no extra field. Follow the current route.
Decide from the receiving screen whether an extra ID is required
Open the Receive, Deposit, or active order screen of the service that should get the coins. Select the asset and network again. Do not start from withdrawal history, a saved screenshot, a chat message, or details from a previous transfer.
Look for the recipient address and a field labelled Destination Tag, Tag, Memo, Memo ID, Comment, Message, or Payment ID. If the receiver displays both and marks the second as required, both belong to this transfer. The address reaches the receiving system; the extra ID tells that system which balance or order gets credit.
- Extra field shown separately: copy it into the matching separate field.
- Receiver says the ID is included in the address: keep the address intact.
- No extra field shown for this route: do not add a random value.
- Instructions conflict or look unclear: stop and ask the receiving platform.
A self-custody wallet is one you control through its recovery phrase. Its unique address often needs no routing ID, but its instructions still win. Do: use the current screen. Don’t: assume every XLM transfer needs a memo.
Build one four-field route bundle before opening Send
Put four fields in one note: asset, exact network, current recipient address, and extra ID if displayed. “XRP” is the asset; “XRP Ledger” is the network. Save any order or request ID separately.
Workflow:
Current receiver screen → asset + network + address + extra ID → X-address or M-address check → wallet preview → test → blockchain success → account credit → main send or one recovery packet
- Open the current Receive, Deposit, or order screen for the intended account.
- Select the asset and exact network again.
- Copy the full recipient address from that screen.
- Copy the displayed tag, memo, comment, or other extra ID separately.
- Match the sending wallet’s network with the receiver’s network.
- Paste each value only into the field intended for it.
- Review the final preview before approving the transfer.
Do not append a tag to a classic address, remove leading zeroes, or translate a comment. For a new exchange, open the YBEX swap widget and use the recipient’s current details. Do: rebuild the bundle. Don’t: mix a fresh network with an old address or memo.
Handle XRP X-addresses, Stellar M-addresses, and TON comments correctly
Some address formats carry the ID inside the address. Never split or convert one by hand. Confirm that the sending wallet supports it.
Keep an XRP X-address intact
An XRP classic address may have a separate numeric Destination Tag. Copy its digits exactly. Never substitute text, zero, or another account’s tag.
An X-address packages a classic address and tag together. If both sides support it, paste it whole without a second tag. If the sender demands separate fields, ask for a supported route instead of converting it. See the XRP Ledger tag documentation.
Follow the displayed Stellar G-address or M-address route
Stellar has several memo types. The receiver sets the type; the sender does not choose one. A pooled G-address may need a specific memo. Copy the shown value.
A muxed M-address can carry the user ID, so a separate memo may not be needed. Support is not universal. Do not convert it or add an old memo. See the Stellar muxed account guide.
Copy a TON Comment or Message as routing data
A TON service may match a shared-wallet transfer to an invoice through a comment. Copy its exact case and spacing. If the app cannot send it, stop and ask for a supported route.
Do: preserve an X-address, M-address, or TON comment exactly. Don’t: unpack an encoded address or choose a memo type by guesswork.
Run the stop or go preview check without changing the identifier
The wallet preview shows what you are about to sign. Review it, not only the clipboard. Some apps hide optional fields or reject encoded addresses. If a required value is absent from the preview, the decision is Stop.
- Stop if the asset or network differs from the receiving screen.
- Stop if the wallet rejects the X-address or M-address.
- Stop if a required tag, memo, or comment has no matching field.
- Stop if any address or identifier character changed after paste.
- Go only when all four route fields match and both sides support the format.
Check the address beginning, middle, and end, then every ID character. Confirm that you did not swap a refund memo with a destination memo.
For a meaningful amount, consider a small test after checking the live minimum and cost. Use the same route and pass it only after account credit. See the test crypto swap checklist.
Do: cancel the preview when a required field is missing. Don’t: send “to see what happens” or assume the network will reject every missing tag.
Verify account credit, not only blockchain success
A blockchain explorer is a public receipt viewer. “Success” means the network accepted the transfer to the displayed address. It does not prove that an exchange assigned the payment to your internal account. That second step happens in the receiver’s records.
Find the transaction hash, or TXID; confirm network and destination in the explorer; wait for confirmations; then open the account or order. A test passes only when the expected asset is credited.
If the explorer is pending, wait. If it shows success but the balance is empty, compare all four route fields. After a test passes, reopen the receiving screen before sending the remainder.
Do: require visible account or order credit before increasing the amount. Don’t: use explorer success alone as the Go signal.
Send one complete recovery packet after a missing or wrong tag
If a required tag, memo, or comment was missing or wrong, stop. A second “corrected” payment does not repair the first.
Contact the receiver through its official site or app, not an inbound message. Manual credit may be possible, but recovery is not guaranteed. Do not assume a refund, deadline, or fee.
Send one ticket containing:
- The receiving account email or user ID, without a password or recovery phrase.
- The order or request ID, if the transfer belongs to an exchange order.
- The asset, exact network, exact amount, and date and time sent.
- The full destination address and TXID.
- The correct tag, memo, or comment shown by the receiver.
- The value entered, or a clear note that the field was empty.
- A withdrawal screenshot with unrelated balances and private data hidden.
For a YBEX route, use official YBEX support with the request ID and TXID. Never send a seed phrase, private key, password, or another payment as “proof.”
Do: send one accurate packet and wait for the case response. Don’t: open conflicting tickets or make another transfer to force credit.
Frequently asked questions
Is a destination tag the same as a memo?
They often perform the same routing job, but the label and format depend on the network and receiver. Copy the field exactly as shown. Do not rename or convert it.
Can XRP sent without a destination tag be recovered?
The receiver may be able to investigate and manually credit it, but recovery is not guaranteed. Stop sending, save the TXID, amount, correct tag, and order ID, then open one official case.
Does every XLM transfer need a memo?
No. A pooled G-address may require one, while an M-address can include the user ID. Follow the current receiving screen and check sender support.
Does TON use a memo or a comment?
The field may be called Comment, Message, or Memo. Paste the exact receiver-issued text. If your wallet cannot include it, stop and ask for another route.
Do BTC or ETH transfers need an XRP-style destination tag?
Usually not, but the receiving screen still decides the fields. Match asset, network, and address, and never add a random ID.
The explorer says Success but the exchange balance is empty. What should I do?
Compare the full route with the receiving screen. Save the TXID and order ID, then send the receiver one complete evidence packet. Do not resend.