Address with Tag or Memo

Overview

An address with a tag or memo is a payment destination that requires both a shared blockchain address and an additional identifier to route funds to the correct account. The blockchain transfers funds to the common address, while the receiving exchange or service uses the destination tag, memo, payment ID, or message to credit the user. The tag is not part of the private key or blockchain address and can be mandatory even when the base address is valid.

Operational risks include omitted or incorrect tags, unsupported memo formats, reused identifiers, exchange processing delays, wrong-network deposits, and mistaken manual recovery.

Checkout and deposit systems should present address and tag separately, validate format, include them in QR or URI data, preserve both values, and warn users before submission.

For Address with Tag or Memo, the operational boundary with Destination Tag and Memo-Based Matching should be explicit. Identifiers for Address with Tag or Memo should connect those records without allowing either linked status to overwrite its own state.

For Address with Tag or Memo, attribution is separate from transaction validity. When Address with Tag or Memo interacts with Destination Tag, a valid transfer can still be unusable when a required memo is missing, the address belongs to another customer, the amount is intended for a different order, or the address has been retired. In the relationship between Address with Tag or Memo and Memo-Based Matching, records should preserve address assignment, memo or tag, derivation or provider reference, activation and revocation times, transaction identifier, block context, and the rule that produced the internal credit.

For Address with Tag or Memo, address lifecycle controls should include generation limits, key or custodian security, monitoring health, rotation or revocation, late-arriving deposits, unsupported-token handling, and reconciliation between blockchain receipts and internal balances. When Address with Tag or Memo interacts with Destination Tag, reusable addresses need stronger privacy and attribution controls than single-use addresses because several payments can reach the same destination over time.