You hit Withdraw on Binance, Bybit, OKX, or MEXC. The chip still says Processing. The TxID field is empty. Your Bitsz swap timer is already ticking. A CEX withdrawal pending with no TxID before a swap send is not a stuck chain. The coins are still inside the exchange. This checklist shows you how to wait for a real hash, when you can still cancel, and how to stop a second send.
Quick answer: If a centralized exchange (CEX) still says Processing with no TxID (the public network receipt), Bitsz has not seen a deposit. Do not open a Fixed order. Do not fire a second withdrawal. Wait for a hash. Cancel only if that venue still allows it. Then match the explorer. The Bitsz homepage “5 min” average is swap marketing, not a CEX withdrawal clock.
Bitsz is an instant non-custodial swap: it does not hold your coins. The widget shows You send, You receive, Network, and Floating or Fixed. Each order gets a one-time deposit address. A CEX Processing chip is an internal queue, not chain congestion. Fixed freezes a quote for 12 minutes (Terms 2.2.1). Binance’s FAQ, updated 2026-08-13, says a TxID often takes 1–30 minutes. That lock can die first. Terms 2.10 treat client-side delays as the client’s problem. Do not treat Terms 6.5 (30 minutes to 72 hours after a valid deposit) as a Processing SLA.
How to split a CEX Processing chip with no TxID from an on-chain broadcast
Empty hash still sits inside the CEX.
A TxID is a transaction hash: a public receipt for a block explorer. A Withdrawal ID is only the CEX ticket number. Explorers do not index that internal number. An empty search is not proof the chain stalled. Until a TxID exists, Bitsz cannot detect that deposit.
- Step 1: Open CEX withdrawal history and look for a TxID, not a Withdrawal ID.
- Step 2: Treat Processing, Pending, or Under Review with an empty hash as an internal queue.
- Step 3: Wait for a TxID before a Fixed Bitsz order, or pick Floating if rails are slow.
- Step 4: Stop a second CEX withdrawal to the same one-time deposit.
- Step 5: Check this order’s expiry against the CEX chip, not a wallet pending label.
- Step 6: Match To, Network, and You send on the same-network explorer after the hash.
- Step 7: Escalate on the CEX clock if that venue’s window has passed with no hash.
- Step 8: Keep a single send if the TxID lands after Bitsz expiry, then use the expired-deposit guide.
| What you see | Likely class | Do | Do not |
|---|---|---|---|
| Processing / Pending / Under Review, no TxID | Internal CEX queue | Wait, or cancel if allowed | Call it a stuck Bitsz swap |
| Withdrawal In Progress, no TxID | Approved, not yet broadcast | Keep it CEX-side | Paste Withdrawal ID into an explorer |
| Sent or Completed plus a TxID | Broadcast | Check To, network, amount | Open a twin Bitsz order |
| Confirmations climbing | Network after broadcast | Wait; this is not AML | Resend to “wake” it |
| TxID after Bitsz expiry | Late broadcast | One send; expired-deposit guide | Pay the dead address again |
| Internal CEX transfer, no TxID possible | Off-chain ledger | Cannot fund an on-chain Bitsz deposit | Wait for a hash that will never exist |
Do check withdrawal history until a real hash exists. Do not write Bitsz that the deposit is lost while the TxID is blank. Use the stuck swap status checklist only after a matching explorer TxID exists.
Avoid a Fixed Bitsz order until the CEX history shows a TxID
Open Fixed only after a real hash.
Fixed is a frozen quote. Terms 2.2.1: fee 1% plus network fee, lock 12 minutes. If the market moves more than 1.3% before Bitsz sees the deposit on-chain, you get a refund path or a market continue. Floating (Terms 2.2.2) is 0.5% plus network fee and is not locked until funds arrive. Binance typically shows a TxID in 1–30 minutes. MEXC (2026-09-16) says 1–60 minutes. A 12-minute lock often ends first. Fixed can be temporarily unavailable in the widget.
| CEX Processing, no TxID | Bitsz Fixed (Terms 2.2.1) | Bitsz Floating (Terms 2.2.2) | |
|---|---|---|---|
| Who holds the coins | The CEX, not the chain | N/A until a deposit is seen | N/A until funds arrive |
| Typical clock | Binance TxID 1–30 min (escalate 6h); MEXC 1–60 min / 1h; OKX >1h | Frozen 12 minutes | Not fixed until the swap completes |
| If the CEX is still in queue | Client-side delay (Terms 2.10) | The lock can die first | Safer if rails may lag |
Verdict: Wait for a CEX TxID, then open the order. If those rails are slow, use Floating. See the Fixed vs Floating guide. Do not start Fixed “while the CEX thinks”. After a hash exists, create the swap on Bitsz.
Make sure you read Terms 2.2.1 and 2.10 before you race a CEX queue. Do wait for the hash, then open. Do not treat homepage “5 min” as Binance broadcast time.
Compare CEX status with this order expiry and stop a second withdrawal
Match the CEX chip to this order clock.
If a Bitsz order is already open, watch that order’s expiry. A wallet “pending” chip is a different clock. Terms 2.4 give each swap a unique deposit. A second Withdraw to the same address does not speed the CEX queue. It risks two broadcasts when the first leaves.
Cancel is venue-specific. Bybit (FAQ updated 2026-04-12): cancel only while the request is pending review (Under Review). Withdrawal In Progress means reviewed and still waiting to hit the chain. A gray Cancel means it is already moving. Instant withdrawal can take up to 15 minutes. MEXC says to cancel Processing through Customer Service. Do not assume every CEX still offers Cancel.
Workflow: First freeze the second Withdraw button. Then compare this Bitsz timer with the CEX status. Next, cancel the CEX request only if that button is still live and 12 minutes will not cover the queue. Then let Bitsz expire without a second send. After a TxID exists, open a fresh order.
Do finish or expire the first path first. Do not send “one more time to wake it”.
When a TxID appears, checklist destination, network, and You send
Once a hash exists, you are checking a public receipt, not a CEX queue. Use mempool.space for Bitcoin, etherscan.io for Ethereum and ERC-20 tokens, tronscan.org for TRON and TRC-20 (Tether on TRON).
To must equal this order’s one-time deposit. The network must match the Network chip. The amount should be close to You send minus the CEX withdrawal fee. Climbing confirmations mean the network is settling, not an AML hold. If the address starts with T but the order wanted 0x, stop and use the network checklist. If pasted To does not match the order UI, stop.
Before the next large withdrawal, check network, memo or destination tag if needed, and the exact amount. Then run a tiny test on a fresh order after these rails have already produced a TxID. See the test swap before a large transfer guide. Do not reuse yesterday’s deposit.
Do match To, network, and amount, then wait for confirmations. Do not paste AML clocks here.
How to escalate on the CEX clock if the hash is still missing
If the TxID is still empty past that venue’s window, write the CEX. Do not write Bitsz as if a deposit already arrived. Binance: no TxID 6 hours after the email confirm, then Support plus a withdrawal-history screenshot. MEXC: no TxID within 1 hour, then Funding History plus a screenshot. OKX: no TxID means the request may not have been processed yet. Pending or In progress more than 1 hour, then OKX Help.
Pack for the CEX: Withdrawal ID, UTC time, asset, network, destination, amount, status screenshot, and “TxID not issued”. Use Bitsz support (support@bitsz.io) only when a TxID already lands on this order’s deposit. Do not pay an “unlock fee” in chat.
If the CEX TxID appears after the Bitsz order expired, do not send again to that one-time address. Keep Order ID and the late TxID. Follow the expired swap after deposit checklist. Terms 6.5 (30 minutes to 72 hours, refuse-and-return, manual up to 68 hours) is a window after a deposit, not a CEX queue SLA. After the rails prove a TxID, open a new swap on the Bitsz widget if you still need the exchange. Check Network and the recipient before Exchange. EU/EEA residents cannot use the service.
Do escalate on the CEX clock with that packet. Do not expect Bitsz to extend Fixed while the CEX is still Processing.
FAQ
Should I open a Fixed Bitsz order while the CEX still says Processing?
No. Fixed is frozen for 12 minutes (Terms 2.2.1). Binance often needs 1–30 minutes for a TxID. Wait for a hash, then open. If rails are slow, use Floating.
Can I cancel a CEX withdrawal if the Bitsz timer is about to expire?
Only if that CEX still offers Cancel. Bybit: cancel only in Under Review. If Cancel is gone, do not send a second withdrawal. Let Bitsz expire, then open a new order after the TxID exists.
Is a CEX Processing chip the same as a stuck Bitsz swap?
No. Processing with no TxID means the CEX has not broadcast. A stuck Bitsz swap starts after a deposit TxID exists on an explorer.
What if the CEX TxID appears after the Bitsz order expired?
Do not send again to that one-time address. Keep Order ID and the late TxID, then use the expired-after-deposit checklist. Terms 6.5 is not a CEX-queue wait promise (Terms 2.10).
The explorer says “not found” but I pasted my CEX withdrawal ID.
That ID is not a TxID. Search only the hash from the withdrawal row. An empty search on an internal ID does not prove congestion.
Should I open a second Bitsz order while the first timer runs?
No. Each order has a unique deposit (Terms 2.4). Finish or expire the first path first. Then open a fresh order after a TxID exists.
Who do I write if there is still no TxID after several hours?
The CEX, with Withdrawal ID, screenshot, asset, network, destination, amount, and UTC time. Binance 6 hours, MEXC 1 hour, OKX more than 1 hour. Do not use Telegram.
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.