How to Add a CEX Deposit Memo on Swap Payout (XRP, XLM, TON)

How to Add a CEX Deposit Memo on Swap Payout (XRP, XLM, TON)
Author profile photo
October 19, 2026
~9 min read

You want USDT to land as XRP, XLM, or TON on Binance, Coinbase, or OKX, so you paste only the deposit address into Bitsz Recipient’s address and click Exchange. The order can finish, the explorer can look green, and the CEX balance can still be empty. Copy that venue’s live deposit address plus Destination Tag, Memo, or Comment into the widget before Exchange. If Bitsz shows no extra-ID field while the CEX shows one, stop and pay out to a wallet you control.

Quick answer: A CEX (hosted exchange) often shares one deposit address across many accounts. The extra ID is how they know the coins are yours: Destination Tag on XRP, Memo on XLM, Comment or Message on TON. Set You receive to that asset, copy address and extra ID from this ticker’s live CEX Deposit page into Bitsz Recipient, then click Exchange once. If the CEX shows an extra ID and the live widget has no matching field, do not paste the tag into the address line. Put a self-custody wallet you control, then send from that wallet to the CEX later with the CEX tag on the send screen.

Bitsz is a non-custodial instant swap. Recipient’s address is where the platform sends You receive after the exchange, not the one-time deposit you pay later. Homepage help calls a Destination Tag (MEMO) an extra identifier for shared exchange wallets: without it, coins can hit the exchange wallet but not your account. That FAQ lists EOS, XRP, XLM, BNB, and XMR. TON is missing, so open this CEX Deposit page.

Treat Recipient’s address as this CEX deposit page, not the later Bitsz You send deposit

Две колонки Bitsz: чип CEX deposit против You send на карточке Recipient

Recipient is the CEX deposit, not You send.

Open the widget. Set the pair so You receive is XRP, XLM, or TON. On Bitsz, native TON often shows as GRAM (prev. Toncoin) with network TON. Match that ticker to the CEX deposit asset. The Network chip must be the same chain the CEX Deposit screen named. Recipient’s address is the payout destination. Extra ID, if shown, is a second field beside that address.

The later Bitsz order deposit (You send) can also print a memo. That value is for your sending wallet. Use the Bitsz deposit memo guide for that leg. Do not paste a Bitsz deposit tag into Recipient. Do: treat this CEX Deposit page as the only source for payout address plus extra ID. Do not: invent a tag or skip the extra ID because a Ledger receive address does not need one.

Copy address plus memo or tag from that same CEX deposit screen

Три шага Bitsz: Copy address, Copy memo и Same screen на одном CEX Deposit

Copy address and extra ID from one screen.

Log in to the receiving venue. Open Deposit for this exact ticker and this exact network. OKX’s help (updated 26 Aug 2026): pick crypto and network, then copy address and tag, memo, or comment if the screen requires one. If that screen shows no extra ID, address alone is what they want. Copy both values as two separate pastes.

You receive asset Name on most CEX screens What to copy
XRP Destination Tag (numeric) Whole number. XRPL tags are 32-bit unsigned (0–4294967295).
XLM Memo (type as printed) Same type the CEX printed. Stellar MEMO_TEXT is up to 28 bytes.
TON / GRAM (prev. Toncoin) Comment, Message, or memo Exact text from this CEX Deposit page (Wallet.tg, 8 Oct 2026).

Coinbase lists XRP as Tag numeric and XLM as Memo alpha-numeric for deposits to Coinbase. TON is not in that table. Do not invent a TON comment. Binance (incorrect-deposits FAQ, updated 5 Dec 2025) names a missing or wrong tag on TON, XLM, and XRP as a reason a deposit will not be credited. Do: two copies from the screen that is open now. Do not: a filler tag or last week’s Binance XRP tag.

Stop the CEX payout when the live Bitsz widget has no memo or tag field

Чеклист Bitsz: нет поля memo, остановить CEX payout, перейти на self-custody

No extra-ID field means stop the CEX payout.

After you paste Recipient’s address, look next to it. The default homepage draw on 19 Oct 2026 still shows one input: Recipient’s address. The public pairs list that day had 7312 pairs and no requiresMemo flag.

If this CEX Deposit page shows an extra ID and Bitsz has no second field for You receive, stop the CEX route. Do not paste the tag into the address line. Do not click Exchange hoping an API will attach it. Orders API v2 stores destinationAddress as the required payout and destinationAddressMemo only if that optional field is supplied. A checkbox like “My wallet doesn’t require destination tag” is only for a receive wallet that shows no extra ID. Self-custody means a wallet whose keys you hold, such as Ledger or Tonkeeper. Ledger (updated 6 Oct 2026): a tag is required when you send to a CEX, not when a CEX sends to Ledger. Pay Bitsz out to that wallet, then send from the wallet to the CEX with the CEX tag on the send screen. Do: switch Recipient to self-custody when the extra-ID field is missing and the CEX requires one. Do not: click Exchange on a CEX address with a silent memo.

Match ticker, network, full address, and extra ID, then click Exchange once

How the payout check runs:

First set You receive to the CEX deposit asset and network. Then copy address and extra ID from that same Deposit screen. Next confirm the live Bitsz widget shows a memo or tag field. Then match four values, tick the checkbox, and click Exchange once. On a large amount, run a tiny same-route test and wait for CEX credit, not only explorer Success.

  1. Set You receive to XRP, XLM, or TON/GRAM and set Network to the CEX deposit network.
  2. Open this venue’s Deposit for that ticker and network. Copy address. Copy extra ID as a second paste.
  3. Look beside Recipient’s address. If the CEX showed extra ID and Bitsz has no matching field, stop and switch Recipient to self-custody.
  4. Match four fields: ticker, Network chip, full address including the middle, and extra ID value plus type.
  5. Tick the non-EU/EEA checkbox and accept Terms, AML, and Privacy. Click Exchange once. Save the Order ID.
  6. On a large or first-time venue, create a tiny test with the same pair, networks, Recipient, and extra ID. Wait until the CEX balance increases. Then open a new large order and recopy Deposit.

First make the address string look like a real XRP, XLM, or TON address. Truncation sits on the invalid Recipient checklist. Then fill extra ID. A 5 min average exchange time on the homepage is not CEX credit without a tag. When the four fields match, create the order on the Bitsz swap widget. For a large payout, use the test-swap-before-large-transfer checklist with the same Recipient and memo. Do: one Exchange click after a full match. Do not: click Exchange again to “fix” the tag.

Avoid sending You send if Exchange stored a blank tag

Stop before you broadcast You send. Terms 2.4 bind pair and recipient wallet when the order is created. Terms 2.5 and 6.3 put incorrect details on the user. There is no Terms line that Bitsz will add a missing CEX tag after Exchange or recover an uncredited CEX deposit. See Terms of Use. Send one pack to Bitsz support: Order ID, what stood in Recipient and in the memo field, and a screenshot of this CEX Deposit page. Do not seed. Terms 6.5 allows a refuse-and-return to the deposit sender, in 30 minutes to 72 hours. That return does not rewrite a CEX extra ID.

If payout already hit the CEX shared address, write that venue with the payout TxID: Binance Unknown Memo/Tag Recovery, OKX support with coin, amount, correct tag, incorrect tag, and hash, or Coinbase support plus the hash. After Finished, use the payout TxID checklist. XRPL code tecDST_TAG_NEEDED (143) is an on-chain fail, not a green Success with an empty CEX account. Do: freeze You send if the stored tag is wrong; write the CEX if payout already landed. Do not: a second swap or a request that Bitsz append a tag to an already sent Payment.

Keep this checklist off the Bitsz deposit memo and payout-TxID guides

This guide starts at CEX Deposit and ends at Exchange. Bitsz deposit memo when you send You send, an invalid Recipient string, explorer matching after Finished, a CEX withdrawal delay, a refund return address, a clipboard hijack, and a stuck or AML wait are other checklists. Do not reuse a test order’s one-time deposit. Do: stay on payout extra ID before Exchange. Do not: mix a You send memo or an explorer wait into this paste.

FAQ

Does a Bitsz XRP payout to Binance need the Binance tag?

Yes, if Binance Deposit for XRP shows a Destination Tag. Copy that tag into the Bitsz extra-ID field for You receive before Exchange. The Bitsz order deposit tag, if any, is for You send.

What if Bitsz has no memo field on Recipient?

Stop the CEX route. Do not paste the tag into the address line. Put a self-custody receive address you control, then send from that wallet to the CEX later with the CEX tag on the send screen.

Should I skip memo because my Ledger does not need one?

No, not when You receive is the CEX. Ledger (6 Oct 2026): a tag is required to a CEX. Never use a random number as a Binance, OKX, or Coinbase deposit tag.

Can Bitsz recover a payout that hit the CEX without a tag?

Do not expect it. Terms 2.5 and 6.3 put incorrect details on the user. If the payout TxID already shows the CEX shared address, write that CEX with the hash. If you have not sent You send, do not send; write Bitsz support with the Order ID.

Is a TON comment the same as an XRP destination tag?

Same job, different label. XRP is a whole number (0–4294967295). XLM is a Memo whose type must match the CEX screen. TON is usually Comment or memo text. Copy the value this CEX Deposit page printed.

The widget checkbox says my wallet does not require a destination tag. The CEX shows a tag. May I leave the box checked?

No. That box is for a unique self-custody receive address that shows no extra ID. If the CEX printed a tag, uncheck it, fill the extra field, or switch Recipient.

Disclaimer: The material in this article is not financial or investment advice. Everything stated here reflects the author's personal view and should not be treated as a recommendation to trade or invest. We make no warranties regarding the accuracy, reliability or completeness of the information presented. Cryptocurrency markets are highly volatile and can move unpredictably. Before committing any funds, every investor, trader or crypto user should study several independent sources and check the regulations that apply in their own jurisdiction.

0.0
(0 ratings)
Click on a star to rate it

You send:

You receive:

Bitsz uses an automated risk assessment system that helps identify suspicious activity during the exchange process. If your transaction is detected by this system, Bitsz reserves the right to request KYC and process the transaction according to AML Policy and also Terms of Use . We use cookies to improve the quality of service. By using Bitsz, you agree to Terms of Use And Privacy Policy .