How to Handle a CEX Travel Rule Check Before You Swap
You paste a Bitsz deposit into a CEX withdraw screen and a Travel Rule sheet appears: “whose wallet is this?”, a Satoshi test, or “sign this address”. That is how to handle a CEX travel rule for a swap deposit: it is an ownership gate on the exchange, not a Bitsz hang and not a missing TxID. Do not mark the one-time address as your MetaMask. Verify a wallet you control, wait until the CEX shows it approved, hop the coins there, then open a fresh swap.
Quick answer: A Bitsz pay-to string is a one-time deposit, not your personal wallet. Stop that CEX withdrawal. Prove a self-custody address you hold, wait Verified, withdraw there, wait for a TxID, then create a new Bitsz order and send from that wallet once.
A CEX is a centralized exchange (Binance, Bybit, OKX, Coinbase). Travel Rule means they record who owns the destination. A Satoshi test is a tiny exact send from your wallet to the CEX. A Digital Signature is a message you sign on that CEX’s official site; no coins move. Self-custody means you hold the keys. Bitsz is non-custodial: Terms 2.4 give each order a unique deposit you cannot spend from. Homepage “about 5 minutes” is swap time after a valid send, not CEX review. EU Transfer of Funds rules (Regulation 2023/1113, fully applicable 30 Dec 2024) explain why venues ask this for self-hosted sends over €1,000; Bitsz is not available to EU/EEA residents.
Treating Travel Rule, “whose wallet is this”, a Satoshi test, or a sign prompt as a CEX ownership gate

Whose-wallet sheet is a CEX gate
Do: read what this venue asks on this withdrawal. Do not: tell Bitsz the swap “hung on Travel Rule”, and do not mix the CEX internal Withdrawal ID with a TxID (the on-chain hash after broadcast).
Bybit’s Travel Rule FAQ (updated 23 Aug 2026) shows the pattern after Submit: Exchange versus Personal wallet, then “Whose wallet is this?”, then Pending review of up to 30 minutes. Binance Address Book labels rows Verified, Declared, Pending, or Unverified. That chip asks who controls To. It is not Bitsz Processing or a blank hash after a broadcast.
| What you see | Whose gate | Do | Do not |
|---|---|---|---|
| Travel Rule / whose wallet / Satoshi / sign | CEX, before broadcast | Verify a wallet you control | Treat it as a Bitsz status |
| Processing, no TxID after Withdraw | CEX after Submit | Use the missing-hash checklist | Relabel it Travel Rule |
| Remaining hours on a new book row | CEX allowlist lock | Wait the lock after Verified | Open a 12-minute Fixed quote |
| Connect or Permit on a non-CEX swap tab | Third-party sheet | Reject it | Unlock a spender |
| Live Chat asks for a public address | Bitsz AML pre-check | Type the send-side address | Connect a wallet |
How the hop runs:
First classify the CEX prompt as an ownership gate. Then stop if To is this live Bitsz deposit. Next verify a wallet you control and wait until that venue shows Approved. After that withdraw to that wallet and wait for this CEX TxID. Then open a fresh bitsz.io order and send from that wallet once.
Stopping if the destination is this live Bitsz one-time deposit: do not mark, sign, or micro-send it

Do not mark this one-time deposit
Do: cancel or abandon the CEX withdrawal to that string. Do not: tick “my MetaMask / personal wallet / I am sending to myself”, pick a random VASP (another exchange in the dropdown), Connect Wallet, sign a message, or dust-pay the Bitsz deposit “as a Satoshi test”.
The homepage tells you to send to the one-time address for this order. Official Satoshi flows require the test to leave from the address being verified and land on a CEX address. A Bitsz deposit cannot do that, and a random dust send to Bitsz is not ownership proof. If Bitsz is missing from a connected-exchange list, do not guess a name. Treat a missing match as “this is not a VASP hop” and verify your unhosted wallet instead.
Verify a self-custody address you control first; do not click Exchange on a 12-minute Fixed quote during review

Wait Approved before opening Exchange
Do: finish the gate on a wallet whose keys you hold, then wait until that row is Verified or Approved. Do not: click Exchange on Bitsz while the CEX still shows Pending, Unverified, or in-review, and do not start a Fixed quote “to cover the test”.
On Binance, mark a self-hosted row as sending to yourself, then Satoshi the exact on-screen amount to Binance (their FAQ example is 0.00000208 BNB-BSC; copy your screen). A third-party self-hosted row is only Declared; do not use that to claim a Bitsz deposit. OKX prefers Digital Signature (no network fee); Satoshi is typically about 5 USDC in 180 minutes from that exact address. Coinbase Exchange signs only ERC-20 on coinbase.com; otherwise send a small deposit from your wallet to Coinbase. Crypto.com allows 90 minutes. Kraken allows 180 minutes, then you must start a new withdrawal. For bitcoin, send from the address being verified, not an empty new receive address.
Fixed rate on Bitsz freezes the quote for 12 minutes (Terms 2.2.1, fee 1% plus network fee). Bybit review can take 30 minutes, and Satoshi windows run 90 to 180 minutes, so 12 minutes never covers that. Floating is not a freeze until funds arrive (Terms 2.2.2). Fixed can also show as temporarily unavailable. Terms 2.10: delays on the client’s side are not Bitsz’s clock. Terms 6.5 (30 minutes to 72 hours) is the swap window after a valid deposit, not a Travel Rule SLA.
Withdraw to that verified wallet, wait for a TxID, then open a fresh Bitsz order and send once
Do: hop through the approved personal wallet, wait until CEX history shows this TxID, then open a new order and copy the deposit from that live screen. Do not: save a Bitsz one-time string in a Travel Rule Address Book “for next time”, and do not fire a second Exchange on the old quote.
- Read this CEX prompt (Exchange vs Personal; myself vs someone else).
- Stop if To equals this live Bitsz one-time deposit.
- Pick a self-custody address you control (funded, if the venue uses bitcoin Coin Control).
- Finish Digital Signature on the official CEX host, or send the exact Satoshi amount from that wallet to the CEX verification address.
- Wait until the row is Verified or Approved, not Pending.
- If a new-address allowlist still shows remaining hours, wait that lock too, then submit Withdraw to the verified wallet only.
- Wait until history shows this CEX TxID. No hash after Submit is a different checklist.
- Open a new order, copy that deposit, and send once from the verified wallet (tiny same-route test first if the size is large).
If a Bitsz quote is already open and Travel Rule appeared on its deposit: do not broadcast or sign that string. Let the unused quote expire, then run steps 3 to 8. A Satoshi test is not a Bitsz test swap; use the test-swap-before-large-transfer checklist only after the CEX TxID. Then create the live order on bitsz.io and copy the pay-to from that screen.
Do not mix this gate with a missing TxID, a whitelist lock, Bitsz AML chat, a fake Connect, reuse, or a test-swap size
Do: open the neighbor guide that matches the chip. Do not: paste every prompt into one Bitsz ticket, and do not treat CEX Travel Rule as Bitsz AML.
If Withdraw is already submitted and history has no TxID, use the CEX withdrawal delay checklist. Remaining hours on a new Address Book row can stack after Verified; wait them. Bitsz AML pre-check is Live Chat with a public address as text (AML Policy 4.1 / section 9), not Travel Rule. A Bitsz swap never asks Connect Wallet. If a third-party tab wants Permit, reject it and use the Connect Wallet and token-approve checklist. Do not store “Bitsz USDT” as a reusable book entry.
After Verified and the CEX TxID, open one new order on bitsz.io and send from that wallet. Check Terms of Use for the 12-minute Fixed lock and the unique-address rule. CEX Travel Rule tickets go to the CEX, not to Bitsz, unless this order’s deposit is already on-chain.
FAQ
Can I declare the Bitsz deposit as my personal wallet?
No. You do not hold keys to the Terms 2.4 one-time address. Stop that withdrawal, verify a wallet you control, then hop.
What if the CEX asks for a Satoshi test to the swap address?
Do not send from the Bitsz deposit, and do not dust-pay it “as a test”. Send the exact on-screen amount from your wallet to the CEX verification address, wait Verified, then withdraw there.
Should I Connect Wallet to sign Travel Rule for a Bitsz deposit?
No. A Bitsz swap never needs Connect Wallet, and a CEX signature is only for an address you control on that CEX host. If the sheet asks you to prove a Bitsz deposit, Reject it.
Is Travel Rule the same as Bitsz AML pre-check?
No. Travel Rule asks who owns the CEX destination; Bitsz AML pre-check is Live Chat with a public address as text. Do not paste a seed into either flow.
What if I already opened a Fixed order then saw the Travel Rule popup?
Do not send and do not sign that deposit. Let the unused quote expire, verify your wallet, hop, then open a new order after the CEX TxID. Fixed is 12 minutes; Satoshi windows are 90 to 180 minutes.
The CEX list has no Bitsz. Should I pick a random exchange or Other?
Do not guess a VASP name to force the withdrawal onto a one-time deposit you do not control. Verify your unhosted wallet, withdraw there, then create the Bitsz order.
Is a Satoshi test the same as a Bitsz test swap?
No. Satoshi proves you control a self-hosted address for the CEX. Run a tiny Bitsz test only after the hop TxID exists.
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.
