A message claiming that your exchange order is “blocked,” “under review,” or “at risk” creates pressure to act before checking the facts. That pressure is the warning. Before sending BTC, ETH, or USDT, separate the actual exchange task from anything an alleged support agent asks you to do. Your safe route must begin with independently verified order details and end with an on-chain transaction that matches them.
Never disclose a recovery phrase or private key, approve an unfamiliar wallet request, install remote-access software, or send crypto to an address supplied only through an unsolicited message. Private keys authorize transactions and control access to the associated funds; giving one away can give another person the ability to move those funds. [1] The FTC also warns against clicking links in unexpected messages and against sending cryptocurrency in response to an impersonator’s instructions. [2]
The Operation State Map
Use this map as both a sequence and a stop/go decision tree. Do not skip forward because someone claims there is an emergency, an expiring verification window, or a special support-only wallet.
- Task: define the exchange you intended to make.
- Transition condition: you can state which asset you are sending, which asset you expect to receive, and where the result should arrive.
- Success check: the plan exists independently of any direct message, call, advertisement, or search-result chat.
- Stop if it does not match: the “support agent” changes the asset, recipient, network, amount, or purpose of the operation.
- Input data: record the route before creating an order.
- Transition condition: the required pair, direction, asset, network, and destination are currently available.
- Success check: you understand what will be sent, what may be deducted as a disclosed fee, and what destination should receive the result.
- Stop if it does not match: availability is assumed from an old screenshot or message. BTC, ETH, and USDT may be supported, but that does not mean every pair, blockchain network, or exchange direction is available for every order.
- Verification: authenticate the service route and order details.
- Transition condition: you have reached the service independently rather than through the alleged support message.
- Success check: the order is visible in the legitimate interface, and its asset, network, deposit address, amount conditions, and status agree with your original task.
- Stop if it does not match: a person asks you to continue in a private chat, use a replacement address, pay an “unlock” charge, or transfer funds to a “safe,” “verification,” or “recovery” wallet.
- Action: review the irreversible transaction.
- Transition condition: the wallet’s final confirmation screen matches the verified order.
- Success check: the asset, network, full destination address, Memo/Tag if required, amount, and wallet-displayed network fee are correct.
- Stop if it does not match: any field differs, the wallet displays an unexplained contract interaction, or you are being told to ignore a warning.
- Waiting: track evidence, not messages.
- Transition condition: your wallet has produced a transaction ID or transaction hash.
- Success check: the transaction appears on an appropriate blockchain explorer with the intended destination and amount, then gains the confirmations required for that route.
- Stop escalating payments: a delay does not justify sending a second deposit, a release fee, extra gas to a stranger’s address, or your recovery phrase.
- Confirmed result or recovery route.
- Transition condition: the on-chain record and exchange order refer to the same transaction.
- Success check: the expected asset reaches the destination you control and the order shows a consistent completed status.
- Recovery route: if the records disagree, preserve the order identifier, transaction hash, screenshots, timestamps, asset, network, and addresses. Contact support only through the independently verified service interface. Do not pay anyone who promises guaranteed recovery.
Verify the Contact Before Discussing the Transaction
Fake support often appears immediately after a user posts publicly about a delayed transaction. A profile name, logo, verified-looking image, or knowledge of your public transaction hash does not prove that the sender works for the exchange. Blockchain transaction data is public, so repeating details visible in an explorer is not evidence of privileged access.
Treat the contact as fraudulent if it asks for a seed phrase, private key, wallet backup, one-time authentication code, screen sharing, remote device access, or a wallet connection unrelated to the exchange order. Also stop if the person introduces a new payment that was not disclosed in the order. An unexpected demand to buy or send cryptocurrency is a standard impersonation pattern identified by the FTC. [2]
If you initiated a support request, compare the reply with the support channel shown inside the independently opened service. Do not authenticate a message by calling the number it contains, replying to the same account, or opening its link. The sender controls all three.
Match the Asset, Network and Address
Asset and network
BTC, ETH, and USDT are not interchangeable labels. BTC is transferred through the selected Bitcoin route. ETH may be transferred on Ethereum or through another route supported by the sender and recipient. USDT exists on multiple blockchain protocols, so selecting “USDT” without matching the network is insufficient. Tether directs users to its current supported-protocol information because protocol support can change. [3]
The sending wallet, exchange order, and receiving platform must name the same network. Similar address formatting is not proof of compatibility. If the order does not clearly show the network, stop instead of asking an unsolicited agent to choose it for you.
Deposit address
Copy the deposit address from the verified order and compare it with the address displayed on the wallet’s final signing screen. Check the complete address where possible, not only a few characters at each end. Clipboard-replacement malware and deceptive interfaces can substitute another valid-looking address after copying.
A confirmed Bitcoin transaction generally cannot be cancelled; a refund would depend on the recipient returning the funds. Bitcoin’s official guidance therefore recommends verifying the full receiving address and considering a small test transaction before a larger transfer. [1] A test transfer can reduce address uncertainty, but only when the exchange route accepts separate deposits and the additional network fee is understood. Do not assume that every order permits split payments.
Memo or Tag
Some asset and deposit routes use an additional identifier such as a Memo or Tag to associate a shared address with a specific account or order. If the verified order supplies one, reproduce it exactly. If it does not, never add a code received in a chat. A missing or incorrect identifier can prevent automatic crediting even when the blockchain transaction reaches the displayed address.
Check the Amount, Fees and Final Wallet Prompt
Distinguish four figures before signing: the amount you intend to send, the network fee shown by your wallet, any service charge disclosed in the order, and the estimated or stated amount to be received. Do not invent a deduction when these figures are unclear, and do not rely on a support message to explain a discrepancy.
Ethereum transactions require a network fee and include fields such as the receiving address, value, gas limit, and fee parameters. After submission, the transaction receives a hash, enters the pending pool, and must be included in a validated block. [4] The exact fee and waiting time can vary with network conditions and wallet settings, so a legitimate-looking number in a message is not evidence that the message is genuine.
Stop at the wallet confirmation screen if it shows:
- a different destination address or network;
- an amount that does not match your reviewed order;
- an unlimited token approval or unexplained smart-contract action;
- a request to sign text or data whose purpose you cannot verify;
- a second recipient described as a fee, reserve, validation deposit, or security wallet;
- an instruction to disregard the wallet’s risk warning.
Requirements for identity or compliance checks can depend on the exchange direction and the results of compliance screening. Confirm the current requirements before creating an order. A person who offers to bypass checks, fabricate documents, or “whitelist” a wallet for an extra crypto payment is taking you outside the valid route.
Proceed Only After the Checks Agree
Once the intended asset, exchange direction, network, destination address, amount conditions, applicable verification requirements, and access route all agree, you can open the exchange service and create a verified order. Recheck the generated details rather than treating a previous order, saved address, or screenshot as reusable.
Before broadcasting the transaction, save the order identifier and note any stated validity conditions. Market prices can change, and a quote or order may no longer apply if its stated conditions expire. If the interface changes the amount, address, or route before you send, return to verification instead of forcing the original transaction through.
If the Transaction Is Delayed or Appears Wrong
Start diagnosis with the transaction hash. A message saying “payment not found” is not enough to determine what happened.
No transaction hash was created
The wallet may not have broadcast the transaction. Check the wallet’s activity history and balance. Do not resend automatically: first establish whether the original transaction exists locally or on-chain. If you exposed a seed phrase or private key during the process, treat the wallet as compromised and use guidance from the wallet’s genuine provider to protect remaining assets.
The transaction is pending
Confirm that the transaction appears on the explorer for the network actually used. For Bitcoin, confirmation begins when miners include the transaction in a block; the timing is probabilistic, and a fee below current network priority can extend the wait. [1] For Ethereum, verify the transaction status, destination, transferred token or ETH value, and whether the transaction is still pending, included, or failed.
Do not send a separate “acceleration payment” to an address supplied by support. If your wallet provides a legitimate fee-management feature, use only its documented controls and understand whether it replaces the original transaction or creates another one.
The transaction is confirmed but the order is not credited
Compare the confirmed asset, network, destination address, amount, and Memo/Tag with the order. Then check whether the exchange requires more confirmations or an internal compliance review. Provide genuine support with the transaction hash and order identifier, but never the seed phrase or private key.
If the network, address, or Memo/Tag was wrong, document exactly what was sent. Recovery may be technically impossible or may depend on whether the recipient controls the address and supports a recovery procedure. No support agent can honestly guarantee the return of an irreversible transfer.
The transaction went to an address supplied by fake support
Stop communicating with the impersonator and do not pay a recovery fee. Preserve the chat, account identifiers, wallet addresses, transaction hashes, email headers, screenshots, and payment requests. Report the account through the platform where contact occurred and notify the legitimate exchange through its verified channel.
Be cautious of anyone who later claims to be an investigator, blockchain specialist, or recovery service and demands payment first. The FTC warns that recovery scams specifically target people who have already lost money and may demand cryptocurrency for supposed assistance. [5] Reporting options and legal procedures differ by country, so use the relevant regulator or law-enforcement channel for your jurisdiction without assuming that reporting guarantees reimbursement.
What Counts as a Completed Route
The route is complete only when the blockchain record matches the verified order and the expected BTC, ETH, or USDT result is credited to the destination you intended to use. A support message, screenshot, transaction notification, or “completed” badge by itself is not sufficient if the on-chain and account records disagree.
Some uncertainty can remain while a transaction is pending, awaiting the route’s required confirmations, or undergoing a disclosed compliance review. That uncertainty should lead to evidence gathering and verification—not to a new address, secret phrase disclosure, remote access, or an additional payment. If any instruction changes the original asset, network, recipient, or purpose, stop and rebuild the route from the first state.