All guides

Wallet checks

Memos, destination tags and refund addresses explained

An address sometimes identifies a service's wallet, while an extra tag or memo identifies the customer to credit. Copying only the address can leave a confirmed transfer without the intended account credit.

A realistic phone transfer form separates address and memo fields beside XRP and Stellar coins and a three-role checklist.
AI-generated illustrative device scene, not an actual product screenshot or live transaction. Some shared receiving addresses need a memo or destination tag to identify the account.

Why a deposit can need an extra ID

Services receiving XRP can use a destination tag to identify which customer should receive credit. Stellar transactions can include a memo, which some receiving services require for the same practical purpose. Whether you need one depends on the receiving service's instructions, not simply on the asset's name.

Open the destination's current deposit page and copy the address plus any requested tag or memo. Check the required memo type and value. Do not invent a number, reuse another account's tag, or assume that an empty field is correct because a personal wallet you used previously did not need one.

Think of the address as a building and the tag as an account label

A service can receive payments for many customers through one blockchain address. The destination tag or memo supplies the additional information it uses to credit the right internal account. Reaching the shared address is therefore only part of the instruction.

An analogy is a package delivered to a building’s reception without the recipient’s name. Delivery to the building may be successful while reception cannot assign the package. A confirmed blockchain transfer can likewise coexist with a missing account credit when a required extra identifier was omitted or mistyped.

This analogy does not mean every XRP or Stellar destination needs an extra field. The requirement comes from the destination. A personal wallet and a custodial account can have different instructions for the same asset, so check the actual deposit page every time you choose a destination.

A smartphone receive form with separate address and memo fields sits beside a labelled parcel analogy and XRP and Stellar coins.
AI-generated illustrative device scene, not an actual product screenshot or live transaction. The address reaches the service; a required memo or tag identifies the customer account.

Check extra IDs in all three places

The recipient, provider deposit and refund can each have different instructions. Reviewing one field does not validate the other two.

A laptop shows three illustrative address-and-memo panels for recipient, deposit and refund beside XRP and Stellar coins.
AI-generated illustrative device scene, not an actual product screenshot or live transaction. Check memo requirements separately for the recipient, deposit and refund details.
PlaceWhere its instructions come from
Recipient memo or tagYour destination wallet or exchange deposit page
Provider deposit memo or tagThe confirmed swap order's deposit instructions
Refund memo or tagThe wallet or service that will accept the original sending asset back
  1. Copy the recipient address and any required extra ID before confirming.
  2. After order creation, inspect the provider's deposit instructions for a separate required memo.
  3. When entering refund details, check the sending-network wallet's own deposit instructions.

Match the refund to the sending side

A refund address is for the asset you originally send, on that same network. If you exchange XRP for ETH, an Ethereum receiving address is not a substitute for an XRP refund address. Choose a refund destination you can access and that accepts the relevant asset and network.

Custodial deposit instructions can change or have minimums and memo requirements. Check them before relying on an exchange address for a possible refund. A provider's refund process and applicable costs depend on that provider's terms; submitting an address does not promise an automatic or instant refund.

Resolve uncertainty before sending

If your destination explicitly requires no extra ID, follow that wallet's instructions and the form's guidance. Where the form requests an explicit zero for no memo, use it only for a destination that requires none. Zero is not a replacement for a real tag supplied by an exchange.

If the destination requires a memo type the form cannot represent, stop before confirming and ask support about compatibility. After an incorrect or missing memo deposit, preserve the swap ID and transaction hash and contact support. Recovery depends on the receiving service and is not guaranteed; sending another transfer is not a reliable way to correct the first.

Copy the required value in a form the destination accepts

XRP destination tags are numeric identifiers. Stellar memos can have different types, including text and numeric IDs. A number displayed on a deposit page should not be reformatted, rounded or replaced with an explanatory sentence. Follow the stated type as well as the value.

Some Stellar services use an account format that carries customer-identifying information rather than asking for a separate memo. That does not establish that every swap provider accepts the format. If the form rejects the address or cannot represent the destination’s required memo, ask about compatibility before ordering. Do not shorten or modify an address to force it through validation.

A memo is not a field for a note to Tornado Swap support. Putting a message such as “my deposit” where an exchange expects an account identifier can prevent automatic crediting. If you have a question, use Contact us separately and keep the transaction fields exactly as instructed.

Where a form uses an explicit zero to indicate no memo, read that guidance carefully. Zero can be a valid numeric value in some contexts, so it is not a universal substitute for blank. Use the destination’s actual requirements and confirm that the selected route can represent them.

A worked example: XRP to ETH with an XRP refund destination

Suppose you are sending XRP and want ETH on Ethereum. Your recipient details must accept ETH on Ethereum. If the order requests a refund address, those details must accept XRP back on the sending network. The ETH receiving address cannot fill the XRP refund role.

If your XRP refund destination is an exchange account, copy its XRP deposit address and required destination tag as one set. A refund reaching the correct shared address without your account’s tag may still need manual investigation. Check minimums and whether that service accepts this kind of incoming transfer before relying on it.

After order creation, inspect the provider’s own XRP deposit instructions. They may contain a different tag from your refund destination because they identify a different account or order. Do not reuse your refund tag in the provider deposit field unless the confirmed instructions actually match.

Save all three sets of details with their roles clearly labeled. A refund address provides a destination for possible provider handling; it does not itself guarantee a refund, set a refund deadline or override the provider’s terms and applicable costs.

If a required memo was already omitted

Keep the transaction hash and original instructions, then contact the receiving service or Tornado Swap support as appropriate to the affected leg. State which role is involved: deposit into the provider, payout to your wallet or a refund. Include the correct extra identifier and the one actually sent, if any.

Do not send a second transfer with the missing tag and assume it attaches that tag to the first payment. Transactions are separate records. Recovery, if possible, follows the receiving service’s process and may require evidence of control, manual work or fees. Never disclose a seed phrase or private key to prove ownership.

A laptop support-case form and phone transaction record highlight a missing memo beside XRP and Stellar coins and an evidence notebook.
AI-generated illustrative device scene, not an actual product screenshot or live quote. If a required tag was missed, keep the records and ask support before sending again.

A FEW MORE DETAILS

Common questions

Does every XRP address require a destination tag?

No. Follow the specific destination’s deposit instructions. Shared custodial addresses commonly need a tag; another wallet may not. The asset name alone does not answer the question.

Can I use my recipient memo as the provider deposit memo?

Only if the separate instructions actually say the same thing. The recipient, provider deposit and refund identify different destinations and may each require a different extra ID.

Is a refund address always my original sending address?

Do not assume that. A sending exchange can use a shared withdrawal wallet that is not an appropriate deposit destination for your account. Obtain refund details that accept the sending asset and network and that you can access.

Can a missing tag be corrected after confirmation?

The original confirmed transfer cannot simply be edited by changing a field in the swap form. Contact the receiving service with the evidence. Any recovery depends on its support process and technical ability; it is not guaranteed.

Prepared by Tornado Swap to explain the swap workflow. Network conditions and provider offers can change; check the current order instructions before sending funds.

Keep reading