Before exchanging cryptocurrency, establish what the operation actually permits, what information may be requested and which details will become irreversible after confirmation. The aim is not to certify an exchange as risk-free. It is to detect contradictions early, separate routine compliance checks from suspicious requests and prevent avoidable errors involving limits, networks, addresses and amounts.

This pre-transaction review uses two passes. The first checks the context of the exchange before funds move. The second repeats the critical fields immediately before the irreversible action. No checklist can remove volatility, counterparty, technical or regulatory risk, but a deliberate pause can expose reasons not to proceed.

Express Check: Stop Signals Before You Create an Order

Do not proceed immediately if any of the following applies:

• The website address came from an unsolicited message, advertisement, unknown QR code or “support agent,” and you cannot independently confirm the correct domain.
• The asset, exchange direction or blockchain network shown in the order differs from the one supported by your sending wallet or receiving platform.
• The displayed minimum, maximum, fee, rate, required deposit or estimated amount to receive changes without an understandable explanation.
• You are being urged to act before a countdown expires, ignore a warning or transfer additional funds to “unlock,” “verify” or “protect” an earlier payment.
• Someone requests a seed phrase, private key, wallet backup, remote access to your device or a transaction signature unrelated to the stated exchange.
• The service requires identity or source-of-funds information, but the request arrives through an unverified channel or asks for information unrelated to the transaction.
• The recipient address changes after copying or pasting, or the address displayed by the wallet does not exactly match the order.
• The offer includes guaranteed profit, guaranteed recovery or a promise that cryptocurrency can be transferred without risk. Government consumer guidance treats guaranteed returns as a strong fraud warning. ^[1]

A stop signal does not always prove fraud. It means the current operation should not be funded until the inconsistency has been resolved through a trusted channel.

How to Read Exchange Limits and Verification Conditions

“The limit” may refer to several different restrictions. An order can be affected by the service’s minimum or maximum amount, the amount currently available for a particular direction, a wallet withdrawal limit, a blockchain fee requirement or a compliance threshold. These are not interchangeable. A value shown by the receiving service does not automatically confirm that the sending platform will permit the same amount.

Verification requirements can also differ by exchange direction and by the outcome of compliance screening. Virtual asset service providers may be required to perform customer due diligence, retain records and obtain information about transfer participants. National implementation varies, so a check that was not requested for one operation may still be requested for another. ^[2]

Before creating an order, determine whether the quoted limit applies to the amount you send, the amount the service receives after network costs or the amount expected at the destination. If the interface does not make that distinction clear, treat the limit as unresolved rather than estimating it.

The service supports USDT, BTC, ETH, DAI, LTC, BNB, XMR and TRX, with additional assets being introduced gradually. This does not mean that every pair, network or exchange direction is available. Check the current order interface before transferring funds. Ruble-to-crypto and crypto-to-ruble exchanges involving a bank card are planned rather than currently available and should not be treated as an active direction.

Two-Pass Pre-Transaction Verification Card

Pass One: Verify the Context Before Funds Move

Context and eligibility checks

What to verify	Where to obtain independent confirmation	What a discrepancy means
Domain and communication channel: confirm that the order page belongs to the intended service and that support messages originate from its published channels.	Use a previously saved address or independently locate the official domain. Compare it character by character and avoid relying on a link supplied in an unexpected message.	A misspelling, extra subdomain, unusual character or conflicting support contact is a reason to stop. Do not enter credentials or connect a wallet.
Exchange direction: identify the exact asset being sent and the exact asset expected in return.	Compare the order form with the asset labels and balances in both the sending wallet and the intended receiving wallet.	If the direction is reversed, unavailable or displayed differently across screens, do not assume it will be corrected after payment.
Asset identity: distinguish the native coin from a token with a similar ticker or name.	Use the official project documentation and, for tokens, the contract information published by the relevant project or trusted receiving platform.	A ticker match alone is insufficient. A different contract or asset can make the deposit unsupported or difficult to recover.
Blockchain network: confirm that the order, sending wallet and receiving destination all specify the same network.	Check the deposit instructions on the order and the network selector in the wallet or platform. Use official network documentation when terminology is unclear.	If one side names a different chain, token standard or network, stop. A valid-looking address does not prove network compatibility.
Memo, Tag, payment ID or similar identifier: determine whether the destination requires an additional routing field.	Read the receiving platform’s deposit instructions and the current order details rather than relying on an earlier transaction.	A missing or different identifier may prevent automatic crediting even when the destination address is correct.
Minimum and maximum amount: establish which quantity each limit measures.	Use the current order form and compare it with the sending platform’s withdrawal screen before submitting either transaction.	If the intended amount falls outside a stated range, or the basis of the limit is unclear, the order needs clarification before payment.
Rate, fees and expected receipt: identify whether the rate is fixed, floating or otherwise conditional, and which network or service costs affect the result.	Use the final order summary and the wallet’s own confirmation screen. Record the values displayed for this specific order rather than using a search result or old screenshot.	An unexplained change can indicate market movement, a revised fee, an expired quote or an altered order. Review the new terms instead of confirming automatically.
Quote validity and order status: check whether the order remains active and whether payment instructions are still current.	Refer to the live order page reached through the confirmed domain.	An expired, cancelled or replaced order must not be funded using old details. Create or obtain valid instructions first.
Verification requirements: determine what identity, transaction-origin or source-of-funds information may be requested for this direction.	Consult the service’s current rules through its verified interface and compare the request with the order status. Requirements can depend on compliance checks and applicable national rules.	An unexpected request needs clarification. A request for a seed phrase, private key or wallet backup is not a legitimate identity-verification step.
Jurisdictional availability: check whether the service and exchange direction are available where you are located.	Use current service terms and official information from the relevant national regulator when necessary.	If eligibility is unclear or conflicting, pause. Do not attempt to bypass location, identity, sanctions or other legal restrictions.
Source of technical data: distinguish order information from wallet data and blockchain data.	Use the confirmed order page for exchange terms, official wallet or project documentation for network behavior, and the correct blockchain explorer for public transaction status.	If different sources refer to different networks, transactions or order identifiers, they are not confirming the same event.

Pass Two: Repeat the Critical Fields Immediately Before Confirmation

Final confirmation-screen checks

What to verify	Where to obtain independent confirmation	What a discrepancy means
Recipient address: compare the complete address shown by the wallet with the current order instructions.	Read both displays directly. If a hardware wallet is used, treat its trusted screen as the final signing display and check more than a shortened beginning and ending.	Any changed character means stop. Clipboard malware can replace a copied crypto address with an attacker’s address. [3]
Network: verify the selected chain one final time after the address has been entered.	Compare the wallet’s network label with the order’s deposit network and the receiving platform’s instructions.	A mismatch means the address must not be used for the current transfer, even if the wallet allows confirmation.
Memo, Tag or payment ID: compare the complete value and confirm that it is entered in the correct field.	Use the active order or destination deposit page, not a value copied from transaction history.	A missing, truncated or outdated value requires correction before signing.
Amount to send: confirm the asset, decimal placement and whether the wallet subtracts its fee from the entered amount or charges it separately.	Compare the order requirement with the wallet’s final debit summary.	If the amount reaching the destination may be below the required minimum, do not submit it while assuming the service will accept it.
Total wallet debit: review the transfer amount plus any network cost displayed by the wallet.	Use the wallet’s final confirmation screen. On networks such as Ethereum, transactions require a network fee and include specific sender, recipient and value fields. [4]	An unexpected total may reflect a fee change, wrong asset, malicious contract interaction or altered transaction. Cancel and inspect the details.
Expected amount to receive: compare the final estimate with the latest active order summary.	Use the confirmed order page immediately before sending.	If the result no longer meets your requirements or differs without explanation, let the order expire or seek clarification rather than sending under assumed terms.
Transaction type and permissions: distinguish a simple transfer from a token approval, contract call or wallet-signature request.	Read the wallet’s action label and permission details. Official network documentation can clarify the difference between an asset transfer and smart-contract execution.	If the wallet requests broader spending permission or a different action than expected, reject it and recheck the workflow.
Order identifier and payment window: ensure that the address and amount belong to the same active order.	Compare the order identifier across the summary, status page and any verified service communication.	Mixed identifiers can mean that details from two orders have been combined. Do not send until one consistent record is established.

After completing both passes, a practical next step is to check the current exchange conditions for the intended direction.

Classify the Result Without Treating It as a Guarantee

Decision categories after verification

Outcome	When it applies	Appropriate action
Continue checking	The domain, direction, asset, network, limits, verification conditions and final transaction fields are internally consistent.	Proceed to the final wallet review, while accepting that market, counterparty and blockchain risks remain.
Clarification required	A condition is incomplete rather than directly contradictory: for example, the fee basis is unclear, a compliance review is pending or the expected amount has changed.	Pause the transaction and request clarification through a verified service channel. Recreate the order if its original terms are no longer active.
Stop	The domain cannot be confirmed; the network, address or Memo/Tag differs; secrets are requested; the transaction action is unexpected; or pressure and guaranteed-profit claims are involved.	Do not sign, send further funds or follow recovery instructions from the same unverified contact. Secure the wallet or device if compromise is suspected.

Control Route: Before, During and After the Exchange

Before the Operation

1. Open the confirmed service domain independently and create a new order for the intended direction.
2. Read the current limits and verification conditions instead of relying on a previous exchange.
3. Confirm asset and network compatibility at both ends.
4. Complete Pass One, then prepare the transfer without sharing wallet secrets.
5. Complete Pass Two on the wallet’s final confirmation screen.

For an unfamiliar destination or newly configured wallet, consider whether a smaller preliminary transfer is supported and economically sensible. It can help confirm routing, but it does not prove that a later transfer will avoid rate changes, compliance review, malware or service disruption.

While the Transaction Is Pending

Save the transaction hash and inspect it in the explorer for the network actually used. A submitted transaction may first remain pending and later be included in a block; the exchange may then wait for its own required confirmation status. Ethereum documentation, for example, distinguishes broadcast, block inclusion and later finality rather than treating them as one instant event. ^[4]

Compare four separate states rather than relying on a generic “processing” label:

• whether the wallet successfully broadcast the transaction;
• whether the correct explorer recognizes the transaction hash;
• whether the destination address and amount on-chain match the order;
• whether the exchange has detected and credited the deposit.

Do not send a duplicate payment merely because the status page has not updated. First determine whether the original transaction exists on-chain and whether it was confirmed.

After Confirmation

Confirm that the order status corresponds to the same order identifier and transaction hash. Check the actual amount received, the asset and the destination wallet. If the transaction completed correctly, disconnect unnecessary wallet sessions and retain only the non-secret records required for later support, accounting or compliance purposes.

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

A delay does not identify the cause by itself. Diagnose the stage at which the operation stopped before sending more funds or opening multiple conflicting requests.

1. Check the transaction hash on the correct explorer. No result can mean that the wallet did not broadcast the transaction, that the hash was copied incorrectly or that the wrong network explorer is being used.
2. Inspect the on-chain fields. Confirm the status, network, recipient address, transferred asset and amount. Do not share private keys or a seed phrase to obtain this information.
3. Compare the amount received by the deposit address. Account for the distinction between the wallet’s total debit, the on-chain transfer value and any network or withdrawal fee shown before sending.
4. Review the order state. Determine whether the order was active, expired, cancelled, awaiting confirmations or placed under compliance review when payment arrived.
5. Record the discrepancy precisely. Note which field changed and when: address, rate, expected receipt, verification requirement or status.
6. Contact support through the independently confirmed domain. Provide the order identifier, transaction hash, network, asset and relevant timestamps. Avoid sending secrets or unrelated identity documents.
7. Do not pay an unexpected recovery fee automatically. Independently confirm any request, especially if it arrives through direct messaging or claims that another transfer will guarantee release or reimbursement.

If the transaction was sent to an incorrect address, through an unsupported network or without a required Memo/Tag, recovery may be technically impossible or dependent on the recipient’s capabilities and policies. Blockchain transfers should therefore be treated as potentially irreversible; official Bitcoin safety guidance specifically recommends verifying the full receiving address before sending. ^[5]

Threats Directly Relevant to an Exchange Check

Phishing and Impersonated Support

A copied website can reproduce branding, order forms and live-chat language while collecting credentials or substituting a payment address. Open the service independently, verify the domain and distrust urgent instructions delivered through an unexpected message. Consumer protection guidance recommends contacting an organization through a website or channel already known to be genuine rather than using contact details supplied in a suspicious message. ^[6]

Address Substitution

Clipboard malware can replace a copied address during the paste operation. Compare the complete destination after pasting and again on the signing device. If the value changes, cancel the transaction, disconnect the affected device from sensitive accounts where practical and scan it for malware before attempting another transfer. ^[3]

Wrong Network

Two networks may use similarly formatted addresses without sharing the same ledger or deposit infrastructure. Select the network from explicit deposit instructions, not from address appearance. If the sender and receiver name different networks, the operation fails the check even when both accept the same asset ticker.

Seed Phrase or Private-Key Exposure

An exchange, explorer or legitimate support process does not need a seed phrase to locate a public transaction. Anyone who obtains a seed phrase or private key may control the corresponding assets. Official wallet guidance says these secrets must not be shared, including with someone claiming to represent support. ^[7]

If a seed phrase or private key has already been exposed, stop using the affected wallet for new deposits. Use a clean device and trusted wallet software to prepare a new wallet, then assess whether remaining assets can be moved without interacting with the suspected attacker. Do not accept unsolicited “recovery” assistance.

Guaranteed Returns or Guaranteed Recovery

An ordinary exchange changes one asset into another under stated conditions; it does not guarantee investment performance. Claims that an exchange will produce certain profits, remove all volatility or recover funds after another payment are unrelated to normal transaction processing and should be treated as fraud indicators. Crypto assets can experience substantial and unpredictable price movements. ^[1]

Safe Transaction Record Protocol

Keep a concise record that is sufficient to identify the operation without creating a new security or privacy risk:

• order identifier;
• transaction hash or txid;
• asset and blockchain network;
• public sending and receiving addresses where record-keeping requires them;
• amount sent and amount received;
• rate and fee information displayed for that order;
• order creation, broadcast and confirmation timestamps;
• non-sensitive screenshots of the order status and transaction confirmation, with unrelated personal information removed;
• support case identifier and a factual summary of any discrepancy.

Do not store seed phrases, private keys, wallet backup files, passwords, authentication codes or unnecessary identity documents with the transaction record. The usable endpoint of the review is a consistent set of current order terms, matching network and address data, and a non-secret audit trail—not a promise that every operational, compliance or market risk has disappeared.