A cryptocurrency exchange requires a receiving address, an asset, a network, an amount, and sometimes a Memo or Tag. It does not require the secret that controls your wallet. A seed phrase can reconstruct the keys and accounts derived from it, while a private key authorizes actions for the corresponding account. Anyone who obtains either secret may be able to transfer the associated assets without your permission. ^[1]

This pre-operation check is designed to catch common mistakes and manipulation before an irreversible action. It cannot guarantee safety: compromised devices, deceptive interfaces, incorrect source information, compliance restrictions, and user error can still affect an operation.

Express Stop-Signal Check

Stop before creating an order or signing a transaction if any of these conditions applies:

• A website, support agent, chat participant, form, browser extension, or “verification tool” asks for your seed phrase, recovery phrase, private key, wallet backup, or a screenshot of any of them.
• You reached the exchange through an unexpected message, sponsored result, shortened address, pop-up, or link sent by a stranger.
• The pasted recipient address differs from the address shown in the exchange order.
• The wallet network does not exactly match the network specified for the deposit.
• A required Memo or Tag is missing, changed, or placed in the wrong field.
• The order details change after you have prepared the transaction.
• Someone pressures you to act immediately or promises guaranteed returns, risk-free profit, or multiplication of the funds sent.

A recovery phrase is effectively a master credential for the wallet, and a private key controls the relevant account. Legitimate exchange processing does not require either secret. Ethereum’s security guidance also warns against entering these credentials into websites or sharing them with supposed support representatives. ^[2]

Why an Exchange Does Not Need Your Wallet Secrets

Information	Purpose	May be shared for an exchange?
Public wallet address	Identifies the source or destination account	Yes, when required for the operation
Transaction ID or txid	Locates a broadcast transaction in the appropriate blockchain explorer	Yes, for status checks or support
Order identifier	Connects a support request to an exchange order	Yes, through the verified support channel
Memo or Tag	Routes a deposit to the correct account when the selected destination requires it	Yes, but only in the transaction field specified by the order
Seed phrase or wallet backup	Reconstructs keys and potentially all accounts derived from the wallet seed	Never
Private key	Signs transactions and controls the corresponding account	Never

A wallet normally signs the transaction locally and broadcasts the signed instruction. The exchange needs the resulting transfer, not the private key used to authorize it. For example, an Ethereum transaction includes the recipient, value, network-related parameters, and a signature generated with the sender’s private key; the private key itself is not included in the transaction. ^[3]

Two-Pass Pre-Operation Verification Card

Complete the first pass while reviewing the proposed operation. Complete the second pass immediately before pressing the wallet’s final confirmation button. Do not enter real addresses, seed phrases, keys, or personal information into an article, shared checklist, chat, or unverified form.

Pass One: Verify the Operation Context

What to verify	Independent confirmation	What a mismatch means
Official domain and session	Use a previously verified bookmark or independently locate the official service domain. Check the full domain spelling and the secure connection indicator, not only the page design.	A look-alike domain, unexpected redirect, or unexplained browser warning is a stop signal. Do not enter order information or connect a wallet.
Exchange direction	Read the “send” and “receive” fields on the order page and compare them with the balances and destination wallet you intend to use.	Reversed assets or an unexpected destination requires correction before an order is created.
Asset availability	Confirm the asset and direction on the current order interface. The service works with assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX, but that does not establish that every pair, network, or direction is currently available.	If the required combination is absent, do not substitute a similarly named token or choose another network merely because its address format appears compatible.
Exact network	Compare the network named in the exchange order with the network selected in the sending wallet and, where relevant, the token’s official documentation.	A network mismatch may send assets to a destination the recipient cannot credit or access. Availability of recovery, if any, depends on technical control of the destination and recipient policy.
Current conditions	Read the amount, displayed rate basis, fees, limits, estimated result, and order validity conditions on the current interface before creating the order.	Missing, unclear, or unexpectedly changed values require clarification. Do not rely on old screenshots, cached pages, advertisements, or third-party summaries.
Verification requirements	Check the requirements shown for the selected direction and use the verified support channel if they are unclear. Requirements can depend on the operation and compliance-check results.	If the requested process differs from the published order flow, pause. Never treat a request for a wallet secret as identity or compliance verification.
Source of instructions	Compare instructions from email or chat with the active order page reached through the verified domain.	Conflicting addresses, changed payment details, or pressure to move the conversation to another account are stop signals.

Pass Two: Recheck Immediately Before Confirmation

What to verify	Independent confirmation	What a mismatch means
Recipient address	Compare the full address in the wallet with the order address. Check more than the first and last characters when the interface allows it, and verify the address on the signing device if using a hardware wallet.	Any changed character means the destination is different. Cancel the transaction and investigate possible clipboard malware or page manipulation.
Network and asset	Read the network selected in the wallet again and compare the asset ticker, token contract where applicable, and network with the order.	A familiar ticker does not prove that the token or network is correct. Stop if any field differs.
Memo or Tag	If the order displays a Memo, Tag, payment identifier, or similar routing value, compare it character by character with the wallet field.	A missing or incorrect value may prevent automatic crediting even when the destination address is correct.
Amount being sent	Compare the wallet’s final amount with the order amount and account for any fee treatment explicitly displayed by the wallet or service.	An unexplained difference can cause underpayment, overpayment, or a result different from the order calculation. Pause and determine which interface deducts the network fee.
Expected amount received	Re-read the current order summary immediately before sending, including whether the displayed result is fixed, estimated, or subject to stated conditions.	If the result or calculation basis changed unexpectedly, do not assume the earlier figure still applies.
Wallet confirmation screen	Review the destination, amount, network fee, and any contract interaction shown by the wallet. Treat the wallet’s final screen as a separate source from the website.	Unexpected permissions, contract calls, unlimited approvals, or unreadable actions are reasons to reject the request and investigate.
No secret disclosure	Confirm that the process has required only public transaction data and any legitimately necessary order or compliance information.	A request for a seed phrase, private key, wallet backup, or remote access is an immediate stop signal, regardless of who claims to be asking.

After completing both passes, one possible next step is to check the current exchange conditions and available direction.

How to Classify the Result

Outcome	When it applies	Required action
Continue checking	The verified domain, direction, asset, network, address, amount, and any Memo or Tag agree across the relevant interfaces.	Complete the second pass at the final confirmation screen. This outcome is not a guarantee of safety.
Needs clarification	A fee treatment, expected amount, compliance requirement, confirmation status, or supported direction is unclear but no secret has been requested.	Pause and ask through the verified support channel. Preserve the order ID and non-secret evidence of the displayed conditions.
Stop	A secret is requested; the address or network differs; the domain appears suspicious; the order changes without explanation; or someone promises guaranteed profit and demands a transfer.	Do not sign, send, install software, share the screen, or continue the conversation through the supplied link.

Control Route Before, During, and After the Operation

Before Sending

1. Open the verified domain independently.
2. Check the available exchange direction and network.
3. Read the current conditions and any verification requirements.
4. Create the order and record its identifier without copying secret wallet data.
5. Complete both passes of the verification card.
6. If practical and supported by the order terms, consider whether a small initial transfer would help verify the route. This does not remove network fees or other risks.

While Waiting

• Keep the original order page or order identifier available.
• Use the txid in the explorer for the network actually used, rather than relying only on a wallet notification.
• Distinguish between “broadcast,” “pending,” “confirmed on-chain,” and “credited by the recipient.” These are different stages.
• Do not send a second payment merely because an unsolicited message claims the first transfer is stuck.
• Do not disclose a seed phrase or private key to “accelerate,” “synchronize,” “validate,” or “refund” a transaction.

After Confirmation

• Compare the confirmed on-chain destination and amount with the order.
• Check the final service status and the amount actually received.
• Save only the minimum non-secret records needed to identify the operation.
• Close unexpected support conversations and ignore later requests to “unlock” funds by making another transfer.

Once a blockchain state change has reached the relevant level of finality, it generally cannot be cancelled through a bank-style reversal. That makes verification before signing more reliable than attempting to repair an incorrect transfer afterward. ^[3]

Threats Directly Relevant to an Exchange

Phishing and Fake Support

A phishing page may reproduce the design of a wallet or exchange and then request a recovery phrase under the pretext of connecting, restoring, verifying, or resolving an error. The correct response is to close the page and independently reopen the official service. Do not use the suspicious page to “check” whether the phrase works.

Wallet screenshots are also unsafe evidence because they may expose a recovery phrase or private key and can be synchronized to cloud storage. ^[2]

Address Substitution

Clipboard malware can replace a copied public address with an attacker-controlled address. Always compare the address after pasting it and again on the final wallet or hardware-device screen. A mismatch indicates that the transaction must be cancelled, not manually “corrected” while the device remains potentially compromised. ^[4]

Wrong Network

Matching or similar-looking addresses do not prove network compatibility. The order must explicitly support the network selected in the wallet. If assets were already sent through the wrong network, do not disclose wallet secrets to anyone offering recovery. Collect the txid, network name, asset, address, and order ID, then contact the verified recipient or exchange support. Recovery may be technically impossible or unsupported.

Seed Phrase or Private-Key Exposure

If a seed phrase or private key has already been shared, photographed on an untrusted device, entered into a website, or sent through chat, treat the affected wallet as compromised. Stop using it for new deposits. On a clean device, use official wallet software or a trusted hardware wallet to create a new wallet with a new recovery phrase, then consider moving any remaining assets while you still control them. Do not reuse the exposed phrase, and do not expect changing an app password to invalidate the compromised blockchain keys. ^[2]

Guaranteed-Return Claims

An exchange transaction does not create guaranteed profit. A person who promises fixed or risk-free returns and instructs you to transfer crypto, reveal wallet secrets, or pay an additional “release” fee is presenting a major fraud signal. U.S. consumer-protection guidance specifically identifies guaranteed crypto returns and claims of little or no risk as scam indicators. ^[5]

Recovery Procedure for Delays, Differences, or Changed Data

If the status is delayed, the amount differs, or order details appear to have changed, use diagnosis rather than repeated transfers:

1. Stop additional payments. Do not send a duplicate transaction or a “verification deposit.”
2. Confirm the broadcast. Locate the transaction in the explorer for the network used and verify its status, destination, asset, and amount.
3. Check the network. Make sure the explorer and transaction belong to the network specified by the order.
4. Check routing data. Compare any required Memo or Tag with the confirmed transaction data.
5. Separate network status from service status. A confirmed transaction may still require recipient-side processing or review.
6. Compare the original conditions. Use a safely stored order summary or screenshot that contains no wallet secrets or unnecessary personal data.
7. Contact verified support. Provide the order ID, txid, network, asset, timestamps, and a precise description of the discrepancy.
8. Reject secret requests. Support can investigate public transaction data without your seed phrase or private key.

These steps help identify where the discrepancy occurred but do not promise a refund, reversal, credit, or recovery. The outcome depends on the blockchain transaction, the destination’s technical control, the order conditions, and applicable compliance requirements.

Minimal Safe Record Protocol

Retain only what is needed to reconstruct the non-secret history of the operation:

• order identifier;
• transaction ID or txid;
• asset and exact network;
• public sending and receiving addresses;
• amount sent and amount received;
• Memo or Tag, if the operation required one;
• relevant timestamps and final status;
• non-sensitive screenshots of the order conditions and confirmation.

Do not store a seed phrase, private key, wallet backup, authentication code, identity document, or unrelated personal information with the order record. A seed phrase and private key are not exchange details: they are credentials capable of transferring control of the wallet. If any exchange flow asks for them, the correct pre-operation decision is to stop.