Your crypto exchange order is still pending, or it says finished but the wallet looks empty. Panic second deposits and Telegram “unlock” chats make losses worse. First lock the Order ID and the live status label, then prove send-side and receive-side with TxIDs on the matching explorers. This stuck crypto swap checklist splits network delay, AML hold, and wrong destination so you either wait correctly or open one official support case.
Summary: If a swap is stuck or “not received,” refresh the live order page and copy the Order ID plus the exact status before you send again. Prove deposit progress and payout credit as two separate legs with TxIDs on the correct network explorers. Fork once into network delay, AML hold, or wrong address/network/memo. Wait while confirmations climb; escalate once via official chat or support@revbit.net inside Terms claim windows – never pay DM unlock fees.
On an instant non-custodial swap you send from your wallet and receive to an address you control. The exchange does not keep a balance like a bank app. A frozen UI can mean still confirming on-chain, a compliance review, or coins that went to the wrong place. Use the live order page as the source of truth. Do not open a second swap while the first deposit is unresolved.
Confirm the Order ID and what processing actually means
Start with identity, not with another transfer. An Order ID is the exchange’s internal ticket. A TxID (transaction hash) is the blockchain receipt. Explorers need the TxID. Support needs both.
- Open the live order page and refresh (F5), or open Exchange History in the cabinet if you used one.
- Copy the Order ID into a note before you change anything else.
- Write down the exact status label (pending, processing, sending, Executed, and similar).
- Note whether the UI shows a deposit TxID, a payout TxID, both, or neither.
- Check email for the same Order ID – do not invent a second order from an old quote.
RevBit Application Status docs list three checks: Exchange History, refreshing the order page without registration, and email. Executed means the exchange completed and funds were sent. It does not mean your wallet app finished syncing the token on the right network.
Do: treat the refreshed order page as the status source. Don’t: reuse a Fixed-rate deposit address from an old quote, and don’t treat “pending” as “failed.”
Workflow: Live order page (F5) → Copy Order ID → Note status label → Note deposit / payout TxID if shown → Only then open explorers or support.
Check send-side confirmations vs receive-side credit
Think of the swap as two mail runs. Send-side is your deposit reaching the exchange. Receive-side is the payout toward your destination. One leg can be fine while the other is still moving.
- Paste the deposit TxID into an explorer for the same network on the order (TRC-20 is Tron; ERC-20 is Ethereum – not interchangeable).
- Record Pending vs Success and whether confirmations are still climbing.
- If the order looks finished or Executed, paste the payout TxID into the receive network explorer.
- In the destination wallet, confirm the same asset and network (USDT on TRC-20 will not show on an ERC-20 list).
- If the asset needs a memo or destination tag (the “apartment number” on shared deposits), confirm that field was filled.
Need a refresher on pasting a hash? Use the blockchain explorer guide. Order ID is not a TxID – explorers will not resolve an internal order code.
| What you see | What it usually means | Next move |
|---|---|---|
| Deposit TxID Pending / low confirmations | Network still processing your send | Wait; do not double-deposit |
| Deposit Success; order still processing | Matching, sending, or review may be running | Keep Order ID; check for AML ask |
| Order Executed; payout Success; wallet empty | Wrong network view, token filter, or memo mismatch | Verify receive network + address; then one ticket |
| Explorer Success to an unexpected address | Wrong destination or reused address risk | Stop sending; gather proof for support |
Do: prove each leg on the matching explorer. Don’t: treat wallet speed-up/cancel guides as an exchange cancel – those only affect a still-pending wallet broadcast, not a confirmed deposit.
Separate network delay from AML hold from a wrong address
Pick one fork. Mixing them wastes time and invites scam chats.
Network delay: confirmations are still climbing and the UI has not asked for documents. Bitcoin blocks land about every 10 minutes; multi-confirmation deposits stretch far past a marketing “~2 min” average.
AML hold: the order freezes or asks for KYC. Terms note AML/KYC may delay an exchange. The AML Policy may freeze when risk is above 40% or high-risk labels appear. Deep refund-vs-resume steps live in the crypto swap AML check checklist – here, only recognize the fork and stop double-sending.
Wrong destination: explorer Success, but wrong network, wrong address, or missing memo/tag. Terms 2.12 recovery limits: 5% fee, minimum USD 20, only if amount > USD 30, review up to 14 days, refusal possible. That is not a return promise.
Quick rate context: Fixed locks a quote for 12 minutes at 1% + network fee; Floating is 0.5% + network fee until funds arrive. Late Fixed sends or reused Fixed addresses can hit Terms 2.10 recalculation paths – diagnose status first.
Do: name the fork before you message anyone. Don’t: treat climbing confirmations as an AML freeze, or an AML document request as “wait five more minutes.”
When to wait vs when to open support with TxID
Wait while the deposit is Pending or confirmations are rising and there is no KYC ask. Escalate once when a confirmed deposit stalls, or when Executed has no payout you can verify.
- Wait if send-side is Pending/confirming and there is no document request.
- Escalate once for confirmed-but-stuck or Executed-without-visible-payout cases.
- Build one packet: Order ID, deposit TxID, payout TxID if any, asset + network both legs, amount, time, screenshots.
- Send it through on-site chat or RevBit support (support@revbit.net) – not strangers who DM first.
- After you file, do not create a parallel “fix” swap or rebroadcast a full second deposit.
Do: one complete ticket with Order ID + TxID. Don’t: pay anyone an “unlock” fee in a private chat.
Claim windows and what not to send to strangers
Respect the clocks while evidence is fresh:
- Terms 2.11: claims on exchange applications within 7 business days to support@revbit.net with complete evidence.
- Terms 2.13: payment disagreement within 6 hours after order completion.
- Read RevBit Terms of Use before you assume a refund path.
Exchanges through the service cannot be canceled by REVBIT after the path runs (Terms 6.3). For before-vs-after-send cancel forks, use how to cancel a crypto swap order.
Never share a seed phrase, 2FA codes, or remote-access tools. Ignore inbound Telegram “support.” Cross-check the fake crypto exchange support scam checklist if anyone asks you to move funds off-site.
Do: keep contact on official chat, /support, or support@revbit.net. Don’t: paste secrets because someone quoted your Order ID.
What to do next after the status checklist
- Keep your note with Order ID, both TxIDs, networks, and the fork you chose.
- If you are still waiting, refresh on a schedule – do not spam new deposits.
- If you escalated, answer official requests only; ignore copycat accounts.
- When the case is clear and you are eligible, create any new swap on a fresh order UI from the RevBit homepage swap widget.
- For the happy path next time, keep how to swap crypto on an instant exchange beside this checklist.
EU/EEA residents cannot use the RevBit swap service – check eligibility before you start a new order.
Frequently asked questions
How long should a RevBit swap take?
RevBit homepage states about 2 minutes average exchange time and a 98% success rate as marketing figures, not a personal SLA. Still verify the live order page and explorers. Bitcoin multi-confirmation deposits can take much longer.
What if Bitcoin is unconfirmed?
Open the deposit TxID on a Bitcoin explorer. If status is Pending or confirmations are still low, wait. Do not open a second swap or send another full deposit “to push it through.”
Can I cancel a stuck swap?
After broadcast, there is no bank-style cancel for exchanges through the service (Terms 6.3). Use this checklist for processing-forever or finished-but-empty cases. For before-vs-after payment forks, read the cancel-swap tutorials – wallet speed-up/cancel is not an exchanger cancel.
Order says Executed but my wallet is empty?
Check the payout TxID on the receive-network explorer, confirm token + network in the wallet, and verify memo/tag if required. Then open one official ticket with Order ID + TxIDs inside the claim windows above.
When should I contact support?
Escalate when a deposit is confirmed but the order stalls, Executed has no verifiable payout, you get an AML/KYC ask, or amount/network errors are clear. Bring Order ID + TxID within 7 business days (Terms 2.11); use the 6-hour window for payment disagreement after completion (Terms 2.13).
Is this an AML hold or just a slow network?
Climbing confirmations with no document request point to network delay. A freeze or KYC request points to compliance review – follow the AML checklist for refund vs resume after a positive review.
Someone on Telegram offered to unlock my swap?
Stop. Do not pay fees, share seeds, or “verify” by sending coins elsewhere. Use only on-site chat, /support, or support@revbit.net, and run the fake-support checklist before you reply.