The swap timer hit zero, and you already tapped Send, or your exchange still shows Processing. Do not pay the same Bitsz deposit address again. First freeze extra sends. Then find out whether a public TxID exists. Next compare the order expiry time with explorer time, read Terms 2.2.1 and 6.5, and send one official packet. This expired crypto swap deposit checklist keeps you from doubling a late deposit.
Quick answer: Stop extra sends. If no outgoing TxID, do not pay the expired address; open a new Bitsz order and copy a new address. If a TxID already exists, do not open a parallel order. Compare expiry with explorer time, not the wallet pending chip. Terms 2.2.1 do not keep the old 12-minute Fixed lock after expiry. Terms 6.5 may refuse the request and return coins to the sender with no extra fee (manual, up to 68 hours). Write official support once with Order ID plus TxID.
Bitsz is an instant crypto exchange on bitsz.io (homepage: established 2023). The widget shows You send, You receive, Network, Floating or Fixed, and Recipient’s address. Homepage how-to copy says send to the one-time address and track until Finished. An expired quote is not a standing instruction.
Use this page only when the timer already ran out, or the send hit the chain after that timer. If the deposit confirmed on the correct address inside the window and status still sits, use the stuck crypto swap status checklist.
Stop before a second send to the same deposit address (checklist)
Freeze extra sends. Do not top up that address.
The countdown is gone, and coins may already be in flight. People top up the same address or open a second order “just in case.” Bitsz assigns a unique address per transaction (Terms 2.4). The chain can still accept a second payment. Auto-credit onto the first order is not a Bitsz rule. A TxID is the public hash of a payment. Delay is not a cue to send again (Terms 2.6).
How the check runs:
First freeze extra sends. Then hunt the outgoing TxID, or confirm there is none. Next compare expiry with explorer times. Then read Terms 2.2.1 and 6.5. After that, send one packet to official support.
- Step 1: Freeze extra sends to this deposit address.
- Step 2: Look in the wallet or CEX for an outgoing TxID to that address.
- Step 3: No TxID: do not pay the expired address; use a new order and a new address.
- Step 4: TxID exists: copy it. Do not bump, replace, or send again.
- Step 5: Write expiry, explorer first-seen, and confirmation in one timezone.
- Step 6: Read Terms 2.2.1 and 6.5. Do not invent a refund button.
- Step 7: Send one official packet: Order ID plus TxID plus times.
- Step 8: Wait for a written path. A new large amount needs a new order.
Do: Treat this address as spent for this order, even if the timer is dead. Do not: Use Replace-by-Fee, a speed-up, or a second order to “save” the old Fixed number.
How to split a wallet that never sent from a TxID broadcast after the timer
No public hash? Do not pay the expired address.
Broadcast means the payment left your wallet into the public network. Confirmed means a validator included it in a block. Ethereum.org lists that order: hash, then pool, then a block. A wallet “Sent” chip is not Bitsz detect. Neither Fixed nor Floating is a reason to pay twice.
| What you see | Likely class | Do | Do not |
|---|---|---|---|
| Timer zero; no outgoing TxID; balance still in the wallet | Never broadcast | New order; new one-time address | Pay the expired address |
| TxID first appears after order expiry | Late deposit | One support packet | Second send or second order |
| TxID first appears before expiry; confirmations after | In-flight / slow chain | Save both times; one packet if status sits | Bump, RBF, or a makeup payment |
| Wallet says Sent; explorer has no hash yet | Local pending or CEX queue | Wait for a public TxID, then compare times | Assume Bitsz already detected it |
If amounts disagree, use the amount mismatch refund checklist. If the network is wrong, use the wrong-network guide. No TxID: copy a new one-time address from a fresh order. TxID exists: do not open a parallel order.
Do: Hunt the outgoing hash before you touch the widget again. Do not: Pay an expired address because the wallet still shows the copied destination.
Compare the order expiry time with on-chain broadcast time, not the wallet pending chip
Match expiry with explorer time, not the pending chip.
Write three stamps in one timezone: when the Bitsz timer hit zero; when the hash first appeared in an explorer for the same Network chip; when it landed in a block. Terms 2.2.1 look at detection in the blockchain network, not the moment you pressed Send.
Match the explorer to the order network: Bitcoin on mempool.space, Ethereum / ERC-20 on etherscan.io, TRON / TRC-20 on tronscan.org. First-seen is when that explorer’s node heard the unconfirmed transaction. Two explorers can disagree.
A mempool is the waiting room of unconfirmed transactions. A CEX “Processing” row is still inside that exchange.
Do: Compare expiry with explorer time on the same network. Do not: Treat the wallet pending chip as Bitsz detect. If the deposit confirmed inside the window and status sits, switch to the stuck-status checklist.
Check the Bitsz Terms 2.2.1 and 6.5 checklist after a late deposit
Read the live Terms of Use. Do not quote a rival exchanger’s claim window.
Terms 2.2.1 (Fixed): fee 1% plus network fee; the rate is frozen for 12 minutes. If the market moves more than 1.3% before the deposit is detected in the blockchain network, the offer is a refund or continuation at market rate. That clause is about the late Fixed price, not a request to send more.
Terms 2.2.2 (Floating): fee 0.5% plus network fee; not fixed until funds are received and the exchange is completed. Terms 2.10 (Bitsz): floating is recalculated only downward; client-side delays are on you. Pick a mode before send in the Fixed vs Floating guide. After Send, you cannot switch. Fixed can be temporarily unavailable; read the live pill.
Terms 6.5: exchanges are processed within 30 minutes to 72 hours. The platform may refuse a request and return coins to the sender’s address with no extra fee. Live Terms add that this refund is processed manually and may take up to 68 hours. That is a possible refuse-and-return, not an auto-refund and not the old Fixed number. Returns go to the sender. The widget has no refund-address field.
The 5% fee and 7 business days sit in the AML policy after a positive AML review of blocked assets. Do not apply them to a late deposit unless support says the order is in AML review.
Do: Quote 2.2.1 and 6.5 as written. Do not: Invent a TIME_EXPIRED screen, a Cancel button, or a “Refund me” panel.
Send Order ID plus TxID to official support (not a stuck-status fix)
One packet, one channel. Write Bitsz through bitsz.io/support and support@bitsz.io (Live Chat on bitsz.io). Include Order ID, Fixed or Floating as shown, You send, deposit address, network, full TxID, explorer URL, and expiry versus first-seen versus confirmation.
Do not paste that packet into the Telegram showcase at t.me/bitsz_io. Do not send a seed phrase or pay an “unlock” bill. If a stranger DMs you as “support” after expiry, use the fake exchange support checklist. If the deposit host is not bitsz.io, stop.
Follow only what support actually said. If they send a return TxID, match network, asset, and sender address. If they offer market continuation under 2.2.1, that is not a request to top up the old deposit.
Do: Send one official packet and wait. Do not: Open a second Bitsz order for the same in-flight coins.
Next steps after the expired swap checklist
- Keep the freeze on extra sends until support writes a path.
- If there was never a TxID, only then create a new order and copy a new one-time address.
- If support returns coins, verify the return TxID before you spend them.
- For a new large amount after this case closes, start a fresh order. Do not reuse the old deposit.
- Track the new order until Finished. Do not assume homepage marketing times apply to a late deposit.
See the test-swap-before-large-transfer checklist for a new large send. The useful next click is official support, not a second payment.
FAQ
Should I send again to the expired address?
No. Stop. Bitsz assigns a unique, one-time address per transaction. Save Order ID and TxID, then write official support.
Is an expired order the same as a stuck processing order?
No. If the deposit was detected on the correct address inside the window and status still sits, use the stuck-status checklist. This page is for a timer that already ran out.
Does the 12-minute Fixed lock still apply after expiry?
Do not assume the frozen quote still applies. Terms 2.2.1 freeze the rate for 12 minutes. If the market moves more than 1.3% before on-chain detect, the offer is a refund or market rate.
Can I open a new order if I never broadcast?
Yes. No TxID: do not pay the expired address; open a new order. TxID exists: do not open a parallel order.
Does Terms 6.5 guarantee a full refund of a late deposit?
No. Exchanges are processed in 30 minutes to 72 hours. The platform may refuse a request and return coins to the sender with no extra fee. Live Terms say that refuse-and-return is manual and may take up to 68 hours. That is not the old Fixed rate.
Is the AML 5% refund / 7 business days the fee for an expired order?
No. Those figures sit in the AML policy after a positive AML review. Use them only if support says the order is in AML review.
The wallet still shows pending after the timer. Should I bump the fee?
Do not treat Replace-by-Fee as a way to restore a Fixed lock. If a public TxID exists, compare expiry versus explorer time and send one official packet.
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.