Encyclopedia Stablecoins · Entry 299
Stablecoin deposit memos and destination tags
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Purpose | A memo can carry transaction-identifying information beyond the destination address. | [1] |
| Attribution | A custodial service can use an extra field to distinguish customers sharing an address. | [2] |
| Requirement | A field optional to a protocol can still be mandatory for a specific deposit workflow. | [1][2] |
The address and the account identifier solve different problems
The destination directs a transfer on the network. An extra identifier can tell a custodial service which internal customer should receive credit. The chain does not necessarily know that internal customer record.
Imagine two customers instructed to use the same receiving address but different identifiers. Sending to the correct address with the other customer’s identifier is still an attribution error.
Do not assume every stablecoin transfer needs a memo
Some services use unique deposit addresses instead. Stellar also supports multiplexed-account approaches, so a memo is not the only way to represent pooled account attribution. Use the current receiving instructions rather than a rule copied from another network.
Treat the identifier as exact data. Its required type and format matter. A payment note typed into a wallet’s private notes field is not necessarily placed in the transaction field the receiver expects.
Gather evidence before seeking correction
If a deposit is missing a required identifier, record the chain, asset, transaction reference, amount and receiving account. Contact the recipient service through its verified support channel to learn whether it can correct the attribution.
A successful chain status does not guarantee recovery, and making a second payment does not edit the first. Never provide a seed phrase or private key as deposit evidence.
Direct answers
Questions people ask
Should I put my name or other personal information in a memo?
Only use the exact receiving instructions needed for the transaction. Memos on public chains can be visible to others; they are not a private channel for identity documents or account credentials.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
A memo or destination tag can identify the customer behind a shared custodial receiving address. Whether it is required depends on the network, asset and receiving service. Copy the service’s complete deposit instructions; an on-chain transfer can succeed while the service cannot automatically assign it to your account.
Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T19:26:58.461Z.
Link to this claimPurpose: A memo can carry transaction-identifying information beyond the destination address.
Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T19:26:58.461Z.
Link to this claimAttribution: A custodial service can use an extra field to distinguish customers sharing an address.
Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T19:26:58.461Z.
Link to this claimRequirement: A field optional to a protocol can still be mandatory for a specific deposit workflow.
Scope: Stablecoins · data through 2026-10-02. Verification: verified · 2026-10-02T19:26:58.461Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
On the Follow a stablecoin payment path · Learn next: Stablecoin sent but not credited: a diagnostic guide
Source register
Sources and references
Retrieval dates and locators are recorded individually.- MemosStellar Development Foundation
Transaction memo use for off-chain recipient attribution; a memo is not a secret.
Locator: Memo; memo types; muxed accounts; transaction attributes · Version / scope: Document retrieved 2026-10-02; content hash recorded · Retrieved: 2026-10-02T18:52:47.147ZOpen source - Deposit pending: memo not includedCoinbase
Custodial shared-address attribution and missing-memo consequences; asset support must be checked separately.
Locator: What is a Destination Tag/Memo?; why needed · Version / scope: Document retrieved 2026-10-02; content hash recorded · Retrieved: 2026-10-02T18:51:59.961ZOpen source - Steps to receive cryptoCoinbase
Supported asset/network pair, recipient details and conditional memo requirements.
Locator: Receive crypto; network and memo selection · Version / scope: Document retrieved 2026-10-02; content hash recorded · Retrieved: 2026-10-02T18:52:00.787ZOpen source - Ethereum security and scam preventionethereum.org contributors
Address checking, malicious token and phishing risks; examples are educational.
Locator: Wallet security; common scams · Version / scope: Document retrieved 2026-10-02; content hash recorded · Retrieved: 2026-10-02T18:51:08.783ZOpen source - Why digital privacy mattersethereum.org contributors
Supports the public-ledger privacy limitation; does not establish a private transaction or universal privacy guarantee.
Locator: Privacy can be the default: public and transparent ledger · Version / scope: Document retrieved 2026-10-02; content hash recorded · Retrieved: 2026-10-02T19:25:01.807ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Stablecoin deposit memos and destination tags.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/stablecoin-deposit-memos/