A crypto exchange safety check should answer one practical question: do the domain, exchange direction, asset, network, address, amount, and stated conditions all describe the same transaction? The process below helps identify inconsistencies before BTC, ETH, or USDT leaves your wallet. It cannot guarantee that a service is safe, prevent every technical failure, or eliminate market, compliance, and counterparty risk.
Express Check: Stop Signals Before You Create an Order
Do not start with reputation claims or a prominent exchange rate. First look for conditions that justify stopping immediately. A convincing interface can still be a phishing copy, and an attractive quote is irrelevant if the payment address or network is wrong.
- Stop if the domain differs from the address you intended to visit, contains an unexpected spelling change, or was opened from an unsolicited message or advertisement.
- Stop if the site, an alleged support agent, or a form asks for a seed phrase, private key, wallet backup, or remote access to your device. A recovery phrase controls the wallet and must not be disclosed. [1]
- Stop if anyone promises guaranteed returns, risk-free profit, or a bonus for sending cryptocurrency first. The FTC identifies guaranteed profit claims as a characteristic of cryptocurrency scams. [2]
- Stop if the sending and receiving sides show different networks, or if the selected network is not supported by both the destination and your wallet.
- Stop if the deposit address changes after you copied it, cannot be reproduced from the active order, or differs between the text field and QR code.
- Clarify before proceeding if the final amount, fee treatment, limit, verification requirement, or expiry condition is missing or changes without explanation.
USDT requires particular attention because Tether tokens exist on multiple blockchain protocols. Asset ticker alone is therefore insufficient: “USDT” must be paired with the exact network supported for that order. Tether also notes that protocol support can change, so current availability should be checked rather than inferred from an old transaction or saved address. [3]
Two-Pass Pre-Operation Verification Card
Complete the first pass while evaluating the proposed exchange. Complete the second pass immediately before the irreversible action: signing a wallet transaction, confirming a withdrawal, or sending funds. Do not enter real addresses, keys, seed phrases, or personal data into this article or an informal checklist shared with another person.
Pass 1: Verify the Transaction Context
| What to compare | Independent confirmation | What a mismatch means |
|---|---|---|
| Domain and page origin | Use a previously verified bookmark, independently typed domain, or trusted account record. Inspect the full browser address rather than the page logo or search-ad headline. | A spelling change, unfamiliar subdomain, redirect, or certificate warning may indicate phishing. Stop and reopen the service through a known route. |
| Exchange direction | Compare the order summary with your intended action: the asset you send and the asset you expect to receive. | Reversed fields can produce a valid but unintended order. Do not assume support can reinterpret a completed transfer. |
| Asset identity | Check the full asset name and ticker in the order, wallet, and receiving platform. For tokens, consult the project’s official documentation when contract identity is relevant. | A similar ticker does not establish that two tokens are the same. An unsupported or imitation token may not be credited. |
| Selected network | Compare the network label in the order with the withdrawal network in the sending wallet and the deposit network at the destination. Use official project documentation and the appropriate blockchain explorer for technical confirmation. | If one side says Ethereum and another says TRON, for example, the fields do not describe the same transfer. Stop rather than choosing a network based only on its fee. |
| Pair and route availability | Confirm that the exact send asset, receive asset, and required network are currently offered before creating the order. | General support for BTC, ETH, or USDT does not prove that every pair, network, or direction is active. |
| Quoted conditions | Read the active order summary for the amount sent, estimated or fixed treatment where stated, fee handling, limits, expiry rules, and amount expected at the destination. | Missing or internally inconsistent terms require clarification. A screenshot from an older order is not confirmation of current conditions. |
| Verification and compliance conditions | Check the requirements shown for the specific exchange direction before creating the order, including any request that may arise from compliance review. | Requirements can vary by transaction and review result. If you are unwilling or unable to meet the stated lawful conditions, do not send funds. |
| Source of instructions | Compare payment details with the active order inside the verified service interface. Treat instructions received only through direct messages, comments, or unofficial chat accounts as unconfirmed. | A request to replace the displayed address or send an additional “unlocking” payment is a strong stop signal. |
For the service described here, supported assets include USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX, with additions planned over time. This does not mean every pair, direction, or network is available. Check the exact route before each operation. Ruble-to-cryptocurrency bank-card exchanges and the reverse direction are planned rather than currently available and should not be treated as an active option.
Pass 2: Recheck the Critical Fields Before Sending
| What to compare | Independent confirmation | What a mismatch means |
|---|---|---|
| Destination address | Compare the complete address in the wallet confirmation screen with the address in the active order. Check more than the first and last few characters, especially after using the clipboard. | Even a small difference may indicate a copy error, clipboard malware, address poisoning, or a changed order. Cancel the transaction and obtain the address again. |
| QR code versus text | After scanning, compare the address decoded by the wallet with the text address shown in the order. | A QR code is only an input method. If it resolves to different data, do not approve the transfer. |
| Network | Repeat the network comparison on the wallet’s final approval screen. Confirm that the destination explicitly accepts the asset on that network. | A compatible-looking address format does not prove network compatibility. Wrong or unsupported destinations can result in loss, and recovery may be unavailable or discretionary. [4] |
| Memo, Tag, message, or payment identifier | If the order supplies an additional identifier, compare it exactly with the corresponding wallet field. If no identifier is shown, do not invent one. | An omitted or incorrect required identifier can prevent automatic attribution even when the blockchain transfer succeeds. |
| Amount to send | Compare the wallet amount with the active order, including the asset denomination and whether the wallet deducts its network fee separately or from the entered amount. | A different amount may fall outside the order conditions or lead to a different credited result. Do not “round approximately” unless the order explicitly permits it. |
| Expected amount to receive | Review the final order summary immediately before payment and distinguish an estimate from a fixed amount where the service states that distinction. | An unexplained change requires clarification. Volatility, quote expiry, network costs, or order conditions may affect the result, but the applicable rule must come from the active order rather than assumption. |
| Order status and validity | Confirm that the order is still active and that its payment details have not expired or been replaced. | Sending to an expired order can delay attribution or require manual investigation. Create a new order if instructed rather than reusing old payment details. |
| Final authorization screen | Read the hardware wallet, mobile wallet, or exchange withdrawal screen itself. Treat the data on the signing device as the final authorization request. | If the signing screen differs from the order, cancel. Do not approve first and investigate later. |
Bitcoin transactions are designed to be irreversible after confirmation, while confirmed transaction data is recorded on the blockchain. This is why the second pass must happen before approval rather than after funds are sent. [5]
After completing both passes, one possible next step is to check the current exchange conditions and available route.
How to Classify the Result
| Outcome | When it applies | Next action |
|---|---|---|
| Continue checking | The verified domain, direction, asset, network, address source, amount, and order terms are consistent, with no request for wallet secrets. | Proceed to the next verification stage. This classification is not a guarantee of safety or successful execution. |
| Clarification required | A condition is incomplete or ambiguous: verification requirements are unclear, the quote changed, a Memo/Tag instruction is uncertain, or the selected route is not visibly available. | Pause without sending funds. Use the service’s official support channel reached from the verified domain and retain the order identifier. |
| Stop | The domain is suspicious, networks conflict, the address changed unexpectedly, secret wallet data is requested, or guaranteed profit is promised. | Close the page, reject the wallet request, and do not make a “test payment” to the questionable address. |
Control Route Before, During, and After the Exchange
Before the Operation
- Open the service through a verified route and inspect the full domain.
- Define the intended direction in plain terms: what you send, what you receive, and on which network.
- Review the current terms, limits, amount calculation, and applicable verification conditions.
- Complete Pass 1 of the card.
- Create the order only after the route is confirmed as available.
- Complete Pass 2 on the final wallet or withdrawal screen.
While the Transfer Is Pending
- Keep the order page and order identifier available, but never expose a seed phrase or private key to “speed up” processing.
- Use the transaction hash, or txid, in an explorer for the selected blockchain. Confirm that the explorer shows the intended sending address where applicable, destination, asset, amount, and network status.
- Distinguish blockchain confirmation from service processing. A transaction can be visible on-chain while the receiving system is still validating or attributing it.
- Do not send a duplicate payment merely because the interface has not updated. First check whether the original transaction was broadcast and whether the txid is valid.
After Confirmation
- Compare the amount credited with the final order result and the applicable terms.
- Confirm that the receiving wallet or account shows the intended asset, not merely a similar ticker.
- Record the order identifier and txid for later reference.
- If the result differs, preserve factual evidence before refreshing away the relevant screens.
Recovery and Diagnostics When Something Does Not Match
A delayed status, amount difference, or changed field does not identify the cause by itself. Diagnose the transaction before requesting action, and do not assume that recovery or reversal is possible.
| Problem | Diagnostic actions | Avoid |
|---|---|---|
| Status remains pending | Check whether the wallet produced a txid, whether the transaction appears in the correct blockchain explorer, and whether it is pending, confirmed, failed, or absent. Compare the time and destination with the order. | Do not resend automatically or pay an unsolicited “acceleration” invoice. |
| Transaction is absent from the explorer | Verify that the correct network and explorer were selected. Check the wallet’s transaction history and whether the transfer was actually broadcast. | Do not treat an internal wallet label as proof of an on-chain transaction. |
| On-chain confirmation exists, but the order is not credited | Compare the destination address, network, asset, amount, Memo/Tag, txid, and order validity. Contact official support with the order identifier and transaction details if they match. | Do not disclose recovery phrases, private keys, passwords, or unnecessary identity documents through unofficial channels. |
| Received amount differs | Compare the original order terms, amount sent, network-fee treatment, quote status, and final calculation. Ask for an itemized explanation if the difference is not covered by the displayed conditions. | Do not infer the cause from market movement alone or accept an explanation that refers to terms not shown for the order. |
| Address or order data changed | If no transfer was sent, stop and recreate the verification path from the known domain. If funds were sent, preserve both versions, the order identifier, timestamp, and txid, then contact official support. | Do not send additional funds to “synchronize,” “verify,” or “unlock” the first transfer. |
| Wrong network or destination used | Document the txid, asset, network, destination, and order identifier. Contact the receiving party through its official channel and ask whether technical recovery is possible. | Do not assume recovery is guaranteed. Tether’s own recovery information, for example, describes assistance as case-specific and discretionary. [4] |
Threats Directly Relevant to an Exchange Operation
Phishing
A phishing page may reproduce branding, order forms, and support chat while changing the domain or deposit address. Check the domain after every redirect, including redirects from advertisements and messages. Ethereum’s official security guidance specifically warns that phishing links can lead to imitation sites that request a seed phrase, password reset, or transfer. [1]
Address Substitution
Clipboard malware or a deceptive address-history entry can replace the intended destination with an attacker’s address. Copy the address from the active order, paste it into the wallet, and compare the complete result before signing. For larger or unfamiliar operations, a small test transfer may reduce the amount exposed to some addressing errors, but it does not prove that the service, later address, quote, or remaining transaction is safe.
Wrong Network
The same asset name can appear on more than one blockchain. This is especially relevant to USDT: the sending wallet’s network, the order’s deposit network, and the receiving platform’s support must match exactly. Never choose a network solely because it appears cheaper, faster, or was used in a previous order.
Seed Phrase or Private-Key Exposure
No exchange troubleshooting step requires handing over the secret that controls your wallet. Anyone with the recovery phrase can control its accounts and assets, and screenshots may expose secrets through cloud synchronization. [1]
Guaranteed-Return Claims
A normal exchange order states transaction conditions; it does not need to promise investment profit. Claims of guaranteed returns, risk-free income, or multiplied cryptocurrency are reasons to stop, regardless of testimonials, urgency, or apparent endorsements. [2]
Minimal Record-Keeping Protocol
Keep only the information needed to trace and discuss the operation:
- order identifier;
- transaction hash or txid;
- asset and selected network;
- amount sent and amount shown as received;
- order creation and transfer times;
- the applicable order conditions or screenshots that do not expose secrets or unnecessary personal information;
- official support case identifier, if one is created.
Do not store a seed phrase, private key, wallet backup, password, authentication code, or full set of identity documents beside the transaction record. Avoid publishing addresses and transaction details unnecessarily: public blockchains can preserve transaction information permanently, and combining it with personal information can reduce privacy. [6]
The final decision should rest on consistency, not a single trust signal. A recognizable design, a favorable quote, or an on-chain address cannot substitute for matching the domain, direction, asset, network, payment details, current conditions, and final authorization screen. If any critical field conflicts, pause before the transaction becomes difficult or impossible to reverse.
