A crypto-to-crypto exchange involves more than choosing two assets and accepting a displayed rate. Before sending funds, you need to confirm that the website is genuine, the exact asset and network are supported, the deposit details have not changed, and the expected result still matches the order. A second check immediately before approval helps catch clipboard replacement, an expired quote, a missing Memo or Tag, and other discrepancies that may appear after the order is prepared.

This pre-transaction audit is designed to help identify reasons to pause or stop. It cannot eliminate volatility, technical failures, compliance reviews, third-party wallet errors, or the consequences of an incorrectly authorized blockchain transfer. Some crypto transactions cannot be unilaterally reversed after they are confirmed, so prevention is more reliable than assuming that an error can be corrected later. ^[1]

Express Check: Stop Signals Before You Create an Order

Run this compact check before reviewing rates or entering a wallet address. If any red signal appears, do not proceed merely because the offer is time-limited or the interface displays a countdown.

Critical stop-signal screening

Signal	Immediate response	Why it matters
The website was opened from an unsolicited message, advertisement, support chat, or shortened link.	Close the page and independently navigate to the service using a previously verified source.	Phishing pages can imitate an exchange interface and substitute their own deposit address. Checking the complete domain is a basic defense against lookalike sites. [2]
The selected asset or blockchain network is unclear, unavailable, or described differently by the sending wallet and the exchange order.	Stop until both sides identify the same asset and network.	A familiar ticker does not prove network compatibility. Tokens with the same name may exist on several blockchains and use different deposit routes.
The deposit address changes unexpectedly after copying, pasting, scanning a QR code, or switching devices.	Do not send. Reopen the order through the verified domain and compare the complete address again.	Malware, a compromised page, or an unintended order refresh may replace the destination.
The interface, a “support agent,” or any other person requests a seed phrase or private key.	Leave the page and do not disclose anything.	A seed phrase or private key can provide control over wallet assets. Legitimate transaction troubleshooting does not require handing these secrets to another person. [3]
The offer includes guaranteed returns, risk-free profit, fund multiplication, or a demand to send crypto to “unlock” earnings.	Stop and treat the proposal as a likely scam rather than an exchange operation.	Regulators warn that guaranteed crypto profits and unusually large promised returns are characteristic scam signals. [4]
The amount, destination, network, Memo or Tag requirement, or expected payout cannot be confirmed before sending.	Do not authorize the transfer.	A critical field that cannot be independently checked is an unresolved transaction risk, not a minor interface inconvenience.

Two-Pass Pre-Transaction Verification Card

The first pass validates the context in which the exchange will occur. The second pass repeats the critical fields immediately before the irreversible action: sending from a wallet or approving a withdrawal from another platform. Information should be checked on your own screens and in independent sources; do not send real addresses, credentials, personal data, private keys, or seed phrases to an article, public chat, or unknown support account.

Pass One: Validate the Operation Context

Pass one — order context and independent confirmation

What to verify	Where to obtain independent confirmation	What a discrepancy means
Website identity: the complete domain, spelling, connection state, and absence of unexpected redirects.	Use a trusted bookmark, previously verified service communication, or a direct navigation method that does not depend on an unsolicited link. Compare the whole domain rather than only the logo or page design.	A different character, extra word, unfamiliar subdomain, redirect, or certificate warning is a reason to stop. Visual similarity does not establish authenticity.
Exchange direction: which asset you are sending and which asset you expect to receive.	Compare the order summary with the balances and asset labels in the sending and receiving wallets.	Reversed “send” and “receive” fields can produce an unusable order or a materially different transaction. Correct the direction before continuing.
Current asset availability: both assets are supported for the intended operation.	Check the live order interface rather than relying on an old article, screenshot, message, or previous exchange.	The service works with assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX and may add more over time, but this does not mean every possible pair, network, or direction is currently available. An absent option requires clarification or a different supported route.
Blockchain network: the network selected by the sender exactly matches the network accepted for the order deposit.	Compare the network name in the sending wallet or withdrawal platform with the network explicitly shown in the exchange order. If a token contract is relevant, consult the project’s official documentation and a suitable block explorer.	Different network labels are a stop condition. Do not infer compatibility from a matching ticker, similar address format, or the fact that both interfaces display the same asset name.
Receiving wallet support: the destination wallet can receive the output asset on the specified network.	Use the wallet provider’s official documentation and the wallet’s own receive screen. Confirm that the displayed receiving account belongs to the intended wallet.	If the wallet does not expose or document the selected network, the destination may not recognize or display the transfer. Resolve the uncertainty before creating the order.
Memo, Tag, payment ID, or similar field: whether the sending or receiving side requires an additional identifier.	Read the current deposit instructions generated by the receiving service or wallet. The receiving platform, not a generic guide, determines whether the field is required.	A required identifier that is missing or incorrect may prevent automatic crediting, delay investigation, or put funds at risk. Some custodial platforms use a shared address and rely on an additional identifier to assign the deposit. [5]
Amount rules: the intended amount is accepted and leaves enough of the network’s native asset to cover the sender-side fee.	Check the current order conditions and the sending wallet’s own fee estimate before submission.	An amount outside the displayed conditions, or an insufficient fee balance, may prevent broadcasting or cause the received deposit to differ from the order expectation. Do not invent or assume a minimum, maximum, or fee.
Rate type and expected output: whether the displayed result is fixed for a stated condition or may be recalculated, and what can affect the final amount.	Read the order summary and current terms presented before creation. Record the displayed input and expected output without treating an estimate as a guaranteed settlement amount.	If the rate type, fee treatment, or recalculation conditions are unclear, clarification is needed. Crypto values can change rapidly, so delay and volatility may affect an exchange when the applicable terms allow recalculation. [6]
Order validity: whether the quote or deposit instruction has an expiry condition.	Use only the current order page. Compare any visible validity indicator with the time on the device used to submit the transaction.	An expired or ambiguous order should not receive funds. Create or request current instructions instead of reusing an old deposit address or order page.
Verification and compliance conditions: what checks may apply to this direction.	Review the current conditions before creating the order and use the service’s verified support route if a requirement is unclear.	Requirements may depend on the exchange direction and the results of compliance checks. An unresolved request or unsupported jurisdictional situation means the operation needs clarification; it is not a reason to conceal information or attempt to bypass controls.
Source quality: critical technical details come from current first-party materials.	Prefer official project documentation, the receiving platform’s deposit instructions, the wallet provider’s documentation, and the relevant blockchain explorer.	Conflicting information from old posts, search snippets, social media accounts, or screenshots means the data is not sufficiently verified.

Pass Two: Recheck Immediately Before Sending

Pause after the transaction has been prepared but before pressing the wallet’s final confirmation button. Compare what the wallet is about to broadcast with the live order details. Do not rely solely on what was correct several minutes earlier.

Pass two — final authorization fields

What to verify	Where to obtain independent confirmation	What a discrepancy means
Complete deposit address: every character shown in the sending wallet matches the current order.	Compare the wallet confirmation screen with the order page on a trusted device. Check the full address, not only the first and last characters. Ethereum’s official anti-phishing guidance likewise recommends verifying the entire address before signing. [2]	Any differing character means stop. Delete the prepared transaction and investigate whether the address was copied incorrectly, replaced, or regenerated.
Memo, Tag, or payment identifier: the final transaction includes the exact value required by the receiving side.	Compare the additional field character by character with the live deposit instruction.	A missing, truncated, or different value requires correction before sending. Never substitute an identifier from an earlier order.
Asset and network: the wallet’s final screen still shows the intended coin or token and the agreed blockchain.	Compare the wallet confirmation with the current order summary and the receiving wallet’s documented network support.	A mismatch is a stop condition even when the address appears syntactically valid.
Transfer amount: the entered amount matches the order and the wallet has not switched between “send amount” and “total including fee.”	Compare the wallet’s final debit breakdown with the order input amount and the displayed network fee.	An unexplained difference needs correction. Confirm whether the fee is added to or deducted from the entered amount before authorization.
Expected amount to receive: the current order result remains acceptable and has not changed unexpectedly.	Refresh only through the verified order workflow and compare the current summary with the value recorded during pass one.	A changed rate, fee presentation, or payout amount means consent must be reconsidered. Do not proceed based on the earlier figure if the current transaction displays different terms.
Destination ownership: the output address is controlled by you or by the intended recipient.	Open the receiving wallet independently and use its receive function. Where practical, compare the address on a second trusted screen or hardware-wallet display.	An address supplied by an unexpected caller, direct message, “account manager,” or recovery agent is not independently verified.
Order status: the order is active and still instructs you to send the selected amount to the displayed address.	Use the live order page reached from the correct domain.	A cancelled, expired, completed, or changed order should not receive another transfer.
Final wallet prompt: no unexpected contract approval, unlimited token allowance, network switch, or unrelated signature has appeared.	Read the wallet’s confirmation prompt rather than approving by habit. Compare the requested action with the simple transfer you intended to make.	An unrelated signature or approval indicates that the action differs from the planned exchange deposit. Reject it and recheck the site and workflow.
Device and communication state: no remote-access session, screen sharing, unsolicited support conversation, or urgent instruction is influencing the action.	Verify that you initiated the operation independently and are using official support channels only if assistance is required.	Pressure to act immediately or to let another person control the device is a reason to stop and secure the environment.

After both passes are complete, one possible next step is to check the current exchange direction and conditions. Availability, network support, order requirements, and compliance conditions should be reviewed again in the live interface before funds are sent.

How to Classify the Result

The card produces a decision status, not a guarantee. Use the most cautious status triggered by any individual check.

Decision status after the two-pass check

Status	When it applies	Next action
Continue checking	The domain, direction, asset, network, destination, amount, additional identifiers, and current order terms agree across the relevant sources.	Proceed to the final wallet review without skipping pass two. This status means no discrepancy was identified; it does not mean the operation is risk-free.
Clarification required	A condition is incomplete or ambiguous, such as an unclear network label, variable expected output, uncertain Memo requirement, unsupported receiving wallet, or pending compliance question.	Pause the transaction. Resolve the specific issue through current official documentation or the verified support channel, then restart the affected checks.
Stop	The domain is suspicious; addresses differ; networks conflict; the order has expired; a seed phrase is requested; the recipient is unknown; or the offer depends on guaranteed profit, urgency, or a payment to unlock funds.	Do not send or sign. Close the session, preserve non-secret evidence if fraud is suspected, and secure the wallet or device when exposure may have occurred.

Control Route Before, During, and After the Exchange

Before the Transfer

• Open the exchange through a verified route and complete both verification passes.
• Confirm that the sending wallet and receiving wallet support the exact networks selected for the input and output assets.
• Leave enough of the relevant native asset for network fees where the wallet requires it.
• Record the order identifier and non-sensitive order summary before sending.
• Where the service and wallet conditions permit, consider whether a small test transfer is operationally appropriate. A test can reveal some address or Memo errors, but it adds fees, may interact with minimum amount rules, and does not prove that a later transfer is risk-free. Receiving platforms commonly recommend test sends when destination identifiers are involved. ^[5]

While the Transaction Is Pending

• Use the appropriate blockchain explorer to look up the transaction by txid and distinguish “not broadcast,” “pending,” and “confirmed on-chain.”
• Keep the order page open only on the verified domain. Do not create a duplicate order or resend the same amount simply because the status has not updated.
• Compare the on-chain destination and amount with the saved non-secret order data.
• Expect the exchange interface and the blockchain explorer to update at different times. A delay alone does not establish loss, completion, or wrongdoing.
• Ignore unsolicited direct messages offering to accelerate, validate, synchronize, or recover the transaction. Support should not require a seed phrase or private key.

After Network Confirmation

• Confirm that the deposit transaction has the level of network confirmation required by the current order rather than assuming that a broadcast transaction is final.
• Check whether the output transaction has been created and, if so, verify its txid on the correct blockchain explorer.
• Compare the asset, output network, receiving address, and credited amount with the final order record.
• Do not post addresses, balances, screenshots containing personal data, or the complete order history publicly. Public blockchain information can be combined with other data to reduce financial privacy. ^[7]

If the Status Is Delayed, the Amount Differs, or Details Change

Recovery is a diagnostic process, not a promise that funds can be returned. Avoid sending a second payment until the first transaction and order have been traced.

Diagnostic actions for common exchange discrepancies

Situation	Checks to perform	Information safe to provide to verified support
No txid appears in the sending wallet	Check whether the transaction was signed, whether the wallet is connected to the intended network, whether the fee balance was sufficient, and whether the wallet reports a local error.	Order identifier, asset, selected network, approximate submission time, and an error message with secrets and unnecessary personal data removed.
A txid exists but remains pending	Open the correct blockchain explorer, check whether the transaction is visible, and review its status and fee information. Do not rely only on a wallet notification.	Txid, order identifier, asset, and network. A txid is normally sufficient for support to inspect public on-chain data.
The blockchain shows confirmation but the order does not	Verify the destination address, network, transferred amount, Memo or Tag, and order validity. Confirm that the transaction was sent to the current order rather than an older one.	Order identifier, deposit txid, asset, network, and the non-secret Memo or Tag if the order required one.
The received amount differs from the earlier estimate	Compare the final order terms, rate type, actual input received, network deductions, and any documented recalculation conditions. Separate sender-side network fees from the amount processed by the exchange.	Order identifier, input and output txids, and screenshots of the relevant order summary with personal or security-sensitive data removed.
The address or other order detail changed before sending	Do not use either version until the reason is established. Check whether the order expired, the page reloaded, a new order was created, or the clipboard value was replaced.	Order identifier, time of the observed change, and redacted screenshots. Never include a seed phrase, private key, password, or authentication code.
Funds were sent using a different network or incorrect Memo	Record the actual network, destination, txid, and entered identifier. Contact the verified receiving service without making additional transfers. Whether assistance is technically possible depends on the specific network, address control, and platform policy.	Order identifier, txid, actual asset and network, destination address, and non-secret transaction identifier. Do not accept third-party guarantees of recovery.

Be cautious after any error becomes public. Fraudsters may impersonate support or promise recovery in return for an advance payment, wallet connection, seed phrase, or private key. The FTC warns that unsolicited crypto recovery offers can themselves be scams. ^[8]

Threats Directly Relevant to a Crypto Exchange

Phishing and Lookalike Domains

A phishing page can reproduce branding, order forms, and support widgets while changing the deposit destination. Verify the complete domain before entering transaction data, and repeat that check after redirects or login prompts. An unexpected message containing a convenient exchange link should be treated as untrusted until independently verified. Official Ethereum security guidance recommends checking for spelling differences and confirming the complete URL. ^[2]

Address Replacement

Clipboard malware and manipulated interfaces can replace an address between copying and wallet approval. Compare every character on the final confirmation screen with the current order. Checking only a few characters is inadequate because a deceptive address may be constructed to look similar at the beginning or end. If the wallet uses a hardware display, treat the address shown on that trusted display as the final signing reference.

Wrong Network

The asset ticker alone does not identify a blockchain route. The sending platform, exchange order, and receiving wallet must agree on the network. If one interface says only “USDT,” “ETH,” or another ticker without clearly identifying the route, pause for clarification rather than selecting the cheapest-looking withdrawal option.

Seed Phrase or Private-Key Exposure

No ordinary exchange deposit requires giving the exchange your wallet’s seed phrase or private key. Anyone who obtains those credentials may control the associated accounts. If either secret was entered into an untrusted page or disclosed to another person, stop the exchange and use the wallet provider’s official security guidance from a clean environment. Do not continue using the exposed wallet as though changing a website password resolves the compromise. ^[3]

Guaranteed-Profit Claims

Exchanging one asset for another does not create guaranteed income. Claims that a transfer will be multiplied, produce a fixed return, release a risk-free arbitrage profit, or unlock a larger balance are outside a normal exchange workflow. Volatility can change the market value of both the sent and received assets, and no checklist can remove that exposure. The FTC identifies promises of guaranteed returns and low-risk crypto profits as scam indicators. ^[4]

Final Non-Secret Record

Keep a concise transaction record until the order is resolved and any relevant reporting or accounting obligations have been addressed. Store only what is needed to trace the operation:

• order identifier;
• date and time of order creation and transfer submission;
• input and output assets;
• selected input and output networks;
• amount sent and amount received;
• deposit and payout txids when available;
• the final status shown by the service;
• non-sensitive support ticket identifier if assistance was requested;
• a copy of the applicable order summary or terms, redacted where necessary.

Do not store a seed phrase, private key, wallet password, one-time authentication code, identity document, or unrelated personal information in the transaction record. The decisive final check is simple: the full address, exact network, required Memo or Tag, transfer amount, expected result, and active order status must agree at the moment of authorization. If one critical field does not agree, the appropriate next step is clarification or stopping—not sending and hoping the discrepancy can be repaired afterward.