When transferring Stellar Lumens (XLM) or other assets on the Stellar network—especially to or from cryptocurrency exchanges—you may encounter additional fields beyond the standard wallet address: Memo_Text, Memo_ID, Memo_Hash, and Memo_Return. These memo types play a critical role in ensuring your funds reach the correct destination and are credited properly. Understanding how each works can prevent costly errors and lost funds.
This guide breaks down each memo type, explains when and why they’re used, and helps you avoid common pitfalls when sending XLM across wallets and platforms.
Why Memos Are Required on the Stellar Network
The Stellar blockchain supports high-speed, low-cost transactions, making it ideal for micropayments and cross-border transfers. However, unlike networks such as Bitcoin or Ethereum, Stellar includes an optional memo field in every transaction. This feature enhances transaction metadata and enables better fund routing—especially for centralized services like exchanges.
Exchanges often use a single deposit address for all users. To distinguish between deposits from different accounts, they require a unique identifier—this is where memos come in. Without the correct memo, your deposit might not be credited—or worse, could be lost permanently.
👉 Learn how to safely send XLM with the right transaction details
Types of Memo Fields in Stellar Transactions
1. Memo_ID
Memo_ID is a numeric identifier used primarily by exchanges. When you deposit XLM to platforms like Binance, Kraken, or OKX, you’ll often see a deposit address paired with a numeric memo (e.g., 123456789).
- Format: Unsigned 64-bit integer
- Use Case: Links your deposit to your exchange account
- Example: Sending XLM to Binance using address
GA5XIG...+ Memo_ID987654321
If you omit or mistype the Memo_ID, the exchange won’t recognize the incoming funds, and your balance won’t update—even though the blockchain confirms the transaction.
2. Memo_Text
Memo_Text allows users to attach a short text message (up to 28 characters) to a transaction. While less commonly required by exchanges, some platforms accept it for internal tracking or user notes.
- Format: UTF-8 string, max 28 bytes
- Use Case: Personal messages, internal labeling
- Example: Sending “Payment for domain” along with XLM
Some wallets display this text, allowing recipients to see context behind a transfer. It’s useful for peer-to-peer payments where clarification is helpful.
3. Memo_Hash
Memo_Hash is a 32-byte SHA-256 hash value encoded in hexadecimal or XDR format. It’s typically used in automated systems or smart contracts where a unique reference must be embedded securely.
- Format: 32-byte hash (64 hex characters)
- Use Case: Invoicing systems, escrow services, dApps
- Example: A payment processor generates a hash tied to an invoice ID
Because it’s encrypted and fixed-length, Memo_Hash ensures data integrity without exposing sensitive information.
4. Memo_Return
Less common than the others, Memo_Return is intended for refund scenarios. If a transaction fails or needs to be reversed, the sender can include a return memo so the recipient knows how to route the refund correctly.
- Format: Same as Memo_Hash (32-byte hash)
- Use Case: Failed payment handling, automated refunds
- Example: A decentralized exchange uses Memo_Return to send failed trade amounts back to users
While rarely used manually, this field supports advanced automation and improves reliability in complex financial workflows.
When Should You Use a Memo?
| Scenario | Memo Required? | Recommended Type |
|---|---|---|
| Sending XLM to an exchange | ✅ Yes | Memo_ID or Memo_Text |
| Sending XLM to your own wallet | ❌ No | Leave blank |
| Peer-to-peer transfer with note | Optional | Memo_Text |
| Automated dApp transaction | ✅ Sometimes | Memo_Hash |
| Refund setup for service | ✅ If supported | Memo_Return |
👉 Discover secure ways to manage your Stellar transactions today
Common Mistakes & How to Avoid Them
- Forgetting the Memo Entirely
One of the most frequent causes of uncredited deposits. Always double-check whether the receiving platform requires a memo. - Using the Wrong Memo Type
Don’t enter a Memo_Text when the system expects a Memo_ID. They are not interchangeable. - Copying Incomplete or Extra Characters
Trailing spaces, missing digits, or incorrect case in hashes can invalidate the memo. Copy-paste carefully. - Assuming All Wallets Need Memos
Only use memos when explicitly required. For personal wallets (e.g., Lobstr, Frontier), leave the field blank unless stated otherwise.
Frequently Asked Questions (FAQ)
Q: Do I need a memo when sending XLM to another personal wallet?
No. If you're sending XLM between your own wallets or to a friend's private wallet (not an exchange), you do not need to include any memo. The transaction will process successfully without one.
Q: What happens if I send XLM with the wrong memo?
If the memo is incorrect or missing when required (especially for exchanges), your funds may not be credited to your account. While the blockchain records the transfer, the receiving service cannot link it to your user ID. Contact support immediately with the transaction hash.
Q: Can I recover funds sent without a required memo?
Possibility depends on the exchange. Major platforms like OKX and Binance often track deposits manually. Provide them with your wallet address, transaction ID, and intended memo. Recovery isn’t guaranteed but is possible with prompt action.
Q: Is there a fee for including a memo in a Stellar transaction?
No. Adding any type of memo—Text, ID, Hash, or Return—does not increase the base transaction fee on the Stellar network, which remains minimal (typically ~0.00001 XLM).
Q: How do I find my deposit memo on an exchange?
Log into your exchange account, navigate to "Deposit" > "Stellar (XLM)", and generate a deposit address. The system will display both the public key and the associated memo (usually Memo_ID). Always use both together.
Best Practices for Using Memos Safely
- Always verify both the address and memo before confirming a transaction.
- Use copy-paste instead of manual typing to avoid typos.
- Save screenshots of deposit instructions provided by exchanges.
- Test with a small amount first when making a new type of transfer.
- Use trusted wallets that clearly label memo requirements (e.g., Freewallet, Atomic Wallet).
Final Thoughts
Memos are a powerful yet often misunderstood feature of the Stellar network. While they add complexity, they also enable scalability and precision—especially for institutions managing thousands of transactions daily.
By understanding the differences between Memo_Text, Memo_ID, Memo_Hash, and Memo_Return, you gain greater control over your digital asset movements and reduce the risk of errors.
Whether you're a casual user or building on Stellar’s decentralized infrastructure, mastering memos is essential for secure and accurate transactions.
👉 Start using a reliable platform to send and receive XLM with confidence