# Stablecoin deposit memos and destination tags 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. Evidence: [Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions); [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included); [Steps to receive crypto](https://help.coinbase.com/en/coinbase/trading-and-funding/cryptocurrency-trading-pairs/steps-to-receive-crypto) Canonical: https://degreesofsatoshi.com/encyclopedia/stablecoin-deposit-memos/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:26:58.461Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Purpose:** A memo can carry transaction-identifying information beyond the destination address. ([Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions)) - **Attribution:** A custodial service can use an extra field to distinguish customers sharing an address. ([Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included)) - **Requirement:** A field optional to a protocol can still be mandatory for a specific deposit workflow. ([Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions); [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included)) ## 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. Evidence: [Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions); [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included) ## 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. Evidence: [Steps to receive crypto](https://help.coinbase.com/en/coinbase/trading-and-funding/cryptocurrency-trading-pairs/steps-to-receive-crypto); [Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions) ## 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. Evidence: [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included); [Ethereum security and scam prevention](https://ethereum.org/en/security/) ## Questions ### 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. Evidence: [Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions); [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included); [Why digital privacy matters](https://ethereum.org/en/privacy/) ## Claims and scope ### stablecoin-deposit-memos-quick-answer 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: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-deposit-memos-fact-purpose Purpose: A memo can carry transaction-identifying information beyond the destination address. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-deposit-memos-fact-attribution Attribution: A custodial service can use an extra field to distinguish customers sharing an address. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ### stablecoin-deposit-memos-fact-requirement Requirement: A field optional to a protocol can still be mandatory for a specific deposit workflow. Scope: {"collection":"stablecoins","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Memos](https://developers.stellar.org/docs/learn/fundamentals/transactions/operations-and-transactions) — Stellar Development Foundation. Transaction memo use for off-chain recipient attribution; a memo is not a secret. Locator: Memo; memo types; muxed accounts; transaction attributes. Retrieved: 2026-10-02T18:52:47.147Z. - [Deposit pending: memo not included](https://help.coinbase.com/en/exchange/crypto-transfers/memo-not-included) — Coinbase. Custodial shared-address attribution and missing-memo consequences; asset support must be checked separately. Locator: What is a Destination Tag/Memo?; why needed. Retrieved: 2026-10-02T18:51:59.961Z. - [Steps to receive crypto](https://help.coinbase.com/en/coinbase/trading-and-funding/cryptocurrency-trading-pairs/steps-to-receive-crypto) — Coinbase. Supported asset/network pair, recipient details and conditional memo requirements. Locator: Receive crypto; network and memo selection. Retrieved: 2026-10-02T18:52:00.787Z. - [Ethereum security and scam prevention](https://ethereum.org/en/security/) — ethereum.org contributors. Address checking, malicious token and phishing risks; examples are educational. Locator: Wallet security; common scams. Retrieved: 2026-10-02T18:51:08.783Z. - [Why digital privacy matters](https://ethereum.org/en/privacy/) — ethereum.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. Retrieved: 2026-10-02T19:25:01.807Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees 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/