Should I enter the XRP destination tag as the Stellar memo?

Only the Stellar recipient can supply its required memo. It is a different receiving instruction. Never carry a customer number across networks by assumption, even if the two fields allow the same digits.

The XLM transfer is visible but my hosted balance is missing. What should I keep?

Keep the payout reference, exact receiving address, memo details and order number. Provide those to the responsible service through its support channel. Network visibility alone does not prove that an internal customer balance was credited correctly.

XRP to XLM: separate the deposit tag and payout memo

An XRP tag does not become the XLM memo

This exchange has two recipients: the XRP deposit used to fund the order, and the Stellar account selected for its XLM payout. Each recipient supplies its own routing details. Copying the number from the first payment into the second can assign the payout incorrectly even when both forms accept numbers. Keep separate notes for the two sides and label which service issued each instruction. A saved contact called “exchange” is too ambiguous when you have more than one hosted account.

XRPL documentation distinguishes the destination tag, which identifies the intended beneficiary in a receiving service’s records, from the source tag, which identifies the originator. These fields do not perform a Stellar routing function. If your sending platform displays its own source tag, that does not replace the destination tag requested by the XRP deposit instruction. Resolve a missing or conflicting field before submitting the payment.

Keep a small routing map before confirmation

Payment	Value to obtain	Where to obtain it
XRP funding	Deposit address and any required destination tag	The current exchange order’s XRP instructions
XLM payout	Stellar receiving account and required memo	The actual XLM recipient’s deposit screen
Hosted-account credit	The recipient’s internal credit record	The service managing that account
Support reference	Order number plus the relevant transaction reference	The exchange record and the corresponding network

Do not reuse either side’s customer identifier merely because the other side also has a routing field.

Settle the Stellar instruction before paying XRP

Read the memo type as well as its value: Stellar supports distinct memo formats, including text and numeric ID. Preserve the type supplied by the recipient. A number displayed as text is not an invitation to select a different type just because it looks numeric. If the exchange form cannot represent the requested instruction, do not invent a substitute.
Do not shorten an M-address: Stellar documents muxed addresses as a way to combine a shared account with an internal ID. Support is not universal across services. This page does not establish that the payout form accepts them. Ask for a compatible receiving instruction rather than trimming an address or separating it by guesswork.
Check the two transaction records independently: The XRP funding record can be complete while the later payout or hosted credit still needs checking. Match the outgoing XRP reference to its deposit, then use the XLM payout reference when asking the recipient about credit. Sending the same XRP again does not repair a wrong XLM memo.

Routing the two payments

Should I enter the XRP destination tag as the Stellar memo?: Only the Stellar recipient can supply its required memo. It is a different receiving instruction. Never carry a customer number across networks by assumption, even if the two fields allow the same digits.
The XLM transfer is visible but my hosted balance is missing. What should I keep?: Keep the payout reference, exact receiving address, memo details and order number. Provide those to the responsible service through its support channel. Network visibility alone does not prove that an internal customer balance was credited correctly.

Tag and memo specifications

Reviewed: 2026-10-21