A crypto exchange can fail before the transaction even reaches the blockchain. The wrong website, an unsupported network, a changed address, or a missing Memo can turn an ordinary transfer into a difficult recovery case.
The purpose of this pre-operation check is to catch those problems while you can still stop. It cannot eliminate market volatility, technical faults, compliance delays, fraud, or human error. Nor does a completed checklist guarantee that an exchange is safe. It gives you a controlled way to decide whether to continue checking, seek clarification, or stop.
Express Check: Stop Signals That Need an Immediate Pause
Do not confirm the exchange or broadcast a wallet transaction if any of these signals appears:
- The domain is unfamiliar or slightly misspelled. Close the page rather than navigating through it. Return using a previously verified bookmark or another independent record.
- The asset is correct but the network is uncertain. A ticker such as USDT does not identify the blockchain by itself. Tokens with the same symbol may operate on several protocols, while an exchange service may support only selected networks. Tether’s own protocol information tells integrators to state explicitly which protocols their platforms support. [1]
- The destination address changed after copying. Do not assume that matching first and last characters are enough. Address-poisoning attacks deliberately use visually similar addresses, so the middle characters also need attention. [2]
- A required Memo, Tag, payment ID, or similar identifier is missing. Pause until the receiving platform confirms whether that field is mandatory for this exact asset, network, and account.
- The final amount or exchange conditions differ from the order screen. A quote may update, but an unexplained difference must be resolved before payment.
- Someone asks for a seed phrase or private key. Stop communication. Anyone who controls a recovery phrase can control the wallet derived from it; legitimate transaction troubleshooting does not require disclosing it. [3]
- You are promised guaranteed returns, doubled funds, or a risk-free result. An exchange operation does not create guaranteed profit. The US Federal Trade Commission identifies guaranteed crypto returns and similar promises as scam signals. [4]
- You are being rushed by an unsolicited caller, direct message, or “support agent.” Do not use contact details or payment instructions supplied in the unexpected message.
If none of these signals appears, continue to the full card. “No obvious stop signal” means only that the detailed verification can proceed.
The Two-Pass Pre-Operation Verification Card
The card separates planning from execution. Pass One checks the context of the exchange before funds are prepared. Pass Two repeats the fields most likely to cause an irreversible mistake at the moment of confirmation.
Pass One: Verify the Operation Context
-
1. Website identity
What to verify: Check the complete domain in the browser address bar, including spelling and the top-level domain. Confirm that no extra words, substituted characters, unexpected subdomains, or unusual redirects have appeared.
Independent confirmation: Compare the address with a trusted bookmark or a domain record saved during an earlier verified visit. If support is needed, open its official channel from the verified website rather than from an advertisement, email, search result, or direct message.
What a discrepancy means: A minor spelling difference is not cosmetic. It may indicate phishing or impersonation. Stop and do not connect a wallet, sign anything, or enter account credentials.
-
2. Exchange direction
What to verify: Read the direction literally: which asset you are sending and which asset you expect to receive. Check that the “send” and “receive” fields have not been reversed.
Independent confirmation: Compare the order with the balances in your sending wallet and intended receiving wallet. Both wallets should support their respective assets and networks.
What a discrepancy means: If the order requires an asset you do not intend to send, or delivers an asset you cannot receive, do not create or fund it. Return to the direction selector and start the check again.
-
3. Asset and pair availability
What to verify: Confirm that the exact exchange direction is currently offered. The service works with assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX and is gradually expanding the list, but this does not mean every pair, network, or direction is available.
Independent confirmation: Use the current order interface and, where necessary, the service’s official support channel. Do not rely on an old screenshot, cached page, third-party list, or previous transaction.
What a discrepancy means: If the required pair or direction cannot be selected, treat it as unavailable until officially clarified. Do not substitute a similarly named token. Ruble-to-crypto bank-card exchanges and the reverse direction are planned rather than confirmed as operating functions, so they should not be assumed to be available.
-
4. Blockchain network
What to verify: Identify the network on the sending wallet, the exchange order, and the receiving wallet. All three must refer to the same supported route. Match the full network name, not merely the asset ticker or a familiar-looking address format.
Independent confirmation: Check the receiving platform’s current deposit instructions and the asset project’s official documentation. After a transaction is sent, use an explorer built for that specific blockchain rather than an explorer for a different network.
What a discrepancy means: If the sender and recipient use different networks, or the service does not explicitly list the required network, stop. Compatibility must be confirmed before a transaction is broadcast; address similarity does not prove network compatibility.
-
5. Current terms and compliance requirements
What to verify: Review the displayed amount, exchange rate or calculation method, service charges if shown, network-related deductions, minimum or maximum conditions, quote validity, and any verification requirements applicable to the direction.
Independent confirmation: Use the current order summary and official service information presented for that operation. Requirements can depend on the exchange direction and the outcome of compliance checks, so current conditions should be clarified before creating the order.
What a discrepancy means: A condition that is missing, unclear, or different from what you expected requires clarification. Do not infer terms from an earlier order or assume that another user’s experience applies to your transaction.
-
6. Source of every critical value
What to verify: Identify where the destination address, network, Memo or Tag, order amount, and expected output came from. Critical values should originate from the active order and the intended recipient—not from chat messages, screenshots, transaction history, or an unrelated browser tab.
Independent confirmation: Compare each value with the corresponding field in the verified service order, wallet, or receiving platform. If an address was supplied outside the order interface, obtain confirmation through an official channel reached independently.
What a discrepancy means: Conflicting sources create an unresolved payment instruction. Stop until one authoritative value is confirmed. Never choose the version that merely looks more familiar.
Pass Two: Repeat the Critical Fields Before the Irreversible Action
Run this pass after preparing the transfer but before clicking the wallet’s final Send, Confirm, or Sign control. Do not depend on what you checked several minutes earlier: order data can be reloaded, clipboard contents can change, and another tab can be mistaken for the active order.
-
1. Destination address
What to verify: Compare the address displayed by the sending wallet with the address in the active order. Inspect the entire address in manageable groups, including characters in the middle. Confirm it after pasting, not before.
Independent confirmation: Reopen or refresh the verified order through the same trusted session and compare it directly with the wallet’s confirmation screen. Do not copy an address from wallet history: address-poisoning scams are designed to exploit that shortcut. [2]
What a discrepancy means: Any changed, truncated, or unexplained character is a stop condition. Ethereum’s official support documentation notes that a transaction sent to the wrong wallet cannot be reversed by the network. [5]
-
2. Memo, Tag, payment ID, or destination identifier
What to verify: Determine whether the receiving side requires an additional identifier. If one is provided, compare it character by character and check that it is placed in the wallet’s correct field rather than appended to the address.
Independent confirmation: Use the deposit instructions for the exact asset, network, and destination account. A Memo or Tag used for one platform, account, or order must not be reused automatically.
What a discrepancy means: A missing or incorrect identifier may prevent the recipient from automatically crediting the transfer even if the blockchain transaction succeeds. Do not send until its necessity and value are clear.
-
3. Asset and network shown by the wallet
What to verify: Read the asset name, token contract details when relevant, and network shown on the wallet’s final confirmation screen. Make sure the selected balance is the intended asset rather than a similarly named or bridged token.
Independent confirmation: Compare the wallet screen with the order and the receiving platform’s current network instructions. For tokens, official project documentation and a network-specific explorer can help distinguish the intended token from unrelated assets using a similar symbol.
What a discrepancy means: A different network or token contract means you are preparing a different transaction from the one verified in Pass One. Cancel it and restart the network check.
-
4. Amount being sent
What to verify: Check the digits, decimal position, asset denomination, and whether the wallet is subtracting a network fee from the entered amount or adding it separately. Preserve enough native network currency to pay the required fee where applicable.
Independent confirmation: Compare the wallet’s final debit with the amount requested by the active order. Use the actual confirmation screen, not a mental conversion or an approximate fiat display.
What a discrepancy means: Sending too little may leave the order underfunded; sending too much exposes additional funds and does not imply that the excess will be returned. If the wallet’s debit differs from the intended amount, cancel and recalculate.
-
5. Expected amount to receive
What to verify: Recheck the latest order summary, including the output asset and the amount currently displayed. Distinguish between an estimate and a fixed value if the interface makes that distinction.
Independent confirmation: Compare the order summary with the receiving asset and address. The receiving wallet’s fiat estimate is not an independent confirmation of the exchange result because market-price sources and update times can differ.
What a discrepancy means: If the output changed beyond what the disclosed calculation or quote conditions explain, pause. Volatility and quote updates can affect an exchange, but an unexplained change should not be accepted by reflex.
-
6. Final signing request
What to verify: Make sure the wallet is asking you to send the intended asset to the verified address for the verified amount. Read the action being authorized; do not assume every wallet popup is a simple transfer.
Independent confirmation: Compare the signing window with the active order and the action you initiated. A legitimate wallet confirmation should provide enough transaction context to review. Unexpected or context-free prompts deserve suspicion. [6]
What a discrepancy means: An unfamiliar contract interaction, unlimited token approval, different recipient, or unexpected signature is not the verified exchange transfer. Reject the request and investigate from the beginning.
After completing both passes, one practical next step is to check the currently available exchange direction and its conditions. Availability on the order screen does not replace the final wallet-side verification.
How to Classify the Result
Continue the verification
This outcome applies when the verified domain, direction, asset, network, recipient details, amount, and current order terms agree, and no secret information or unrelated authorization has been requested.
It means you may move to the next control point. It is not a guarantee of safety, successful crediting, a fixed completion time, or protection from volatility.
Clarification required
Use this outcome when a network label is ambiguous, the Memo or Tag requirement is unclear, the available direction differs from an older record, the final amount changed without a clear explanation, or compliance requirements have not been established for the operation.
Do not fund the order while the question remains open. Reach official support from the verified service interface and keep the question limited to non-secret operational data. Support does not need your seed phrase or private key to identify a transaction.
Stop
Stop if the domain or recipient address differs, the networks are incompatible, the wallet displays an unexpected authorization, someone requests recovery words, or an unsolicited person pressures you to transfer crypto.
Also stop if the exchange is tied to a promise of guaranteed returns or “risk-free” profit. Those claims are incompatible with the volatility and operational risks of crypto assets and are recognized scam indicators by consumer regulators. [4]
The Control Route: Before, During, and After the Exchange
Before funding the order
- Complete both passes using the live order and the wallet that will actually send the funds.
- Remove distractions: close unrelated exchange tabs, messaging windows, copied addresses, and duplicate wallet popups.
- Record the non-secret order identifier and the displayed conditions needed to understand the transaction later.
- Confirm how the service communicates order updates and how official support is reached.
- Do not proceed merely because a timer, caller, or message creates urgency.
While waiting
- Use the order status page reached from the verified domain rather than a new link sent by message.
- After the wallet broadcasts the transaction, copy the txid from the wallet and inspect it using the correct network’s blockchain explorer.
- Check the transaction’s sender, recipient, asset or token contract where applicable, amount, network status, and confirmation count.
- Do not send a second payment solely because the order page has not updated. First determine whether the original transaction is pending, confirmed, failed, or absent from the intended blockchain.
- Ignore anyone offering paid “acceleration” or guaranteed recovery through an unsolicited message.
After blockchain confirmation
- Compare the confirmed on-chain recipient and amount with the verified order data.
- Check whether the service has recognized the deposit and whether the output transaction has been created.
- If an output txid is provided, inspect it on the appropriate explorer and verify the receiving address, asset, amount, and status.
- Confirm receipt in the destination wallet or platform itself. A service status such as “completed” is useful evidence, but the receiving account and blockchain record provide separate confirmation.
- Preserve only the operational record needed for support or accounting; do not archive wallet secrets with the order details.
If the Status Is Delayed, the Amount Differs, or Data Changes
A delay or mismatch is a diagnostic problem first. Sending more funds or following instructions from an unsolicited “recovery agent” can make it worse.
If the status is delayed
- Confirm that the sending wallet produced a txid.
- Open the correct network explorer and determine whether the transaction is absent, pending, failed, replaced, or confirmed.
- Verify that the explorer record shows the same destination address and amount as the order.
- Check the order’s current status through the verified domain.
- If the blockchain shows confirmation but the order remains unchanged, contact official support and provide the order ID and txid. Do not provide a seed phrase, private key, wallet password, or remote access to your device.
Network confirmation does not necessarily mean that a platform has completed its internal processing. Conversely, a wallet notification is not enough to prove that the transaction has confirmed on the intended blockchain.
If the amount does not match
- Separate the amount entered in the wallet, the total wallet debit, the network fee, the amount received by the deposit address, and the exchange output.
- Check the decimal places and asset denomination. A stablecoin amount, its fiat estimate, and the wallet’s total debit are different values.
- Compare the discrepancy with the conditions displayed when the order was created.
- Ask official support to explain any difference that cannot be reconciled from the order and on-chain record.
Do not assume that an overpayment will be refunded or that an underpayment will be processed automatically. The available response depends on the transaction, service rules, network, and compliance review.
If the address, network, or order data changed
If the change happened before broadcasting, cancel the prepared transaction and repeat both passes. Do not “correct” one field while leaving the rest unchecked.
If funds have already been sent, preserve the original order ID, txid, timestamps, and non-secret screenshots. Determine from the explorer where the transaction actually went. Contact the receiving service through its verified support route, but treat recovery as uncertain. Public blockchains generally do not provide a central authority that can reverse a confirmed transfer; Ethereum’s official guidance explicitly describes wrong-address transactions as irreversible. [5]
Be cautious of anyone who contacts you afterward and promises to recover the funds for an upfront payment. The FTC warns that unsolicited crypto recovery offers can be a second scam targeting people who have already experienced a loss. [7]
Threats Directly Relevant to an Exchange
Phishing and fake support
A phishing page may reproduce an exchange or wallet interface closely enough to collect credentials, alter payment details, or trigger a malicious signature. Inspect the address bar before entering information and again before payment.
Unexpected support messages deserve the same treatment. Open support through the verified website rather than using a phone number, username, QR code, or link supplied by the person contacting you.
Clipboard replacement and address poisoning
Malware can interfere with copied data, while address poisoning relies on lookalike addresses placed in transaction history. In both cases, the defence is the same at the critical moment: compare the address displayed by the wallet with the active order after pasting.
Checking only a few characters at the beginning and end is weak because lookalike addresses can preserve those visible fragments. Compare the middle as well, and avoid sourcing a destination from transaction history. [2]
Wrong network
The recipient address alone does not establish the correct route. Confirm the blockchain separately on the sender, order, and recipient. This is particularly relevant for assets that exist on multiple networks.
If the same ticker appears under several network choices, do not select the cheapest or fastest-looking option unless the exchange order and receiving platform explicitly support it.
Seed phrase exposure
A seed phrase is not an order number, verification code, or support credential. It controls access to the wallet accounts derived from it. Never paste it into an exchange page, support chat, diagnostic form, or screen-sharing session. MetaMask’s security guidance states that anyone with the recovery phrase can control the associated accounts. [3]
If a seed phrase may have been exposed, treat the wallet as compromised. Do not continue signing exchange transactions from it while seeking routine order support.
Guaranteed-profit claims
A normal asset exchange should not require belief in a guaranteed investment return. If someone directs you to exchange and send crypto as part of a scheme promising certain profit, multiplied funds, or no risk, stop before transferring anything. Regulators consistently identify such guarantees as a hallmark of crypto investment fraud. [4]
Minimal Record-Keeping Protocol
Keep enough non-secret information to reconstruct what happened without creating a new security or privacy risk:
- order or application identifier;
- date and approximate time of creation and payment;
- send asset, receive asset, and selected networks;
- amounts and conditions displayed for the order;
- deposit txid and, when available, output txid;
- non-secret screenshots of the order status and wallet confirmation;
- the official support ticket identifier if a case was opened.
Do not store a seed phrase, private key, wallet password, authentication code, full identity document, or unrelated personal information alongside this record. Share only the minimum operational data needed for a specific support request.
The final pre-operation rule is simple: if the verified order, receiving instructions, wallet confirmation, and blockchain network do not tell the same story, do not broadcast the transaction. Resolve the discrepancy first.