Your wallet already says Sent. The explorer may even show Success. The Bitsz order is still Processing, so it is tempting to send a second deposit, open support at 0 confirmations, or paste a Binance table onto this swap. Don’t. Copy the deposit TxID from the sending wallet, open only the You send explorer, and match To, asset, and amount before you count blocks. Wait there until credit is even possible.
Quick answer: Copy the deposit TxID from the sending wallet or CEX history, never the Order ID. Open only the You send explorer. Read Failed vs 0 confirmations vs climbing N. Match To, asset, and amount to this unique deposit. Wait there. Do not invent a Bitsz confirmation count from a Binance or OKX table. Explorer Success is not credited on Bitsz. Do not open support at 0 confirmations.
Bitsz is a non-custodial instant swap: the widget creates a unique deposit address for that order (Terms 2.4). A confirmation is an extra block after the network includes your send, not the order chip. Terms 6.5 says exchanges are processed in 30 minutes to 72 hours. That window is processing, not a timer for blocks. Homepage “5 min average” and “1 to 20 minutes” lines are marketing. A TxID (transaction ID, or hash) is the long string that identifies one on-chain send, like a parcel tracking number. Explorers index hashes, not Bitsz Order IDs. If you have no public hash yet, stop this page and use the CEX withdrawal delay checklist.
How to read deposit confirmations:
First copy the deposit hash from the sending wallet, then open only the You send explorer, then match To, asset, and amount, then wait while N climbs, then branch: keep waiting, treat a drop as unsent, or leave for stuck, payout, or ticket pack.
Start by checking the sending wallet: copy the deposit TxID, never the Order ID
Copy the deposit TxID, not Order ID.
Start with the outgoing history on the wallet or centralized exchange (CEX) that paid this order. That send’s network must match Network / You send on the live Bitsz card. Do copy the complete deposit TxID. Do not paste the Order ID into mempool.space, Etherscan, or Tronscan. Do not grab the payout hash from You receive; that hash is for after Finished, on the payout TxID explorer checklist.
- Copy the full deposit TxID from the sending wallet or CEX history on the You send network.
- Open only that network’s explorer and paste the hash, not the Order ID.
- Read Failed vs 0 confirmations vs climbing N, then match To, asset, and amount.
- Wait on that explorer; do not invent a Bitsz N from another venue.
- Do not open support, pay a speed-up DM, or send a second transfer at 0 confirmations.
- Branch once: keep waiting, treat a drop as unsent, or leave for stuck, payout, or ticket pack.
Open only the You send explorer and match To, asset, and amount before counting blocks
Match To, asset, and amount first.
Use one explorer for the You send network. Bitcoin on mempool.space, Ethereum / ERC-20 on etherscan.io, TRON / TRC-20 on tronscan.org. USDT on TRC-20 is Tether on Tron; USDT on ERC-20 is Tether on Ethereum. A “similar” explorer on the other chain will not show this send.
Before you count blocks, match the row to this order. To must equal this order’s unique deposit, character by character, not the first few symbols. For USDT, check Tokens Transferred / TRC20 transfer against the official contracts: ERC-20 0xdac17f958d2ee523a2206206994597c13d831ec7, TRC-20 TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Amount should be about You send minus the sender’s network fee. Do match To, token, and amount before you count confirmations. Do not treat a partial match as enough.
Read Failed vs 0 confirmations vs climbing N; explorer Success is not Bitsz credited
Explorer Success is not credited yet.
Zero confirmations means the send sits in the mempool, the waiting room of unconfirmed transfers, not yet in a block. Failed, dropped, or replaced means those coins often never reached the deposit, or a new TxID replaced the old one. Success or Confirmed means the chain included the transfer. It is not the Bitsz Finished chip and it is not “credited on Bitsz.” Do read Failed vs 0 vs climbing N on this hash. Do not treat explorer Success as order credit.
| Explorer reading | What it means | What to do |
|---|---|---|
| Failed, dropped, or replaced | Coins may still sit with you, or a new TxID exists | Track the new hash on this deposit. Do not send a twin |
| 0 confirmations (mempool) | Submitted, not in a block | Refresh the explorer. Do not open support |
| Climbing N | In a block; later blocks add 1 | Wait inside 30 minutes–72 hours. Do not paste another venue’s N |
| Success / Confirmed on this To | The chain included the transfer | Not yet credited on Bitsz. Keep the order tab open |
Wait on that explorer; avoid pasting a Binance or OKX confirmation table onto this Bitsz order
Bitsz Terms, FAQ, and Support do not publish a retail number such as “USDT TRC-20 = N” or “BTC = N.” If this live order card shows a waiting threshold, read that card. Do not import Binance’s example (BTC credit 1, unlock 2) or a CEX TRC-20 habit of about 19–20. Those are their rules and they change. API docs sample minConfirmationsToTrade (XRP 12, TRX 3) are examples, not a USDT or Bitcoin SLA. Retail users do not call that API.
Network guidance is not a Bitsz promise. bitcoin.org: one confirmation means inclusion in a block; 6 or more is the usual high-value rule of thumb; blocks average about 10 minutes; 0 confirmations are not secure. Ethereum finality is typically about 12.8 minutes; a wallet “confirmed” after one block is not Bitsz credit. Keep waiting on the matching To while N climbs, inside Terms 6.5 (30 minutes to 72 hours). A Fixed 12-minute lock is until the send is detected on-chain, not a confirmation timer. A slow fee is on the sender (Terms 2.10). Do wait on the correct To. Do not send a second transfer “to speed it up.” Do not pay a chat that offers to speed confirmations.
Avoid support tickets, speed-up DMs, and a second send while confirmations are still climbing
A ticket does not move miners. Refresh the explorer. Do not message chat every ten minutes at 0 Bitcoin confirmations. Write official support only after the explorer shows confirmed on this deposit, or failed / dropped. Then pack Order ID plus the full deposit TxID via the official support ticket pack. Use Bitsz support, Live Chat on typed bitsz.io, or support@bitsz.io.
Replace-by-Fee (RBF) on Bitcoin can replace an unconfirmed send with a new TxID; the old hash can drop. If your wallet already replaced a 0-conf send, track the new hash that still pays this deposit and amount. Do not change To. Do not treat RBF as a Bitsz credit switch. A DM “accelerator” is a scam. Use the fake exchange support checklist. Do not open a second widget. Do not reuse this one-time deposit on a new quote.
Branch after the explorer: keep waiting, treat a drop as unsent, or leave this checklist
Pick one branch from the explorer. Still confirming or 0 conf on the correct To: wait inside 30 minutes–72 hours. Failed or dropped, and the coins are back with you: do not send a repeat “just in case” until you know whether a replacement hash already pays this deposit. Explorer Success on the correct address, chip still Processing: stop this page and use the stuck crypto swap status checklist. If Live Chat already named AML or KYC, switch to the post-deposit KYC documents checklist. Chip Finished: read the payout hash, not this page. Wrong network is not “too few blocks.” When this order is Finished or clearly closed, create the next swap on the Bitsz Exchange widget. Do not click Exchange again to hurry the current deposit.
FAQ
How many confirmations does a Bitsz USDT TRC-20 deposit need?
Bitsz does not publish a retail TRC-20 number. Do not copy a CEX habit of about 19–20 onto this order. If this live card shows a waiting threshold, use that. Otherwise wait on tronscan.org while N climbs and To matches this unique deposit, inside 30 minutes to 72 hours (Terms 6.5). API samples (TRX 3, XRP 12) are docs examples, not a USDT rule.
The explorer says Success. Is the Bitsz order credited?
No. Success means the chain included the transfer. Bitsz credit is later, after required confirmations. If To, asset, and amount match and the chip is still Processing, use the stuck-status checklist, not a second send.
Should I open support at 0 confirmations?
No. Zero means the tx is still in the mempool. Refresh the You send explorer. Write official support only after confirmed on this deposit, or failed / dropped, then pack Order ID plus the full TxID.
Can I RBF or speed up Ethereum so Bitsz credits faster?
Do not treat fee bumps or a DM “accelerator” as a Bitsz credit switch. A Bitcoin RBF replacement gets a new TxID. If your wallet already replaced a 0-conf send, track the new hash that still pays this deposit and amount. Do not change To. Do not pay anyone to “speed confirmations.”
Is 1 Bitcoin confirmation enough?
bitcoin.org: 1 confirmation can be acceptable for low-value payments; 6 or more is the usual high-value rule of thumb; blocks average about 10 minutes. That is network guidance, not a Bitsz SLA. Do not assume 1 conf means credited on Bitsz.
I have no TxID yet, only a CEX Withdrawal ID.
Stop this page. Explorers do not index that internal ID. Use the CEX withdrawal delay checklist. Bitsz has not seen a deposit until a public hash exists.
Is this the stuck, payout, or support-packet guide?
No. Confirmed on the correct address but still Processing is the stuck-status checklist. Chip Finished is the payout explorer checklist. The first official message is the ticket-pack guide.
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.