A crypto exchange can fail before the first coin moves. A copied address may have changed, USDT may be selected on the wrong blockchain, a required Memo or Tag may be missing, or the quote may no longer match the amount shown in your wallet.
This pre-operation card is designed to catch those problems in two passes. The first checks the context of the exchange. The second repeats the critical fields immediately before you approve an action that may be irreversible. It reduces avoidable mistakes, but it cannot eliminate technical, compliance, market or counterparty risk.
Express check: stop signals that need attention now
Pause before creating or funding an exchange request if any of these signals appears:
- The website domain differs from the address you intended to visit, contains an unexpected word or character, or was opened through an unsolicited message.
- The selected asset, exchange direction or network is not explicitly available in the current interface.
- The sending wallet and receiving side display different blockchain networks.
- The address changes after you paste it or does not match the address on the final wallet confirmation screen.
- A Memo, Tag or other destination identifier is displayed on one side but missing on the other.
- The amount to send, quoted result, fee information or final amount to receive changes without a clear explanation.
- Someone asks for a seed phrase, private key, wallet backup or remote access to your device.
- A message promises guaranteed profit, risk-free returns or the recovery of funds in exchange for another payment.
Official Ethereum security guidance warns that phishing pages may imitate legitimate websites and ask visitors to reveal a recovery phrase or send assets. It also recommends checking the destination address exactly before approving a transaction, since an Ethereum transfer cannot normally be reversed by the network. [1]
How to read the two-pass card
Each checkpoint contains three elements: what to compare, where to obtain independent confirmation, and what a mismatch means. Independent confirmation should come from your own wallet, the current exchange request, official project documentation, or a blockchain explorer for the selected network—not from a screenshot sent by an unknown person.
Classify the result without treating any category as a safety guarantee:
- Continue checking: the visible values agree, the source is credible, and no unexplained field is missing.
- Clarification required: a condition is incomplete, unfamiliar or temporarily unavailable. Do not fund the request until it is resolved through the service’s designated channel.
- Stop: the domain, network, address, asset or required identifier conflicts with the intended operation, or anyone requests wallet secrets.
Pass one: verify the exchange context
1. Domain and session
What to compare: the domain in the browser, the page opened for the exchange and the details shown after any redirect. Look for substituted characters, additional words and unexpected subdomains.
Independent confirmation: use a previously verified bookmark or type the known domain yourself. Compare it with the address displayed by the browser rather than relying on a logo, search advertisement or link preview.
A mismatch means: stop. Do not connect a wallet, enter account credentials or send funds. A convincing design does not prove that the page belongs to the intended service.
2. Exchange direction and current availability
What to compare: the asset you will send, the asset you expect to receive and the direction between them. Confirm that the exact direction is available now.
Independent confirmation: check the live exchange form before preparing the wallet transaction. The service supports USDT, BTC, ETH, DAI, LTC, BNB, XMR and TRX and is gradually adding assets, but that does not mean every possible pair, network or direction is active.
A mismatch means: clarification is required. Do not substitute a similarly named asset or choose another network merely to make the form proceed. Ruble-to-crypto and crypto-to-ruble operations involving bank cards are planned rather than currently available, so they should not be treated as an active route.
3. Asset identity
What to compare: the full asset name, ticker and, for tokens, the selected blockchain. This is particularly important for USDT because it exists on multiple protocols; the ticker alone does not identify the transfer network. Tether’s official protocol page lists USD₮ implementations on several blockchains and advises platforms to make their supported protocols explicit. [2]
Independent confirmation: compare the exchange form with the withdrawal screen in your wallet or sending platform. If a token contract is relevant, use the project’s official documentation and a compatible blockchain explorer rather than an address supplied in a chat message.
A mismatch means: stop. An asset with the same ticker on a different blockchain is not automatically compatible with the deposit route.
4. Blockchain network
What to compare: the network selected for sending with the network attached to the receiving address. Match the explicit network name, not just the appearance of the address.
Independent confirmation: check both the current exchange request and your wallet’s send screen. If either side does not state the network clearly, consult the official documentation for the asset and ask the service to clarify the route before creating or funding the request.
A mismatch means: stop. Do not assume that an address accepted by a wallet is correct for the exchange request. Wallet validation may detect malformed text, but it does not establish that you chose the intended recipient, token or deposit network.
5. Amount, quote and conditions
What to compare: the amount you plan to send, any displayed network or service charges, the quoted exchange rate, the expected amount to receive and any stated minimum or maximum applicable to that request.
Independent confirmation: use the current request summary and the final amount displayed by your wallet. Recalculate the basic relationship between the sending amount, disclosed charges and estimated result. Do not rely on an old screenshot or a quote from a previous request.
A mismatch means: clarification is required if the cause is not explicitly shown. Crypto prices and exchange conditions can change, so a revised result is not automatically evidence of fraud; an unexplained revision, however, should not be approved.
6. Compliance requirements
What to compare: the current requirements for the chosen direction, including any information or verification requested before or during processing.
Independent confirmation: read the conditions shown for the specific request and use the service’s designated support channel if something is unclear. Requirements can depend on the exchange direction and the outcome of compliance checks. Applicable obligations may also differ between countries.
A mismatch means: clarification is required. Do not follow third-party instructions for bypassing verification, sanctions controls, service restrictions or applicable law.
7. Source of the receiving details
What to compare: where the receiving address, Memo, Tag or payment identifier came from and whether those details belong to the current request.
Independent confirmation: obtain them directly from the active exchange request. Refreshing the page, opening another request or switching assets may produce different details, so do not reuse fields from an earlier operation unless the service explicitly confirms that they remain valid.
A mismatch means: stop. Never replace an address with one supplied by a person claiming to be an administrator, broker, recovery agent or support representative.
Pass two: repeat critical fields before sending
Start this pass only when the wallet is ready to display its final confirmation screen. Do not rely on memory, and do not approve the transaction while another person is pressuring you to hurry.
1. Destination address
What to compare: the complete address in the exchange request, the wallet recipient field and the final signing screen. Check more than the first and last few characters.
Independent confirmation: compare the values directly on screen. If you copied the address, verify it after pasting because clipboard-altering malware can replace crypto addresses.
A mismatch means: stop and delete the prepared transaction. Recopy the address from the active request. If it changes again, secure the device and wallet before continuing.
2. Memo, Tag or additional identifier
What to compare: whether the request requires an additional destination field and whether the exact value appears in the correct wallet field.
Independent confirmation: use the instructions attached to the current request and your wallet’s final transaction summary. Only include such a value when the route explicitly requires it.
A mismatch means: stop. A valid blockchain address does not compensate for a missing or incorrect identifier when the receiving system uses that field to attribute a deposit.
3. Network and asset
What to compare: asset, token standard where relevant, and blockchain network one final time.
Independent confirmation: keep the exchange summary and wallet confirmation visible together. For USDT, do not reduce this check to “USDT on both sides”; confirm the specific supported protocol. [2]
A mismatch means: stop even if the address format looks plausible or the wallet allows the transaction to be signed.
4. Sending amount and expected result
What to compare: the exact amount leaving your wallet, the amount required by the request, the displayed network fee and the latest estimate of what you will receive.
Independent confirmation: use the wallet confirmation screen and the still-active request summary. Check whether your wallet subtracts the network fee from the entered amount or adds it separately.
A mismatch means: clarification is required. Cancel the prepared transaction if the deposited amount would differ from the request and the service has not explained how that difference will be handled.
5. Freshness of the request
What to compare: whether the request remains active and whether its address, quote, amount or conditions have changed since pass one.
Independent confirmation: reopen or refresh only through the verified domain, then compare the current summary with the values already prepared in your wallet.
A mismatch means: do not send using mixed data from two versions of the request. Rebuild the transaction from the latest confirmed details or request clarification.
6. Final wallet action
What to compare: the recipient, asset, network and amount presented by the wallet at the moment of approval.
Independent confirmation: trust the wallet’s own signing display over text copied into a message or document. A legitimate exchange does not need your seed phrase or private key to receive an ordinary blockchain transfer. Ethereum’s official security guidance describes a recovery phrase as the master key to a wallet and states that legitimate services should not request it. [1]
A mismatch means: reject the transaction. If the wallet asks you to sign an unexpected contract interaction rather than the transfer you intended, do not proceed until you understand exactly what is being authorized.
After completing both passes, one possible next step is to check the currently available exchange conditions. Availability and requirements should still be reviewed for the exact asset, network and direction before a request is funded.
Control route: before, during and after the exchange
Before sending
- Close unsolicited messages and open the verified domain independently.
- Complete pass one before copying any payment details.
- Prepare the wallet transaction without approving it.
- Complete pass two against the final signing screen.
- Save the request identifier and the non-secret request summary.
While the transaction is pending
After broadcasting, record the txid produced by the wallet. Use the appropriate blockchain explorer to check whether the transaction exists, whether it is pending or confirmed, and whether the destination and amount match what you sent. Ethereum’s documentation notes that explorers can display the transaction hash, status, block, sender, recipient, transferred tokens, value and fee. [3]
For Bitcoin, a txid is also used to identify and track a transaction, while confirmed transfers become part of the blockchain’s public record. [4] For any supported asset, make sure the explorer corresponds to the blockchain actually used. Do not interpret activity on a different network as confirmation of the intended deposit.
A blockchain confirmation and a completed exchange status are separate events. The first shows what happened on-chain; the second reflects how the service has processed the request.
After confirmation
Compare the final credited asset and amount with the completed request summary. Verify the receiving transaction in the relevant wallet or explorer where the network makes that information publicly visible. Do not delete your request identifier or txid until the result has been reconciled.
If the status is delayed, the amount differs or details change
A delay does not reveal its cause by itself. Diagnose the operation in a fixed order rather than sending another payment immediately.
- Confirm broadcast: check whether your wallet created a txid. No txid may mean the transaction was never broadcast or is still held locally.
- Check the correct network: search using an explorer for the blockchain selected in the request.
- Read the on-chain status: determine whether the transaction is pending, failed or confirmed. Ethereum transactions, for example, receive a transaction hash when submitted and must be included in a validated block before they are considered successful. [5]
- Compare destination and value: verify the actual on-chain recipient and transferred amount against the saved request summary.
- Check additional fields: review any Memo, Tag or identifier recorded by the wallet or sending platform.
- Compare timestamps and request status: establish whether funds were sent while the request was active and whether its conditions changed before broadcast.
- Contact the designated support channel: provide the request identifier, txid, asset, network and a concise description of the discrepancy. Do not send a seed phrase, private key, password or unnecessary personal records.
Do not create a replacement transfer merely because the interface is slow to update. A second payment can produce a second valid blockchain transaction. Likewise, no diagnostic step guarantees that a mistaken transfer can be recovered.
Threats directly relevant to an exchange
Phishing and fake support
Phishing pages can copy branding, forms and wallet prompts. Verify the domain independently, especially after clicking a search result, advertisement, email or messenger link. Treat private messages from supposed support agents as unverified until the same instructions are confirmed through the service’s designated channel.
Clipboard address replacement
Malware can substitute another recipient after an address is copied. Compare the pasted address with the active request and then compare it again on the wallet’s final approval screen. If repeated copies produce different addresses, stop using the device for the transaction.
Wrong network
The network must agree at both ends. This check matters especially for tokens available on several blockchains, but it also applies whenever a wallet or sending platform offers multiple withdrawal routes. Never choose a network solely because its displayed fee is lower.
Seed phrase or private-key exposure
A seed phrase and private key authorize control of wallet funds; they are not deposit details. Never type them into an exchange page, support chat, diagnostic form or blockchain explorer. If either secret has been exposed, do not continue the exchange from the affected wallet until an appropriate wallet-security response has been completed.
Guaranteed-return claims
An exchange request should describe a conversion, not promise investment profit. Claims of guaranteed income, doubled deposits or risk-free returns are a reason to stop, particularly when they require sending crypto to an address supplied through social media or private chat. Official Ethereum security material identifies giveaway and investment-style promises as common scam patterns. [1]
Minimal record protocol
Keep only the information needed to identify and reconcile the operation:
- request identifier;
- date and time of creation and broadcast;
- asset and blockchain network;
- exchange direction;
- amount sent and displayed amount to receive;
- public sending and receiving addresses when necessary for reconciliation;
- Memo or Tag only if it formed part of the public transaction details;
- txid for the outgoing transaction and, when available, the receiving transaction;
- non-sensitive copies of the request status and disclosed conditions.
Do not store seed phrases, private keys, wallet backup files, passwords, authentication codes or excessive identity documents alongside this record. The useful audit trail is the one that proves which public transaction and exchange request you are discussing without creating a new route into your wallet or exposing more personal information than necessary.
