A crypto exchange order can look straightforward while hiding several independent conditions: minimum and maximum amounts, the supported blockchain network, address formatting, compliance requirements, quote rules and the amount ultimately delivered. The safest moment to resolve ambiguity is before funds leave your wallet.

This pre-operation cross-check card uses two passes. The first establishes whether the exchange context makes sense. The second repeats the fields that matter most immediately before an irreversible action. It reduces avoidable errors, but it cannot eliminate market, operational, technical or compliance risk.

Express check: stop signals before you go any further

Pause before creating or funding an order if any of these points remains unresolved:

• The domain was opened from an unsolicited message, advertisement, search result or support chat and has not been independently verified.
• The required asset, exchange direction or blockchain network is not explicitly available in the current order interface.
• No clear minimum or maximum amount is shown, or your intended amount sits near a boundary whose treatment is unclear.
• The displayed receiving address changes unexpectedly after being copied, pasted or scanned.
• The sending wallet’s network and the receiving side’s network do not match exactly.
• A required Memo, Tag or payment identifier is missing, duplicated or different across screens.
• The final amount, exchange rate, fee treatment or quote conditions change without a clear explanation.
• Someone asks for a seed phrase, private key, wallet backup or remote access to your device.
• A representative offers guaranteed returns, “risk-free” profit or a secret way to bypass verification, sanctions or legal restrictions.

An Ethereum transaction sent to the wrong address cannot simply be reversed by a central operator. Other networks and custodial platforms may also provide no practical recovery path after an incorrect transfer, so confirmation screens should be treated as decision points rather than routine pop-ups. ^[1]

How to classify the result

Continue the cross-check when the information is present, consistent and independently confirmable. This means only that the audit can proceed—not that the operation is guaranteed to be safe or successful.

Clarification required when a limit, fee, network, verification condition, quote rule or recipient field is missing or ambiguous. Do not guess. Ask through a verified support channel before sending funds.

Stop when data conflicts across screens, the domain cannot be authenticated, the network is incompatible, the address changes unexpectedly, secret wallet credentials are requested or anyone proposes evading compliance controls.

Pre-Operation Cross-Check Card: pass one

The first pass checks the operating context. Complete it while there is still time to leave the process without broadcasting a transaction.

Pass one: context, availability and conditions

What to cross-check	Independent confirmation	What a discrepancy means
Domain and communication channel. Confirm the spelling, top-level domain and secure browser connection. Check whether the page came from a bookmark or a source you already trust rather than an unsolicited message.	Compare the address with a previously verified record. Open support from the known site interface instead of following a link sent by a stranger.	A misspelling, extra word, unusual subdomain or conflicting support contact is a stop signal consistent with phishing or impersonation.
Exchange direction and asset. Verify what you are sending and what you expect to receive. Do not treat similarly named assets or ticker symbols as interchangeable.	Compare the order interface with the asset labels in the sending wallet and receiving wallet. Check current availability before creating the order.	If the intended direction or asset is absent, do not substitute another option. The operation requires clarification or a different supported route.
Current service availability. The service works with assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR and TRX, while its asset range is expanding. That list does not establish that every pair, network or direction is currently offered.	Use the live order interface to confirm the exact asset pair and network at the time of the operation.	An asset being generally supported does not make a specific route available. If the route cannot be selected, stop that attempt rather than improvising.
Fiat route status. If the plan involves exchanging Russian rubles from a bank card into cryptocurrency or the reverse direction, confirm whether the feature is live.	Check the current order interface and published service conditions.	This card-to-crypto and crypto-to-card function is planned, not an established active feature. Do not create a substitute transfer on the assumption that it already works.
Blockchain network. Match the network named by the service with the network selected in the sending wallet. Check the full network name, not only the asset ticker.	Use the receiving instructions, the wallet’s network selector and, where necessary, the asset project’s official documentation. Confirm that the recipient supports that exact network.	A network mismatch can prevent the recipient from crediting the deposit and may lead to permanent loss. Do not send merely because an address format appears compatible. [2]
Minimum and maximum limits. Confirm the permitted input amount and whether limits apply per order, per period, by asset, by network or under compliance rules.	Read the values in the current order form and applicable conditions. If the interface and support information differ, request clarification before funding.	An amount below or above an applicable boundary may not be processed as expected. Never split an operation to avoid verification or other restrictions.
Rate and fee basis. Determine whether the quote is fixed or variable, what can cause recalculation, which fees are included and which network costs are paid separately.	Compare the order summary with the amount shown in the sending wallet. Review the quote terms presented for that specific order.	If the expected output cannot be reconstructed from the displayed terms, the operation is not ready. Ask for an explanation rather than estimating the result.
Verification conditions. Check whether identity, source-of-funds or other compliance information may be requested for this direction and amount.	Use the current service conditions and verified support. Requirements can depend on the operation and the result of compliance screening.	An unresolved request can delay or halt processing. Refusal to explain what category of information is required calls for clarification; a request for wallet secrets is a stop signal.
Recipient fields. Identify whether the destination requires only an address or also a Memo, Tag, payment ID or another routing value.	Read the receiving platform’s deposit screen and official documentation. The receiving side—not the sender’s assumptions—determines whether an extra identifier is required.	A missing or incorrect Memo or Tag can prevent automatic crediting or create a recovery case with no assured outcome. [3]
Information source and timestamp. Note where each critical condition came from and whether it belongs to the order currently on screen.	Compare the live interface, the order summary and verified support information. Refresh stale pages before relying on them.	A screenshot, old message or third-party post may describe expired conditions. Conflicting or undated information requires clarification.

Pre-Operation Cross-Check Card: pass two

Run the second pass immediately before clicking the wallet’s final Send, Confirm or Withdraw control. Do not rely on what was correct several minutes earlier: quotes can refresh, orders can expire and copied data can be replaced.

Pass two: final fields before an irreversible action

What to cross-check	Independent confirmation	What a discrepancy means
Destination address. Compare the entire address displayed by the wallet with the address in the active order. Checking only the first and last few characters is not enough when the stakes are significant.	Use two views where practical: the order page and the wallet confirmation screen. If a QR code was used, inspect the decoded address before approving.	Any changed, shortened, reformatted or unfamiliar address is a stop signal until its origin is established.
Memo, Tag or payment identifier. Recheck the exact characters and confirm that the value belongs to this order and recipient.	Compare the receiving instructions with the wallet’s final transaction preview.	A missing or conflicting identifier means the transaction is not ready. Do not place the value in a message field that the selected network does not recognize.
Asset and network. Confirm both again after entering the address. Some wallets change available networks when accounts or assets are switched.	Compare the wallet preview, order page and recipient’s network label. The labels must refer to the same blockchain route.	If the same asset appears on two different networks, that is not a close-enough match. Stop and select the supported route.
Amount being sent. Check the decimal point, asset denomination and whether the wallet has deducted or added the network fee.	Compare the order’s required input with the wallet’s actual transfer amount and available balance.	An amount changed by rounding, fee deduction or a denomination error may fall outside the order conditions. Clarify before sending.
Expected amount to receive. Recheck the current output and the conditions under which it may change.	Use the latest order summary rather than an earlier screenshot or estimate.	An unexplained change means the quote requires review. Volatility and changing network costs can affect conditions, but they do not justify approving figures you do not understand.
Order status and validity. Confirm that the order is still active and waiting for the transaction you are about to send.	Refresh the official order page carefully without opening a replacement order or funding details from a separate tab.	An expired, cancelled or already funded order must not receive another transfer unless verified support provides clear instructions.
Final wallet preview. Read the transaction as a new document: destination, network, asset, amount, fee and any extra field.	Compare each field with the active order one final time. Reject the request if the wallet displays an unexpected contract interaction, permission or destination.	A single unexplained difference is enough to stop. Confirmation creates consequences that a later checklist may not repair.

Once both passes are complete and unresolved discrepancies have been cleared, a practical next step is to check the current exchange conditions for your intended route.

Control route: before, during and after the exchange

Before sending

1. Close unsolicited chats and open the service through a verified route.
2. Create one order and record its non-secret identifier.
3. Complete pass one, resolving every limit, network and verification question.
4. Prepare the transfer, then complete pass two from the wallet’s final preview.
5. If the service and wallet permit it within their current minimums and fee conditions, consider whether a small test transfer is appropriate. A test can reveal some addressing errors, but it does not prove that a later transaction will be risk-free.

While waiting

Keep the order page available, but do not respond to direct messages claiming that an extra transfer is needed to “unlock” the exchange. Do not create a second order for the same payment unless verified support instructs you to do so.

After the wallet broadcasts the transaction, obtain the txid from the wallet and inspect it in the correct blockchain explorer. Compare the network, destination, transferred amount and confirmation status. A txid on one blockchain does not prove that a recipient supports or monitors that network.

After blockchain confirmation

Separate network confirmation from service completion. A confirmed transaction shows that the network processed the transfer; it does not by itself establish that every order condition, compliance review or recipient routing field was satisfied.

Check the order status and the received asset independently. Verify the asset itself, not only its displayed fiat value, because cryptocurrency prices can move while an operation is pending.

If the status is delayed, the amount differs or data changes

A delay is a diagnostic situation, not proof that funds are lost or that the exchange is complete. Work through the evidence in a fixed order:

1. Confirm broadcast. Check whether the wallet produced a txid. If there is no txid, the transfer may not have reached the network.
2. Open the correct explorer. Search the txid on the explorer for the network actually used. Verify status, destination, amount and confirmations.
3. Compare the network. Ensure that the explorer’s chain is the one specified by the active order.
4. Inspect the amount. Compare the on-chain transferred amount with the order input, accounting only for fee treatment explicitly shown by the wallet or service.
5. Check routing data. Determine whether a required Memo, Tag or payment identifier was transmitted correctly.
6. Review order changes. Record whether the quote expired, the order status changed or a compliance request appeared. Do not edit evidence or create overlapping orders.
7. Contact verified support. Provide the order identifier, txid, asset, network and a concise description of the discrepancy. Do not send a seed phrase, private key, password or unnecessary identity data.

If a wrong address, unsupported network or missing identifier is involved, recovery may be technically impossible or may depend on the recipient’s systems and cooperation. No outcome should be assumed in advance. Be cautious of third parties demanding an upfront crypto payment for guaranteed recovery; recovery offers are themselves a known fraud pattern. ^[4]

Threats that directly affect an exchange check

Phishing and fake support

A convincing interface does not prove that a domain is genuine. Phishing pages can copy branding, order forms and support language while replacing the deposit address. Unexpected messages that create urgency or redirect you to a new site should be treated as hostile until independently verified.

Do not let a person in a call or chat guide the transaction screen by screen. Pressure to act immediately removes the time needed for the two-pass check.

Address replacement

Clipboard-altering malware and manipulated QR codes can substitute a destination after you copy it. Compare the full address on the final wallet screen with the active order. If your wallet or device behaves unexpectedly, stop and investigate on a clean, trusted device rather than repeatedly pasting the address.

Wrong network

A token name is not a network specification. The sending and receiving sides must support the same asset on the same blockchain route. Official platform guidance warns that transfers over an unsupported or incorrect network can be unrecoverable. ^[2]

Seed phrase or private-key exposure

No exchange-status investigation requires the words that restore a self-custody wallet. Anyone with a seed phrase or private key may be able to control the corresponding accounts and move their assets. Wallet documentation explicitly warns users never to share these credentials, including with people claiming to be support staff. ^[5]

If a seed phrase has already been disclosed, do not continue the exchange from the potentially compromised wallet. Use the wallet provider’s official security guidance to assess the next steps without sharing the phrase again.

Guaranteed profit tied to an exchange

An exchange operation should not be confused with an investment promise. Claims that a transfer will produce guaranteed returns, double an amount or deliver profit without risk are fraud indicators. The US Federal Trade Commission warns that guaranteed crypto returns and pressure to send cryptocurrency are common scam tactics. ^[6]

Minimal transaction record: what to keep and what to exclude

Store only the operational evidence needed to identify the exchange and diagnose a discrepancy:

• order identifier;
• transaction ID or txid;
• asset and blockchain network;
• amount sent and amount received;
• order creation and transaction times;
• displayed status and relevant non-sensitive notices;
• screenshots of the order summary and transaction status, with unnecessary personal information redacted;
• support case identifier, if one was created.

Do not place a seed phrase, private key, wallet password, authentication code or full identity document in the transaction record. Avoid collecting extra personal details “just in case.” The useful record is compact: it should connect one order to one on-chain transaction without becoming a new source of account compromise.

The final decision rule is simple: if the domain, route, network, destination, amount, limits or verification conditions cannot be reconciled across reliable sources, do not broadcast the transaction. Preserve the non-secret evidence, seek clarification through a verified channel and restart the two-pass check only after the discrepancy has a concrete explanation.