What Is a Destination Tag (and Memo Field) in an XRP Transaction?

Two fields on an XRP transaction get confused with each other constantly: the destination tag and the memo field. They're both optional numbers/data attached to a payment, but they do genuinely different jobs — and confusing them is a real, common way people lose track of funds.

The destination tag

Many exchanges and other services don't give each user their own unique XRP deposit address. Instead, they use one shared address for all users, and rely on a destination tag — a number you include with your payment — to identify which specific internal account the deposit belongs to. If a service requires a destination tag and you send without one (or with the wrong one), your funds arrive at the right address but with no way for the service to know it's yours. Depending on the service, this can mean a delayed credit, a support ticket, or in the worst case, permanently unrecoverable funds. See our guide on what happens when a transaction goes wrong for more on that risk.

Not every destination requires a tag — a personal wallet address usually doesn't need one at all, since it's not shared across multiple users the way an exchange's deposit address typically is. Whether you need one depends entirely on where you're sending to; always check the specific recipient's instructions.

The memo field

The memo field is something else entirely: an optional piece of arbitrary data you can attach to any XRPL transaction, used for things like reference notes, invoice numbers, or application-specific metadata. Unlike a destination tag, a memo generally isn't used by exchanges to route a deposit to the correct account — it's just extra data riding along with the transaction, readable by anyone who looks the transaction up (memos aren't private or encrypted).

Why the mix-up matters

Because both are optional numeric-ish fields attached to a payment, it's easy to assume they're interchangeable or that filling in one covers the other. They don't. If a service requires a destination tag specifically, putting the same number in a memo field instead won't accomplish anything — the service is checking the destination tag field, not scanning memos for a number.

Where this shows up on this site

Our QR Code Generator has a dedicated destination tag field, separate from the amount — worth using deliberately if you're generating a QR code for a deposit to an exchange or service that requires one. Always confirm the exact tag required directly from the recipient rather than guessing.

Related reading

For the broader checklist of things worth verifying before sending any payment, see How to Verify an XRP Wallet Address Before Sending Funds.