The Bitsz order already shows Finished, but the wallet or CEX on the receive side still looks empty. An empty app does not cancel that chip. Copy the payout TxID (the hash Bitsz sent on the You receive network), open that network’s explorer, and match destination, asset, amount, and confirmations. This swap finished payout TxID explorer checklist takes about 8 to 12 minutes and keeps you from a second send.
Quick answer: When the live Bitsz order shows Finished and the receive wallet is empty, copy the payout TxID. Do not paste the Order ID or treat the deposit TxID as proof of payout. Open the You receive explorer, match To to Recipient’s address, then pick one branch: wait for confirmations, unhide a token, write the receiving CEX, or send one official Bitsz packet.
Bitsz is an instant crypto exchange (homepage, founded 2023). Track the live order until Finished. Other desks may say Executed or Completed; on Bitsz, trust that chip. Terms 6.5 gives 30 minutes to 72 hours. The homepage 5 min average is marketing, not a payout SLA. Still Processing or API trading / kyc: stuck swap status checklist. CEX withdrawal with no hash before you swapped: CEX withdrawal delay checklist.
Workflow: first copy Order ID and the Finished chip, then isolate the payout hash, next open the receive-network explorer, then pick one branch, then wait or write one official ticket. Do not open a twin order.
Checking the Finished chip: do not send again
Empty wallet is not a reason to send again.
Do copy the Order ID and the exact Finished chip from the live Bitsz order. Do not send a second payment “to wake it up”. An empty wallet UI is not proof Bitsz failed to pay: the app may be syncing, a CEX may still be counting confirmations, or a token may be hidden. An Order ID is Bitsz’s internal number (API orderId), not a blockchain hash. Keep it for support. Deposit sits on You send; payout sits on You receive. Bitsz is non-custodial (footer: it does not hold, store, or manage funds). Terms 2.6 notes delays. That is not a reason to broadcast again to the same one-time address.
- Write down the Order ID and the exact status chip from the live Bitsz order.
- Stop if the chip is not Finished; switch to the stuck-status checklist.
- Copy the payout TxID in full, with no spaces and no truncated middle.
- Copy the deposit TxID and label it as the send into Bitsz.
- Copy Recipient’s address, You receive asset, network, and quoted amount.
- Open only the explorer for the You receive network.
- Match To, asset, amount, memo or tag if needed, and confirmations.
- Pick one branch: pending, hidden token, CEX not credited, or missing payout hash.
Splitting payout TxID from deposit TxID: do paste only the payout hash
Paste the payout hash, not the Order ID.
A TxID (transaction ID, or hash) is the long string that identifies one on-chain send, like a parcel tracking number. LightSwap (updated 19 Jul 2026): a TxID is not an Order ID and not a withdrawal ID. Explorers index hashes, not Bitsz order numbers. One swap is two on-chain sends: deposit TxID on You send, payout TxID on You receive. Cross-chain pairs produce two hashes on two explorers. USDT on TRC-20 is not USDT on ERC-20. Do paste the full payout hash. Do not paste the Order ID into mempool.space. Do not prove payout with the deposit hash. API decode: destinationAddress is Recipient’s address; amountToWithdrawFact stays 0 until sent.
Opening the receive-network explorer: do not use the deposit explorer
Open the You receive explorer only.
Start with the You receive chip. EN Bitsz canon: Bitcoin on mempool.space, Ethereum / ERC-20 on etherscan.io, TRON / TRC-20 on tronscan.org. Other receive chains: bscscan.com (BNB Chain) or solscan.io (Solana). Gate Learn (29 Jul 2026): an indexer can lag about a minute. Refresh. Do not resend.
| You receive | Open | Do not open |
|---|---|---|
| Bitcoin | mempool.space | ETH or TRON explorer |
| Ethereum / ERC-20 | etherscan.io | Tronscan or Bitcoin |
| TRON / TRC-20 | tronscan.org | Etherscan (ticker is not enough) |
| BNB Chain / Solana | bscscan.com / solscan.io | The You send deposit explorer |
Do use the network next to You receive. Do not drop a TRC-20 hash into Etherscan. Explorers are read-only. Never type a seed, never pay an “unlock” fee, never wallet-connect to view a hash.
Matching To, asset, amount, and confirmations: do read the full To
Do read the full To string. Do not trust a cropped screenshot from a chat. Check these fields against the live order:
- Explorer status: pending, success, confirmed, or failed.
- To equals Recipient’s address, full string.
- Asset and token contract, not only the wallet ticker.
- Amount close to You receive / amountToGet, not You send.
- Memo or destination tag if the receive venue requires one.
- Confirmation count; refresh instead of broadcasting again.
- Official USDT ERC-20: 0xdac17f958d2ee523a2206206994597c13d831ec7.
- Official USDT TRC-20: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t (tether.to).
- On Ethereum, Value can be 0 ETH while USDT is in Tokens Transferred.
- amountToWithdrawFact still 0: payout hash may not exist yet.
- A one-minute empty indexer: refresh, not a second send.
- To on a different network than You receive: stop; not a recovery guide.
For USDT on Ethereum, open Tokens Transferred. VertexChange (29 Sep 2026) and Gate flag the 0 ETH trap. Confirm the contract on Tether’s supported protocols list. If the receiving CEX asks for a memo or destination tag, that extra ID must match. See the memo and destination tag checklist.
Choosing one branch: pending, hidden wallet, CEX, or missing hash
Exolix (15 Sep 2026): Completed on the desk is not funds already visible in a wallet. Pick one row. Do not mix branches in one ticket.
| What you see | What it means | Do | Do not |
|---|---|---|---|
| 0 conf, pending | Not in a block yet | Refresh receive explorer | RBF / Speed-up to “hurry Bitsz” |
| Success, self-custody empty | Hidden token, lag, wrong network toggle | Add token contract, rescan | Assume Bitsz never paid |
| Explorer success, CEX empty | Credit is a second checkpoint | Use that CEX deposit clock | Open a second Bitsz order |
| Finished, no payout hash, or To mismatch | Needs an official check | One packet: Order ID + both hashes | Telegram DMs or a seed “unlock” |
Pending Bitcoin: 0 confirmations means not in a block. bitcoin.org (Bitsz EN canon): about 10 minutes to 1 confirmation when the fee is enough, 6 confirmations about an hour. Do not RBF “so Bitsz pays faster”. Confirmed but a self-custodial wallet looks empty: same network in the app, add the token contract if hidden, then rescan (Exolix 15 Sep 2026; LightSwap 19 Jul 2026).
Confirmed but a CEX has not credited: explorer Success is not exchange credit (Gate Learn, 29 Jul 2026). Bybit: Pending until its confirmations, Completed once credited. CEX.IO (31 Aug 2026): if confirmations suffice, chat with User ID, TxID plus explorer link, sending address, and a deposit-address screenshot. Binance FAQs (updated 19 Dec 2025): Success but no credit goes to self-service retrieval after 1 hour if confirmed. Read that venue’s deposit page (Binance BTC can require at least 2 confirmations even if the chain shows 1). Do not invent a universal N for Bitsz. Do write the receiving venue when To matches. Do not write Bitsz “return my coins”.
Sending one official packet: do write Bitsz or the receiving CEX
Use this branch when the payout hash is missing on a Finished order, the explorer stays not found after the full string, or To does not match Recipient’s address. Terms 2.4: unique address captures pair and recipient wallet. Terms 2.5 and 6.3 put address mistakes on the user. Do not invent a clawback. Do not send again.
Pack one message: Order ID, Finished chip, deposit TxID, payout TxID or “payout field empty”, both networks, Recipient’s address, You receive amount, explorer URL, screenshots of the order and empty wallet. Send it once via Bitsz support, support@bitsz.io, or Live Chat on bitsz.io. Official Telegram t.me/bitsz_io is a public channel, not a ticket. If To already matched, write the CEX instead. Do not reuse this deposit address.
What to do next
Keep the Order ID until the balance is spendable. Pending: wait on that chain. CEX still counting: watch its deposit page. Desk check: one packet. Do not open a second swap “just in case”. When this case is closed, use the widget on bitsz.io for a new order, not a twin.
FAQ
Is the deposit TxID enough to prove payout?
No. The deposit hash only proves your send to Bitsz on You send. Copy the payout TxID and open the You receive explorer.
What if the explorer says not found?
Re-copy the full payout hash, confirm it is not the Order ID, and use the receive-network explorer. Wait about a minute for indexers. If it stays empty, send one official packet. Do not send again.
What if a CEX has not credited a confirmed payout?
Explorer Success is not CEX credit. Check that venue’s deposit page, then open a CEX ticket with the payout TxID. Binance retrieval: after 1 hour if confirmed. Do not open a second Bitsz order.
Should I send again because the wallet looks empty?
No. An empty app is not proof the payout is missing. Match the explorer first.
Is Finished the same as Processing?
No. Processing, or any not-Finished status with a deposit already on-chain, belongs on the stuck-status checklist. This page starts after Finished.
What if the payout To does not match Recipient’s address?
Stop. Terms 2.5 and 6.3 put address errors on the user. Pack Order ID plus both hashes for official support. Do not invent a clawback.
Do I paste the Order ID into mempool.space?
No. Explorers index hashes. Keep the Order ID for support. Paste the payout TxID on the You receive explorer only.
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.