A cryptocurrency symbol alone does not identify a safe transfer route. The receiving side must support the exact asset on the exact blockchain selected by the sending wallet. The address, any required Memo or Tag, the amount, and the active exchange order must also remain consistent until the transaction is approved.
The two-pass pre-operation check below is designed to catch discrepancies before an irreversible action. It cannot eliminate every risk: a compromised device, a convincing phishing page, incorrect information supplied by a recipient, or a last-second change in transaction details can still cause loss. Confirmed blockchain transfers generally cannot be cancelled, while recovery from an unsupported network, wrong address, or missing identifier may be impossible or dependent on the receiving service’s technical capabilities. [1]
Express Check: Stop Signals Before You Prepare the Transfer
Do not proceed to the full review if any of these conditions is present:
- The website domain differs from the known service domain, contains an unexpected spelling variation, or was opened from an unsolicited message.
- The exchange order names one cryptocurrency, but the sending wallet is prepared to transfer another.
- The receiving side specifies one network, while the wallet’s withdrawal screen shows another.
- The network is inferred from the address format rather than explicitly confirmed. Different assets or networks can sometimes use visually similar or identical address formats, so appearance is not proof of compatibility. [2]
- The address or Memo/Tag changed after copying, scanning, or switching applications.
- The service’s current order screen, wallet preview, and independently obtained receiving details do not show the same amount or destination.
- A person claiming to be support asks for a seed phrase, private key, remote device access, or a transfer to a “verification” wallet.
- The transaction is being promoted through guaranteed returns, risk-free income, or a promise to multiply the transferred cryptocurrency. Government consumer guidance identifies guaranteed crypto profits as a scam indicator. [3]
If a stop signal appears, closing the transaction window is safer than attempting to resolve the inconsistency under time pressure. Start a new check from a trusted source only after the cause is understood.
How to Read the Two-Pass Check Card
Each row contains three elements: what must match, where to obtain confirmation independently, and what a discrepancy means. “Independent confirmation” does not mean repeating information from the same browser tab. It means comparing the order with another authoritative source, such as the receiving wallet’s deposit screen, the sender’s wallet preview, official project documentation, or the appropriate blockchain explorer.
The possible outcomes are:
- Continue checking: the information agrees, but the remaining fields still require review.
- Clarify: the information is incomplete, ambiguous, outdated, or dependent on conditions that have not been confirmed. Do not send while clarification is pending.
- Stop: a critical field conflicts, the source cannot be authenticated, or transaction details change unexpectedly.
None of these labels is a guarantee of safety. They indicate what to do with the review, not what the blockchain will ultimately do.
Pass One: Verify the Operation Context
The first pass establishes what operation is actually being prepared. Complete it before copying an address into the sending wallet.
| Check | What to verify | Independent confirmation | Meaning of a discrepancy |
|---|---|---|---|
| Domain and session | The domain is the expected one, the connection has not been opened through an unsolicited advertisement or message, and the order belongs to the current authenticated session where authentication is required. | Use a previously saved bookmark, independently typed domain, or another official communication channel already known to be genuine. Compare the full domain rather than the logo or page design. | A spelling variation, unexpected subdomain, certificate warning, forced download, or seed-phrase request is a stop outcome. Phishing pages can imitate wallet and exchange interfaces closely. [4] |
| Operation direction | The asset being sent and the asset expected in return are shown on the correct sides of the order. | Compare the order summary with the balance that will be debited and the destination wallet that should receive the result. | If the direction is reversed or the interface is unclear, clarify. If confirming the order would send an unintended asset, stop. |
| Asset identity | The full asset name and symbol match in the order, sending wallet, and receiving instructions. For tokens, confirm the intended token rather than relying only on a familiar ticker. | Use the current order page and the receiving platform’s asset-specific deposit screen. Where a token contract is relevant, obtain it from official project documentation and inspect it with the appropriate explorer. | A different symbol, token contract, or native-versus-token form is a stop outcome. A duplicated ticker that cannot be resolved requires clarification. |
| Asset availability | The chosen asset and exchange direction are currently available rather than assumed from a general list. | Check the service’s current order interface immediately before creating the operation. The exchanger works with assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX and is gradually adding others, but this does not establish that every pair, network, or direction is available. | If the asset is generally listed but the required direction is absent, clarify or choose a genuinely supported route. Never substitute a different coin without creating and reviewing a new order. |
| Blockchain network | The sending network exactly matches the network selected for receiving. Treat the asset and network as one combined route, such as “asset on network,” not as separate assumptions. | Compare the explicit network name on the receiving instructions with the network selector in the sending wallet or platform. Use official network documentation if abbreviations differ. | If the names refer to different blockchains or token standards, stop. Sending an asset through an unsupported network may prevent automatic crediting and may lead to permanent loss. [5] |
| Destination ownership and purpose | The address was generated for this operation or supplied by the intended receiving wallet, account, or service. | Retrieve the destination from the receiving interface itself. Do not reconstruct it from transaction history, a search result, a social-media message, or an explorer entry for a service’s operational wallet. | An address obtained from a different source is a stop outcome until its ownership and purpose are confirmed. |
| Memo, Tag, or other identifier | Determine whether the selected asset and receiving service require an additional account identifier as well as the blockchain address. | Read the asset-specific deposit instructions in the receiving account. Confirm both the value and whether the field is mandatory; do not infer this from another service’s instructions. | A required identifier that is absent, altered, or placed in the wrong field is a stop outcome. Some custodial systems use a Memo or Tag to assign a shared address deposit to the correct account, so a valid on-chain transfer may still remain uncredited when the identifier is wrong. [6] |
| Amount rules | The amount to send follows the active order instructions and is expressed in the correct asset units. Account for whether the sending interface deducts a network fee from the entered amount or adds it separately. | Compare the exchange order with the final withdrawal preview. Use the order’s current terms rather than a screenshot or quote from an earlier session. | If the wallet preview produces a different on-chain amount, clarify before sending. Do not manually compensate for fees unless the interface and order instructions make the calculation unambiguous. |
| Quoted result and conditions | The expected amount to receive, calculation basis, applicable charges, and any time-sensitive conditions are visible and understood. | Use the current order summary and final confirmation screen. Ignore values copied from advertisements, old tabs, cached pages, or third-party rate comparisons. | An unexplained change requires clarification. If the displayed asset, direction, destination, or amount changes outside the accepted order mechanics, stop. |
| Operational and compliance requirements | The current requirements for the selected direction are known before the order is funded. | Read the conditions shown for that specific operation and use the service’s authenticated support channel if a requirement is unclear. Verification requirements may depend on the exchange direction and the results of compliance checks. | If required information or a review procedure is unexpected but appears within the authenticated process, clarify. Requests to evade checks, conceal transaction origin, or transfer funds to a private “agent” are a stop outcome. |
| Source freshness | Addresses, network instructions, and order values come from the active operation rather than an old message or saved template. | Regenerate or reopen the receiving details from the current account and compare the order identifier and timestamp context where displayed. | Outdated or conflicting instructions require clarification. An address that changed without an explained order refresh is a stop outcome. |
Pass Two: Recheck Immediately Before the Irreversible Action
Pass two begins after the transaction has been prepared in the wallet but before selecting Send, Confirm, Withdraw, Sign, or any equivalent final control. Do not rely on memory or assume that copied data remained unchanged.
| Check | What to verify | Independent confirmation | Meaning of a discrepancy |
|---|---|---|---|
| Asset in the wallet preview | The wallet is about to debit the exact cryptocurrency specified by the exchange order. | Place the wallet’s final preview beside the active order summary and compare the full asset name and symbol. | A different asset is an immediate stop. Return to the order rather than editing isolated fields until they appear plausible. |
| Final network | The network shown at confirmation is the one approved during pass one. Check again even if the wallet selected a default automatically. | Compare the final wallet preview with the receiving side’s explicit network label. | Any mismatch is a stop. A compatible-looking address does not override a network conflict. |
| Complete destination address | The entire pasted or scanned address matches the current address supplied for the operation. | Compare the beginning, middle, and end, preferably using a wallet or hardware-device display that shows the actual signing destination. Official Ethereum security guidance recommends checking the complete address rather than only a small prefix or suffix. [7] | One changed character is enough for a stop. Delete the prepared transaction and investigate the clipboard, QR source, device, and browser session. |
| Memo or Tag | The identifier is present only when required and matches exactly, including digits, letters, and case where the receiving instructions treat case as significant. | Compare the wallet field directly with the current receiving screen. Verify that a QR code included the identifier rather than assuming it did. | A missing, duplicated, truncated, or different identifier is a stop. |
| Amount sent | The blockchain amount leaving the wallet matches the order requirement after the interface’s fee treatment is understood. | Use the wallet’s final transaction preview and the exchange order, not the approximate fiat equivalent. | An unexplained difference requires clarification. A misplaced decimal point, wrong unit, or unintended full-balance transfer is a stop. |
| Network fee and total debit | The network fee and total wallet deduction are distinguishable from the amount intended for the recipient. | Review the wallet’s final debit breakdown. If the wallet does not present enough information to determine what the recipient will receive, pause. | If the fee changes the transferred amount in a way that conflicts with the order, clarify. An unfamiliar additional transfer or approval is a stop. |
| Expected amount to receive | The output asset and displayed result still correspond to the active order immediately before payment. | Refresh only through the authenticated interface and compare the current summary with the order already reviewed. | A permitted recalculation that is clearly explained may allow the review to continue. An unexplained asset or destination change is a stop; an unclear amount change requires clarification. |
| Order identifier and status | The payment is being made against the intended open order, not an expired, cancelled, completed, or duplicated one. | Compare the active order identifier with the confirmation page or official support record. | Do not fund an order whose status no longer accepts payment. This is a stop until the service confirms the correct procedure. |
| Last-second integrity check | No destination, amount, network, or signing instruction changed after the previous comparison. | Read the final confirmation on the signing device or wallet itself. Treat that display as the proposed transaction, even if the browser shows something else. | A last-second change is a stop and may indicate clipboard malware, a compromised interface, or an unintended wallet action. |
After completing both passes without unresolved discrepancies, a possible next step is to check the currently available exchange route and its conditions. Repeating the critical comparisons remains necessary if a new order is created or any field changes.
Decision Point: Continue, Clarify, or Stop
Continue checking
Use this outcome only when the domain, operation direction, asset, network, destination source, amount logic, and order status agree. It means the next check may begin; it does not mean the transaction is risk-free. Before approval, the second pass must still be completed against the actual wallet preview.
Clarify before sending
Pause when a field is incomplete rather than plainly wrong. Common examples include an unfamiliar network abbreviation, uncertainty over whether the fee is deducted from the transfer, an unexplained difference in the expected output, or unclear verification requirements. Resolve the question through the authenticated service interface or official support channel. If clarification changes the route, create or review the operation again from the beginning.
Stop the operation
Stop when the asset or network differs, the address fails the full comparison, a required Memo/Tag is missing, the domain is suspicious, the order no longer accepts payment, or someone requests a secret. Do not “try a small amount” through a route already known to be wrong. A test transfer demonstrates only that the tested route behaved in a particular way; it cannot make an unsupported network compatible.
Control Route Before, During, and After the Transfer
Before broadcasting
- Complete pass one using current receiving instructions.
- Prepare the transaction without approving it.
- Complete pass two from the wallet’s final preview.
- If considering a small test transfer, first confirm that the exchange order permits partial or multiple payments. Some order structures expect one specific payment, so an unapproved test may create a separate discrepancy rather than reduce risk.
- Approve only if there is no unresolved stop or clarification condition.
While waiting
- Record the transaction ID, or txid, once the wallet has broadcast the transaction.
- Open the explorer appropriate to the selected network and search for the txid. A blockchain explorer can show whether a transaction is pending, included in a block, successful, or failed; the exchange interface may require additional processing after the network records it. [8]
- Compare the explorer’s asset, destination, amount, and transaction status with the saved non-secret order details.
- Do not send a duplicate payment merely because the exchange status has not updated. First determine whether the original transaction is pending, confirmed, failed, or absent from the intended network.
- Ignore unsolicited “recovery support” messages. Return to the service through the verified domain.
After network confirmation
- Check whether the exchange order recognizes the incoming transaction.
- Keep the txid and order identifier available until the operation reaches its final displayed status.
- Confirm the output asset, credited amount, and receiving destination against the reviewed order.
- If the blockchain shows success but the service does not credit the transfer, collect diagnostic facts rather than attempting another transfer.
If the Status Is Delayed, the Amount Differs, or Data Changes
A delay does not by itself reveal the cause. The transaction may still be pending on-chain, may have been sent on another network, may lack sufficient confirmations for the receiving system, or may require an internal review. Diagnose the stage before contacting support.
When the status is delayed
- Search the txid in the explorer for the network actually selected by the sender.
- If the transaction is not found, verify whether the wallet broadcast it and whether the txid belongs to another network.
- If it is pending, do not create a replacement unless the sending wallet provides a documented replacement mechanism and the effect is understood.
- If it is confirmed, compare the destination, token or native asset, transferred amount, and Memo/Tag where applicable with the receiving instructions.
- Check the authenticated order page for a processing, review, or compliance status.
- Contact official support with the order identifier, txid, network, asset, and factual description of the discrepancy. Do not include a seed phrase or private key.
When the received or displayed amount differs
Separate three values: the amount debited from the sender, the amount recorded as transferred on-chain, and the amount credited or calculated by the service. A network fee may affect the wallet’s total debit without changing the recipient amount, or a sending platform may deduct a fee from the entered amount. The exchange calculation may also follow conditions shown in the order. Compare these values before treating the difference as a missing transfer.
If the on-chain amount does not match the order requirement, preserve the evidence and contact authenticated support. Do not send the difference automatically: an additional payment could be treated as a separate transaction or may arrive after the order conditions have changed.
When the address, network, or order data changes
Do not approve an edited transaction merely because most fields still match. Close the confirmation screen, preserve non-secret evidence of the change, verify the domain and device security, and regenerate the receiving instructions from the authenticated order. If a transaction was already broadcast, use its txid to establish exactly what reached the blockchain. Recovery cannot be promised; feasibility depends on the network, destination control, receiving system, and nature of the error.
Threats Directly Related to a Wrong-Route Transfer
Phishing
A phishing page can present a plausible order while replacing the deposit address or network instructions. Verify the full domain independently, avoid transaction links from unsolicited messages, and never enter a recovery phrase into a website. A familiar logo, valid-looking interface, or search-engine placement does not authenticate the recipient.
Clipboard and address substitution
Malware can replace a copied address before it is pasted, while address-poisoning attacks can place a lookalike address in wallet history. Compare the complete destination on the final signing display and obtain it from the active receiving screen rather than recent transaction history. [9]
Wrong network
A token may exist on multiple blockchains, but those versions are not interchangeable merely because they share a symbol. The sending and receiving sides must support the same route. Never select a cheaper or faster network unless the receiving instructions explicitly name it as available for that asset and operation.
Seed-phrase disclosure
A seed phrase or private key controls the wallet and is not needed to trace a public transaction, verify a txid, or credit an exchange order. If one has been exposed, stop using the affected workflow and follow the wallet provider’s official compromise procedure from a clean device. Do not send the phrase to support or store it with transaction records.
Guaranteed-return pressure
An exchange transfer should not be rushed because a third party promises guaranteed income, risk-free arbitrage, or automatic multiplication of funds. Such claims are unrelated to network compatibility and are a reason to stop the operation, not a reason to shorten the review.
Safe Transaction Record
Retain only the information needed to identify and diagnose the operation:
- exchange order identifier;
- transaction ID or txid;
- asset and blockchain network used;
- public sending and receiving addresses where needed for support;
- amount recorded on-chain;
- order and transaction status;
- relevant timestamps;
- screenshots of non-secret order terms or error messages, with unnecessary personal information removed.
Do not store a seed phrase, private key, wallet password, authentication code, full identity document, or unrelated personal data in the same record. The final practical rule is narrow: if the asset, network, destination, identifier, and amount cannot all be confirmed from current and independent sources, the transfer is not ready to be approved.