A safe exchange begins before any cryptocurrency is sent. The practical goal is to verify three things in order: that the website belongs to the service you intend to use, that the proposed exchange matches your original task, and that every irreversible transaction detail is correct. A professional-looking interface, positive reviews, or an encrypted connection cannot establish all three on their own.
The route below applies when you already hold BTC, ETH, or USDT and want to exchange it for another supported asset. It does not evaluate whether buying or selling a cryptocurrency is a suitable financial decision.
Start by defining the exchange you actually need
Write down the intended result before opening an exchange form. At minimum, record:
- the asset you will send;
- the asset you expect to receive;
- the blockchain network for each asset, where a network choice exists;
- the wallet address that should receive the result;
- whether the receiving platform requires a Memo, Tag, message, or other identifier;
- the minimum acceptable final amount after disclosed charges;
- the country from which you are using the service.
This short specification protects against a common failure: starting with one task and accepting a form that silently changes the asset, network, amount, or destination. If you need USDT on a particular blockchain, receiving USDT on another blockchain is not an equivalent result for operational purposes. Tether issues tokens on multiple protocols, and platforms do not necessarily support every one of them. [1]
Availability must be checked at the time of the operation. A service may support BTC, ETH, and USDT without supporting every possible pair, network, or direction involving those assets.
Check the exchange service before checking its rate
Open the correct domain independently
Do not enter through a link sent by a stranger, an unsolicited support account, a private message, or an advertisement that imitates a familiar brand. Open the domain through a source you already trust or type the known address yourself. Compare the complete domain name, including spelling and the ending after the final dot.
Confirm that the connection uses HTTPS, but do not treat the padlock as evidence that the operator is legitimate. Fraudulent websites can also use encrypted connections. The FTC recommends contacting a company through a website or number known to be genuine rather than through information contained in a suspicious message. [2]
Stop if the domain changes unexpectedly during the order, if a “support agent” sends a replacement deposit page, or if the site asks you to install remote-access software, disclose a seed phrase, export a private key, or share an authentication code. None of those secrets is needed to receive a normal blockchain transfer.
Identify the operator and its stated rules
Look for clear terms of service, privacy information, support channels, and an explanation of the order process. The available information should let you understand who handles the transaction, which restrictions may apply, and how to submit a problem report without relying on a social-media account.
If the service claims a registration, licence, or regulatory status, search for the exact legal entity in the relevant official register. Match names, locations, registration numbers, and authorised activities rather than accepting a badge or certificate image. Requirements differ by country and business model, and a registration may relate to anti-money-laundering obligations rather than investor protection. Registration also should not be interpreted as a government guarantee or approval. [3]
A missing registration is not interpreted the same way in every jurisdiction, so this check cannot be reduced to one universal licence. Stop when the operator makes a legal claim that cannot be matched to the appropriate authority or when the service appears unavailable to users in your country.
Separate reputation signals from proof
Search the service name together with terms such as “scam,” “complaint,” “withdrawal,” and “phishing.” Read recent negative reports as well as positive ones, paying attention to repeated patterns: substituted deposit addresses, unexplained demands for additional payments, inaccessible support, or requests to pay a separate “release fee.” The FTC recommends this kind of independent search before sending cryptocurrency. [4]
Reviews are leads, not proof. They can be outdated, manipulated, or related to an impersonation site rather than the genuine service. Compare the domain, dates, transaction type, and response from the operator. Stop if the only reassurance comes from testimonials displayed by the exchange itself or from accounts that pressure you to act immediately.
Guaranteed returns, claims of zero risk, and promises to multiply cryptocurrency do not belong in a normal asset exchange. U.S. regulators identify guaranteed high returns and little-or-no-risk claims as prominent warning signs of fraudulent crypto websites. [5]
Operation state map
-
State 1: Task defined
- Transition condition: the send asset, receive asset, required network, and destination wallet are written down.
- Success check: the intended result can be described without referring to the exchange form.
- If it does not match, stop: do not compare offers until you know exactly what must arrive and where.
-
State 2: Source data prepared
- Transition condition: you control the sending wallet and can verify the receiving address directly in the destination wallet or account.
- Success check: the destination confirms support for the exact asset and network, including any required Memo or Tag.
- If it does not match, stop: do not infer network compatibility from a similar address format or from the asset ticker alone.
-
State 3: Exchange identity checked
- Transition condition: the domain was opened independently, the operator’s terms and support channel are accessible, and applicable public claims can be verified.
- Success check: no unexplained domain changes, impersonation indicators, guaranteed-profit claims, or requests for wallet secrets appear.
- If it does not match, stop: close the page rather than asking an unverified messenger account whether the page is genuine.
-
State 4: Route and conditions checked
- Transition condition: the exact pair and networks are currently available, and the form shows the amount to send, estimated or stated amount to receive, applicable charges, limits, and rate conditions.
- Success check: the displayed route still produces the asset and network specified in State 1.
- If it does not match, stop: do not substitute another network or asset merely because the original route is unavailable.
-
State 5: Verification requirements understood
- Transition condition: you have reviewed the service’s stated compliance conditions before creating the order.
- Success check: you understand that requirements can depend on the exchange direction and the result of compliance checks, and you are prepared to follow only instructions shown through the verified service channel.
- If it does not match, stop: do not send funds if required information is unclear or if the route is not available in your jurisdiction.
-
State 6: Order details locked and compared
- Transition condition: an order has been created and its deposit asset, network, address, amount, validity conditions, and identifier are visible.
- Success check: every field matches the previously checked route, and the deposit address remains identical when compared character by character.
- If it does not match, stop: never send to an address supplied later through email, chat, comments, or direct messages.
-
State 7: Irreversible-action checkpoint passed
- Transition condition: the wallet’s final confirmation screen shows the correct asset, network, deposit address, amount, and any required Memo or Tag.
- Success check: the beginning, middle, and end of the address match the order; the wallet fee does not change the required transfer amount unexpectedly; no field has been populated solely from an untrusted clipboard entry.
- If it does not match, stop: cancel the wallet confirmation. Do not rely on support to reverse a blockchain transfer.
-
State 8: Transaction sent
- Transition condition: the wallet broadcasts the transaction and produces a transaction ID or hash.
- Success check: the hash appears in a suitable block explorer for the selected network, with the expected destination and amount.
- If it does not match, stop: do not create a second transfer merely because the exchange interface has not updated.
-
State 9: Network confirmation observed
- Transition condition: the transaction is included in a block and reaches the confirmation status required by the exchange.
- Success check: the explorer reports a successful transaction on the correct network, while the exchange moves the order from waiting for deposit to processing.
- If it does not match, stop: use the diagnostic branches below instead of sending more cryptocurrency.
-
State 10: Result confirmed or recovery started
- Transition condition: the payout transaction is issued or the service identifies a specific exception.
- Success check: the intended asset arrives at the destination address on the intended network and can be independently found in the relevant explorer.
- If it does not match, stop: preserve the order details and transaction hashes, then contact support through the independently verified domain. Do not pay an unsolicited recovery agent.
How to review the asset, network, and address
Asset and network are separate fields
BTC normally refers to the native asset of the Bitcoin network, while ETH normally refers to the native asset of Ethereum. USDT requires an additional network check because the token exists on multiple blockchains. An exchange form that says only “USDT” without identifying the deposit and payout protocols does not provide enough information for a safe transfer.
The sending wallet, exchange deposit route, and receiving wallet must all refer to the same network at each relevant step. Similar-looking names do not establish compatibility. If the requested network is unavailable, return to the task definition rather than selecting the closest-looking option.
Use the address shown inside the current order
Copying an address reduces typing errors but introduces clipboard risk. After pasting, compare several sections of the full address with the exchange order. A QR code should receive the same comparison: check the decoded address on the wallet’s confirmation screen rather than assuming the image is correct.
A small test transaction can sometimes reduce address uncertainty, but it is not automatically appropriate for an exchange order. The route may have a minimum deposit, a limited validity period, or rules against splitting one order into several payments. Use a test only if the current order terms explicitly allow it and the extra network fee is acceptable. Otherwise, create a separate eligible test order rather than sending an unapproved partial amount.
Memo and Tag fields are conditional
A Memo or Tag helps some custodial systems associate a shared blockchain address with the correct customer or order. It is not required for every asset or destination. If the order provides one, copy both the address and identifier exactly. If no identifier appears, do not invent one based on instructions from another platform.
Stop when the exchange says a Memo or Tag is mandatory but your wallet provides no way to enter it. Resolve the compatibility problem before sending.
Check the amount and charges before creating the transfer
Distinguish among the amount sent from your wallet, the blockchain network fee, any service charge reflected in the exchange calculation, and the expected payout. These values may be presented differently depending on the wallet and route. Do not calculate the final result from an advertised headline rate if the order provides a separate payout figure.
On Ethereum, a transaction requires a network fee and must be included in a validated block before it is successful. Token transfers may also require the network’s native asset to pay transaction costs. [6]
Before approval, check whether your wallet adds its network fee on top of the transfer or subtracts it from the entered amount. If the exchange expects an exact deposit, a deduction can create an underpayment. Also review whether the displayed rate can change, whether it has an expiry condition, and what happens when the received amount differs from the order. Stop if these consequences are not stated clearly enough to understand.
Once the identity, route, network, destination, conditions, and irreversible-action checklist all pass, you can open the exchange form and verify the currently available BTC, ETH, or USDT route. Recheck the live order rather than assuming that a previously viewed pair or network remains available.
What to verify while waiting
The transaction hash is the main bridge between the sending wallet, the blockchain, and the exchange order. Save it together with the order identifier and the exact deposit instructions. A wallet notification alone is not the final result.
For Bitcoin, a transaction becomes confirmed when it is included in the blockchain, and additional confirmations strengthen confidence that the payment will not be reversed by a chain reorganisation. The required number is determined by the recipient or exchange, not by a universal rule for every transaction. [7]
Ethereum transactions progress from broadcast and pending status to inclusion in a block, followed by stronger consensus states. A successful explorer status proves network execution, but it does not by itself prove that the exchange has completed its internal review or issued the payout. [6]
During this state, compare three views:
- Wallet: whether a transaction hash was created and which network was used.
- Block explorer: whether the transaction is pending, successful, failed, or absent, plus its destination and amount.
- Exchange order: whether the deposit is awaiting detection, awaiting confirmations, under review, processing, completed, expired, or marked with another stated status.
Do not resend merely because these systems update at different times. A duplicate transfer is a new blockchain transaction, not a request to accelerate the first one.
Delayed or incorrect transaction: diagnostic branches
No transaction hash exists
The wallet may not have broadcast the transaction. Confirm that the balance was actually debited and check the wallet’s activity on the selected network. If no hash exists in the wallet or explorer, there is no on-chain transaction for the exchange to identify.
Do not send again until you know whether the first submission failed locally or is simply not displayed correctly. If the wallet is controlled by another platform, use that platform’s verified support channel.
The transaction is pending in the explorer
A pending transaction has been broadcast but has not yet reached the required confirmed state. Check the selected network, fee information, and wallet-provided transaction management options. Do not use replacement, cancellation, or fee-bumping tools unless you understand how that wallet implements them; an incorrect replacement can create a different problem.
The exchange normally cannot credit a deposit before its required network confirmation state. Avoid opening new orders or sending additional deposits as a substitute for waiting.
The transaction failed
A failed on-chain transaction did not complete the intended transfer, even though a network fee may have been consumed. Verify the explorer’s destination, status, and transferred value. Do not assume the exchange received funds based only on the wallet’s initial submission notice.
The transaction is confirmed but the order is not credited
Compare the confirmed transaction with the order:
- deposit address;
- asset and token contract where applicable;
- network;
- amount;
- Memo or Tag;
- time and order validity conditions;
- required number of confirmations.
If all fields match, contact support through the independently verified website and provide the order identifier and transaction hash. The operation may be awaiting internal processing or a compliance review. Verification requirements depend on the exchange direction and the results of those checks, so clarify the current requirements rather than relying on an earlier transaction or a third-party description.
The wrong network was used
Stop all further transfers. Record the transaction hash, sending address, receiving address, asset, and actual network. Contact the operator of the destination address through its verified support channel.
Recovery depends on whether the recipient technically controls a compatible address and has a process for handling unsupported deposits. It may be unavailable, may require additional verification, or may involve a charge. No recovery should be assumed or promised.
The address or Memo was wrong
If the destination address is wrong, the exchange generally cannot reverse a completed blockchain transfer. If the address is controlled by an identifiable platform, contact that platform, but do not assume it can return the asset.
A correct shared deposit address with a missing or incorrect Memo may allow a custodial platform to investigate, but automatic credit can fail. Preserve evidence of account ownership and the transaction details. Follow only the destination platform’s official procedure and do not disclose private keys or seed phrases.
Regulators warn that cryptocurrency sent to fraudsters is generally difficult to recover, while supposed recovery services may demand further payments and create a second loss. [8]
The order expired or received a different amount
Do not send an extra payment to “unlock” or “release” the first one unless that instruction appears in the verified order procedure and you have independently confirmed it with official support. Ask how the service handles expired orders, underpayments, overpayments, and rate changes. Possible outcomes depend on the stated terms and compliance checks; a refund or particular exchange result cannot be guaranteed.
The payout hash exists but the wallet shows no balance
Open the payout transaction in an explorer for the stated network. Confirm the destination address, asset, status, and token contract where relevant. Some wallet interfaces do not immediately display every token even when the explorer records the transfer. Add or enable a token in a wallet only after verifying its official contract and network; an asset with the same ticker can be an unrelated token.
The verifiable finish line
The route is complete only when the payout can be independently matched across the exchange order, the correct block explorer, and the destination wallet: the intended asset was sent to the intended address on the intended network, the transaction has the required status, and the final received amount is consistent with the disclosed order conditions.
Some uncertainty can remain after a deposit is confirmed, including compliance review, processing delays, network congestion, or an unsupported-deposit investigation. Preserve the order record and both transaction hashes until the result is reconciled. If any asset, network, address, amount, or verification requirement no longer matches the task defined at the start, stop the route instead of trying to repair it with another irreversible transfer.
