Memos and Destination Tags

How the XRP Ledger attaches extra payment context, and why destination tags are a frequent source of costly mistakes.

The problem: one address, many senders

Many services — most commonly centralized exchanges — use a single XRPL address to receive deposits from all of their customers, rather than generating a unique address per user. Since the XRPL doesn't natively support "sub-accounts" the way some systems do, these services instead rely on an extra field to identify which customer a given incoming payment belongs to.

Destination tags

A destination tag is a numeric field that can be attached to a payment, intended to let the receiving party (typically an exchange) identify which of its internal customer accounts a deposit is meant for. If a service requires a destination tag for deposits and you omit it (or enter the wrong one), your funds may still arrive at the correct address on-ledger, but the receiving service may have no way to credit them to your account — potentially requiring a manual, sometimes lengthy, support process to recover, or in the worst case resulting in permanent loss if the service has no reliable way to identify the depositor.

X-addresses as a mitigation

As mentioned in Addresses, Key Pairs, and Cryptography, the newer X-address format encodes the destination tag directly into the address string, so a wallet that fully supports X-addresses can reduce the risk of a sender copying the address correctly but forgetting the separate tag field.

Memos

Separately from destination tags, the XRPL also supports attaching one or more memo fields to a transaction — arbitrary data, typically used to record a short note, reference number, or application-specific metadata alongside a payment. Unlike destination tags, memos are not used by most exchanges to route deposits; they're a general-purpose way to attach human- or machine-readable context to a transaction.

Why this data lives on-ledger

Because both destination tags and memos are included directly in the transaction data stored on the public ledger, they're visible to anyone who looks up that transaction via a block explorer — useful for recordkeeping and dispute resolution, but also a reminder that memo content is not private, and shouldn't be used to record sensitive information.

Practical takeaway

If you're sending XRP to an exchange, wallet service, or any address that isn't a personal wallet you control directly, always check whether a destination tag is required, and copy it exactly — this single step prevents the large majority of "my deposit didn't show up" support tickets across the ecosystem.