SWAPARIO
ADDRESS IDENTIFIER GUIDE

Crypto memos, destination tags and payment IDs explained

Reviewed September 1, 2026 · Swapario editorial

SHORT ANSWER

A memo, destination tag or payment ID identifies a recipient inside a shared blockchain address. The address routes funds to a service; the extra identifier can route them to the correct customer account. Copy both fields exactly when the receiving wallet or exchange provides them.

01

Shared deposit addresses need an internal identifier

Custodial services can use one blockchain address for many customers. Networks such as XRP Ledger support destination tags, while other assets and services use memos or payment identifiers.

02

Use the identifier only when the receiver provides it

A self-custody wallet can have a unique address and need no tag. A custodial destination can require one. Never invent, shorten or reuse a tag from another account.

03

A missing tag can require manual crediting

The blockchain transaction can succeed while the receiving service cannot assign it automatically. Contact the destination service with the transaction hash and proof requested through official support.

CONCRETE EXAMPLE

Example: an XRP address and destination tag are two instructions

A custodial XRP destination may provide a classic address beginning with r and a numeric destination tag. The address reaches the service’s XRP wallet; the tag tells that service which internal balance should receive credit. An XRP X-address can encode both pieces, but the interface must explicitly support it. Other networks use different conventions: some memo-based chains request text or numbers, while older Monero workflows could use payment IDs or integrated addresses. Never invent an identifier—copy the exact field supplied for the selected payout or deposit.

CHECK THIS CASE

  1. 1Copy the address and extra identifier into their separate labeled fields.
  2. 2Confirm whether the interface expects a classic address or an encoded address format.
  3. 3If no memo or tag is supplied by the receiving wallet, do not add a random value.

ACTION CHECKLIST

Before you continue

  • Copy the address and identifier from the same deposit screen.
  • Check whether the extra field is required or optional.
  • Keep leading zeros when shown.
  • Review the final order details before sending.
  • Never reuse another customer’s tag.

FAQ

Questions about this topic

Is an XRP destination tag part of the address?+

With a classic address it is normally a separate number. An X-address can encode the address and tag together.

What if my own wallet does not show a tag?+

Do not add one unless the receiving wallet or service explicitly provides it.

Can support recover a deposit with a missing tag?+

The receiving service may be able to investigate, but recovery is not guaranteed and can require verification of the transaction.

RELATED ROUTES AND ASSETS

Continue with the exact intent

All guides

Educational information only. The live route, wallet instructions and provider notice shown for an exchange take precedence over general examples.