A memo or destination tag can be essential when a service uses one receiving address for several customers. The network can deliver funds to that address while the service lacks the information needed to credit your account. Use the exact current value and type provided in the receiving instructions.
A local note or withdrawal order number does not automatically replace a required network field.
BTKWIN.COM · EDUCATIONAL EXAMPLEAddress and tag can identify different things
A service can give two customers the same receiving address with distinct tag values. The address directs the network payment while the additional data lets the off-chain system identify the intended customer.
The XRP Ledger documentation describes source and destination tags and their off-ledger interpretation. That does not mean every transfer of an asset always requires a tag. The actual receiving page for your account and route establishes the requirement.
For an educational example, customer A has tag 12001 and customer B has 12002 at a shared service address. Sending with B’s value does not become A’s deposit because the sender adds A’s name to an unrelated personal note. These are sample values, not usable deposit instructions.
Do not confuse a memo with a transaction identifier
A transaction ID locates the record after creation. A required destination identifier belongs to the payment data under that route. The ID can help support investigate a missing memo but does not retroactively insert data you omitted.
A platform’s internal withdrawal reference is another distinct item. It may locate a request before a public transaction exists. Supply the correct reference for the question rather than copying whichever long number appears nearby.
A local description can organize your own history without being sent as an on-chain memo. Read the actual field’s function and final preview. Similar names are not proof that the recipient sees the information.
References and limits
| Reference | Purpose | Does not replace |
|---|---|---|
| Receiving address | Network destination | Required account tag |
| Memo or destination tag | Association specified by the receiver | Correct asset and network |
| Transaction ID | Locate created network transaction | Omitted original payment data |
| Local note | Personal organization where local | Required transmitted field |
| Withdrawal order number | Sender-service request tracking | Public broadcast or receiving-account credit |
Field type can matter as much as the visible value
Memo is not one uniform format across all networks. A service may require a number, text or another supported type. XRP Ledger source and destination tags are 32-bit unsigned integers in transactions; do not add names, decorated separators or explanatory prose.
Stellar’s transaction documentation distinguishes memo types and formatting. A numeric-looking value submitted as text need not be equivalent to the required identifier type.
For a hypothetical service requesting Memo ID, placing the same digits in Memo Text does not establish compliance. Copy the supplied value using its declared type, and inspect whether another application or spreadsheet changed spaces, digits or formatting.
Some address formats include additional data
A supported address representation can encode an address and tag together. XRP’s documented X-address is one example. This is not a reason to invent a format by appending digits to a conventional address.
Check both products’ support for the representation and inspect decoded destination data. If the sending interface requests the field again or reports a conflict, resolve its documented behavior rather than guessing whether to duplicate the value.
A QR reader transports data without authenticating the source. Review which fields were populated and whether they match current receiving instructions. Our QR guide explains that separate source and confirmation review.
Why a payment can fail or succeed without credit
A receiving account’s rules can require a tag, leading to rejection when absent. In another case the network payment succeeds while a service’s internal crediting process needs additional association. Actual result and service requirements determine the case.
Requiring some tag is also different from verifying the right customer value. A random number chosen to satisfy a technical field can still fail to identify your account. Do not insert zero or an invented label simply to pass the form.
Other problems can coexist: unsupported asset, wrong network, minimum or incomplete confirmation. Finding a missing memo does not automatically prove it is the only issue. Continue matching the route and evidence.
Before submitting the payment
Open the receiving account’s current instructions and copy destination and required identifier separately where applicable. Match type, complete value, asset and network in the sending preview. Verify the selected receiving account has not changed during preparation.
Calculate net receipt and applicable minimum as well as the memo. A correct identifier does not make an insufficient quantity qualify. If the sending product lacks a suitable field, consult official support before paying.
The cost calculator can organize amounts but cannot verify an account-specific tag. The authoritative value comes from the intended receiving service or wallet instructions.
If a memo was missing or wrong
Gather network, asset, transaction ID, amount, time and destination, then the required memo and the data actually sent where readable. Open official support independently and describe the discrepancy clearly.
Kraken’s deposit recovery information illustrates a service-specific process and limitations. It is not a guarantee that every case is recoverable, free or immediate. Follow the actual recipient’s stated procedure.
Service processing may associate an existing payment internally where possible; that is different from editing a confirmed transaction’s original content. Preserve the original facts rather than promising that support can rewrite the chain.
Avoid creating another exposure while seeking help
Recovery words, private keys and login codes are not needed simply to inspect a memo. Do not send more funds to activate the first deposit based on an unsolicited promise. Use an official understandable process for the particular case.
Keep public transaction data proportionate to the question and preserve ticket references. Our missing deposit guide separates execution from crediting. Correct field names, types and values make that diagnosis more precise before the next transfer.
Source and destination tags are not interchangeable
Where a protocol distinguishes them, each field has its own role. Follow the receiving account’s requirement in the specified destination field. Copying another tag from a previous transaction merely because its label looks familiar can preserve the wrong reference while producing a technically populated form.
Continue reading
English content and examples reviewed: 27 October 2026. Read the Arabic edition.
