Crypto memos and destination tags
Some services use a shared address and a separate memo or destination tag to identify a customer. Follow the destination’s exact instructions; address syntax alone cannot check crediting details.
Worked example
| Field | XRP Ledger example | Role |
|---|---|---|
| Destination account | r… shape, incomplete here | Ledger account receiving the transaction |
| Destination tag | Unsigned 32-bit value | Additional destination identification |
| Service instructions | Required / optional depends on receiver | Determines deposit-crediting workflow |
The address is only one field
A shared service account may receive funds for many customers. The tag can tell the service which customer to credit. A transaction can arrive on-chain without enough information for automatic customer attribution.
Read the receiving screen each time
Do not copy a tag from another account or infer it from an address. XRP Ledger tags and other systems’ memos are not interchangeable formats. If instructions are missing or inconsistent, resolve them with the receiving service before proceeding.
Common pitfalls
- This is a field explanation, not a complete XRP receiving example.
- A valid address does not prove the memo or tag is correct.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.