Today we are releasing XRP Ledger destination tag support in the address book in Ripple Custody (Wallet).
Address book entries for the XRP Ledger can now include an optional destination tag alongside the r-address. Ripple Custody (Wallet) now treats multiple counterparties that share the same r-address but differ by destination tag as distinct entries across lookup, policy evaluation, and transaction history.
Destination tags are optional 32-bit unsigned integers (0 to 4,294,967,295) used to identify a specific counterparty at a shared XRP Ledger r-address.
Exchanges routinely use a single XRP Ledger r-address for many customers, relying on the destination tag to route incoming funds. Without destination-tag awareness, two distinct counterparties sharing the same r-address appeared as one entry, causing address book conflicts and mislabeled transaction history.
- Optional destination tag field — When adding an XRP Ledger address, enter a destination tag to identify a specific counterparty at a shared r-address. Leave it empty for tagless addresses.
- Exact-match lookup — The r-address and destination tag are matched together. A tagless entry is distinct from any entry with a tag.
- Distinct counterparties on a shared r-address — Multiple address book entries can share the same r-address when paired with different destination tags.
- Accurate transaction attribution — New transactions display the counterparty whose r-address and destination tag exactly match the transaction's destination.
- Backward compatible — Existing tagless address book entries continue to work without change. Ripple Custody (Wallet) doesn't backfill historical transactions.