Before exchanging one cryptocurrency for another, verify the operation twice: first when preparing the order, then again immediately before sending funds or approving an irreversible transaction. This process can expose a wrong network, altered address, misleading rate, missing Memo or Tag, or phishing page before assets leave your control. It cannot eliminate volatility, technical failure, compliance delays, fraud, or user error, so treat it as a decision aid rather than a guarantee of safety.
Express Check: Stop Signals Before You Create an Order
Run this short check before reviewing detailed conditions. If any stop signal appears, do not send funds while trying to resolve the issue at the same time.
| Check | Continue checking only if | Stop if |
|---|---|---|
| Website identity | You reached the service through a domain you independently verified, and the browser shows no unexpected redirects or certificate warnings. | The page came from an unsolicited message, advertisement, look-alike domain, shortened address, or support account that contacted you first. |
| Requested secret information | The order requires only information relevant to the exchange and any applicable compliance process. | Anyone requests a seed phrase, private key, wallet backup, remote device access, or a transfer supposedly needed to โverifyโ your wallet. A recovery phrase provides control over wallet assets and should never be disclosed. [1] |
| Asset and network | The sending wallet, exchange order, and receiving platform all identify the same asset and compatible blockchain network. | The asset symbol matches but the networks differ, or the destination does not clearly confirm support for the selected network. |
| Destination details | The deposit address and any required Memo, Tag, payment ID, or similar identifier come directly from the active order. | The address changed after copying, arrived through a separate chat, or cannot be reconciled with the order page. |
| Terms | The displayed send amount, expected receive amount, rate type, applicable fees, limits, and expiry conditions are understandable. | Material figures are hidden, contradictory, unexpectedly changed, or accompanied by pressure to send immediately. |
| Claims and pressure | The service describes an exchange rather than promising an investment outcome. | Someone promises guaranteed returns, risk-free profit, or extra gains for sending more. Regulators identify guaranteed high returns and little-or-no-risk claims as fraud warning signs. [2] |
A stop signal does not prove that every part of the operation is fraudulent. It means the available information is insufficient or inconsistent enough that sending crypto would be an unjustified risk.
Two-Pass Pre-Transaction Verification Card
The first pass validates the context of the exchange. The second repeats the fields that can cause an irreversible loss if they are wrong at the moment of transfer. Obtain confirmations from sources independent of copied messages: the official order interface, your wallet, the receiving platformโs deposit screen, official network documentation, and an appropriate blockchain explorer.
Pass One: Validate the Operation Context
| What to verify | Where to obtain independent confirmation | What a discrepancy means |
|---|---|---|
| Correct domain and session Confirm the domain character by character, the secure browser connection, and whether you opened the site from your own bookmark or another independently verified source. |
Compare the browser address with a previously saved trusted record. Open a fresh session rather than relying on a link in email, social media, search advertising, or direct messages. | A spelling variation, unexpected subdomain, redirect, certificate warning, or different order after reopening may indicate phishing or session manipulation. Stop and re-establish the service identity. |
| Exchange direction Verify which asset you will send and which asset you expect to receive. Read the direction as โsend asset โ receive asset,โ not merely as two adjacent tickers. |
Compare the order summary with the withdrawal screen in the sending wallet and the deposit screen for the receiving wallet. | Reversed assets or inconsistent labels may create an unusable order or cause funds to be sent to an incompatible destination. Do not infer the intended direction from the address format alone. |
| Current availability Confirm that the exact asset pair and required networks are available now. |
Use the live order interface and current service conditions. The exchanger supports assets including USDT, BTC, ETH, DAI, LTC, BNB, XMR, and TRX and is gradually adding more, but this does not mean every pair, network, or direction is available. | If the required combination is missing or marked unavailable, do not substitute a similarly named asset or another network without checking whether your receiving platform supports it. |
| Asset identity Check the full asset name, ticker, and, where relevant, token contract or other network-specific identifier. |
Use the official asset documentation and the receiving platformโs deposit information. For tokens, compare the contract shown by a reputable explorer with the identifier recognized by the destination. | Matching tickers do not necessarily establish that two tokens are the same asset. An identifier mismatch can indicate an unsupported or imitation token. |
| Blockchain network Confirm that the withdrawal network, order deposit network, and final receiving network are identical or explicitly compatible. |
Check all three interfaces separately. If a network name is abbreviated or branded differently, resolve the ambiguity through official documentation before continuing. | A network mismatch is a stop condition. A valid-looking address is not proof that the destination will credit a transfer made through that network. |
| Receiving address ownership Confirm that you control the destination wallet or that the address was generated by the intended receiving account. |
Obtain the address from the walletโs receive screen or the platformโs authenticated deposit page. If the wallet supports it, verify the address on the wallet device itself. | An address supplied only through chat, email, screenshots, or a third party lacks adequate confirmation. If ownership is unclear, stop. |
| Memo, Tag, payment ID, or equivalent Determine whether the destination requires an additional identifier as well as an address. |
Read the current deposit instructions displayed inside the authenticated receiving account and compare them with the exchange order. | A missing or incorrect identifier can prevent automatic allocation of the deposit even when the address is valid. Do not invent, reuse, or omit the value unless the destination explicitly says none is required. |
| Amount and available balance Verify the amount to send and whether the wallet balance also covers any network fee charged separately. |
Compare the order with the walletโs final transaction preview. Use the walletโs current network-fee calculation rather than an old estimate or screenshot. | If the wallet will send less than the order requires, deduct a fee from the transfer amount, or use a โsend allโ function unexpectedly, the exchanger may receive a different amount. Recalculate before proceeding. |
| Rate and expected output Identify whether the rate is fixed, floating, estimated, or recalculated under stated conditions. Record the expected receive amount shown for the current order. |
Use the active order summary and its published conditions. Distinguish the quoted exchange result from wallet withdrawal fees, blockchain fees, and any receiving-platform charges. | A result that differs from the earlier quote may reflect market movement, order expiry, fee treatment, or changed conditions. If the reason is not clear, seek clarification before sending. |
| Limits and order validity Check the permitted amount range, the orderโs validity window, and what happens if funds arrive late or in a different amount. |
Read the conditions attached to the specific direction and current order rather than relying on general promotional text. | An amount outside the displayed range or a transfer after expiry may require recalculation, review, or support intervention. Do not assume the original quote remains available. |
| Compliance conditions Check which verification requirements may apply to this direction before committing funds. |
Use the current order terms and official support channel. Requirements may depend on the operation, applicable rules, transaction data, and the outcome of compliance checks. | If the required information, review procedure, or possible restrictions are unacceptable or unclear, do not create or fund the order. Never attempt to bypass identity, sanctions, geographic, or legal controls. |
| Source freshness Confirm that every critical value belongs to the current order rather than an old tab, previous exchange, cached page, screenshot, or support conversation. |
Refresh the authenticated order status and compare its identifier with the order you intend to fund. | Mixed information from multiple orders can lead to an expired address, wrong amount, or incorrect destination details. Close unrelated tabs and restart the check. |
Pass Two: Recheck Immediately Before the Irreversible Action
Pause at the walletโs final confirmation screen. Do not approve the transfer while switching between messages, answering a caller, sharing your screen, or responding to urgency from โsupport.โ Cryptocurrency transfers such as confirmed Bitcoin and Ethereum transactions generally cannot be reversed by a central operator, so recovery may depend on the recipientโs cooperation or a serviceโs technical ability to assist. [3]
| What to verify | Where to obtain independent confirmation | What a discrepancy means |
|---|---|---|
| Order identity and status Confirm that the order identifier matches your record and that the order is still waiting for the specified deposit. |
Compare the active order page with the confirmation record created during Pass One. | A closed, expired, completed, or different order must not be funded without clarification. |
| Full destination address Compare the complete address, not only its first and last characters. |
Check the wallet confirmation screen against the current order page. If possible, use a second trusted device or the hardware wallet display for the comparison. | Any changed character is a stop condition. Malware and address-poisoning tactics can exploit partial comparisons; Bitcoin safety guidance specifically recommends checking the entire receiving address. [4] |
| Memo, Tag, or payment identifier Confirm both the value and the field in which it appears. |
Compare the final wallet preview with the order and destination deposit instructions. | A missing, truncated, reformatted, or different value requires cancellation of the pending transfer until the correct entry method is established. |
| Network selected by the wallet Verify the actual network through which the wallet will broadcast, not merely the asset ticker. |
Use the walletโs network indicator and compare it with the orderโs deposit network. | If the wallet has switched networks or the selected chain differs from the order, cancel the transaction. |
| Exact send amount Confirm the amount after decimal placement, โmaximum amountโ behavior, and any deduction made by the wallet. |
Compare the final wallet preview with the orderโs required deposit amount. | A difference can place the transfer outside the order terms or change the expected output. Do not assume the service will automatically interpret the difference as intended. |
| Network fee and total debit Distinguish the amount sent to the exchange address from the fee and the total removed from the wallet. |
Use the final transaction breakdown produced by the wallet. | If the fee changes the sent amount rather than being added separately, return to the amount field and correct the transaction. |
| Expected amount to receive Recheck the latest displayed estimate or fixed result and its conditions. |
Use the current order page immediately before broadcast. | A material or unexplained change means the economic terms are no longer the ones reviewed in Pass One. Pause rather than relying on an earlier screenshot. |
| Destination for the exchanged asset Confirm that the output address remains the wallet or account you intended to credit. |
Compare the order summary with the destination walletโs receive screen. | An altered output address suggests a different order, account mistake, or compromise. Do not send the deposit. |
| Final authorization context Confirm that you are signing a straightforward transfer with the intended wallet and account. |
Read the walletโs complete confirmation prompt, including asset, recipient, value, network, and any contract interaction it displays. | An unexpected token approval, unlimited spending permission, contract call, or request to connect another wallet is outside a normal transfer flow and requires separate investigation. |
After completing both passes without unresolved discrepancies, one possible next step is to review the currently available exchange conditions. Recheck the live pair, network, amount, and verification requirements before creating an order because availability and conditions can change.
Classify the Result Without Treating It as a Guarantee
| Outcome | When it applies | Action |
|---|---|---|
| Continue verification | The domain, direction, asset, network, address, additional identifier, amounts, conditions, and order status agree across the relevant sources. | Proceed to the final wallet preview and repeat Pass Two. This result means no discrepancy has been identified; it does not certify the transaction as risk-free. |
| Clarification required | Information is incomplete, terminology differs between interfaces, the quote changed, compliance requirements are unclear, or the order is nearing expiry. | Pause. Use the serviceโs official support channel or the receiving platformโs authenticated support route. Preserve the order identifier and screenshots that exclude secrets. |
| Stop | The address, Memo or Tag, network, asset, order identity, or destination does not match; the page requests wallet secrets; a third party applies pressure; or the operation includes guaranteed-profit claims. | Cancel the pending authorization, close the suspicious page, and reopen trusted services independently. If wallet secrets were exposed, treat the wallet as compromised and follow the wallet providerโs official incident guidance from a clean device. |
Control Route Before, During, and After the Exchange
Before Sending
- Secure the environment: update the wallet through its official distribution channel, close screen-sharing software, and avoid conducting the exchange on an unfamiliar or publicly accessible device.
- Open the exchanger and receiving platform independently rather than through unsolicited links.
- Complete Pass One and record only non-secret reference data.
- Generate or confirm the destination address inside the receiving wallet or authenticated account.
- Review the live order terms, including the rate method, amount range, expiry rules, network, and possible compliance conditions.
- At the wallet confirmation screen, complete Pass Two without interruptions.
While the Transfer Is Pending
- Save the transaction identifier, commonly called a txid or transaction hash, once the wallet broadcasts it.
- Open an explorer intended for the selected blockchain and locate the transaction by its txid. Block explorers can display transaction status, sender, recipient, amount, block, and confirmation data; the exact fields vary by network. [5]
- Compare the on-chain destination and transferred amount with the order. Never rely solely on a screenshot sent by another person.
- Keep the order page open or return through the independently verified domain. Ignore direct messages claiming that an extra payment is required to โreleaseโ the transaction.
- Allow for the confirmation rules shown for the specific order. A broadcast transaction, a confirmed network transaction, a credited deposit, and a completed exchange are separate stages.
After Confirmation
- Verify that the incoming asset reached the intended wallet or platform account.
- Compare the asset, network, and received amount with the completed order record.
- If the transfer is visible on-chain but not credited, collect the order identifier, txid, timestamps, and non-sensitive screenshots before contacting official support.
- Review wallet activity for any unrelated transfer, approval, or account change that occurred during the operation.
- Remove unnecessary wallet connections created during the process, but do not sign unfamiliar revocation or โsecurity verificationโ transactions proposed by unsolicited support accounts.
Threats Directly Relevant to Crypto-to-Crypto Exchange
| Threat | How it appears | Practical control |
|---|---|---|
| Phishing | A look-alike website, fake advertisement, cloned order interface, fraudulent browser extension, QR code, or person impersonating support asks you to sign in, send funds, or reveal wallet credentials. | Open the service independently, inspect the full domain, and keep support communication within authenticated channels. Phishing pages may imitate legitimate services and ask for a seed phrase or trigger malware installation. [6] |
| Address substitution | The pasted address differs from the copied value, changes after an extension or application opens, or a similar address appears in wallet history. | Compare the entire address on the final confirmation screen and, where available, on a hardware wallet display. Cancel the transfer after any mismatch; do not simply paste the same clipboard value again. |
| Wrong network | The same ticker is available on several networks, while the wallet defaults to a network different from the exchange deposit route. | Match the network in the sending wallet, order, and receiving platform. Treat network names as transaction-critical fields rather than optional labels. |
| Seed phrase or private-key exposure | A website, โsupport specialist,โ recovery service, bot, or wallet-check procedure requests secret words or a private key. | Stop immediately. Do not type, photograph, upload, or send the secret. Anyone with a recovery phrase may control the associated wallet, and legitimate services should not need it to trace or process an exchange. [1] |
| Guaranteed-return pitch | The exchange is reframed as an investment program: send one asset now and receive a larger amount later, with โguaranteedโ profit or no risk. | Do not treat the offer as a routine cryptocurrency swap. Guaranteed high-return and risk-free claims are established fraud indicators, especially when combined with urgency or requests for additional transfers. [7] |
Recovery and Diagnosis When Something Does Not Match
A delayed status, different amount, or changed order does not by itself identify the cause. Diagnose the transaction in sequence and avoid sending a second payment until the first one is understood.
If the Status Is Delayed
- Check whether the wallet actually broadcast the transaction and produced a txid.
- Look up that txid in an explorer for the network selected in the wallet.
- If the explorer has no record, review the walletโs pending or failed status and follow the wallet providerโs official guidance. Do not create a replacement transaction unless you understand how the wallet handles pending transfers and nonces or equivalent network rules.
- If the transaction is visible but unconfirmed, record its network status and wait according to the orderโs current instructions.
- If it is confirmed on-chain but the order remains unchanged, compare the destination address, asset, network, amount, Memo or Tag, and order validity.
- Contact official support with the order identifier and txid if the on-chain data matches the order but crediting has not occurred.
If the Sent or Received Amount Does Not Match
- Separate the transaction amount from the walletโs network fee and total account debit.
- Review whether the rate was fixed, floating, estimated, or recalculated after an expiry or amount difference.
- Check whether the sent amount fell outside the orderโs stated range or arrived in multiple transactions.
- Compare the completed order record with the receiving walletโs transaction history and the blockchain explorer.
- Request an explanation through official support if the difference remains unresolved. Provide reference data, not wallet secrets.
If the Address, Network, or Other Data Changed
- Before broadcast: cancel the wallet confirmation and reopen the order from the verified domain. Create a new order if the previous one is invalid or cannot be reconciled.
- After broadcast: preserve the txid and determine which address and network actually received the transaction. Confirmed blockchain transfers may be irreversible, and assistance or recovery cannot be assumed. [3]
- If the page may have been compromised: stop using it, scan the device through trusted security tools, review browser extensions, and change affected account credentials from a clean environment.
- If a seed phrase or private key was disclosed: do not continue using the exposed wallet as though it were secure. Consult the wallet providerโs official compromise procedure from a clean device, and distrust anyone offering guaranteed recovery for an advance payment.
Minimal Record-Keeping Protocol
Keep enough non-secret information to identify and diagnose the exchange without creating a new security or privacy risk.
| Keep | Purpose | Do not keep with the record |
|---|---|---|
| Order identifier | Lets official support locate the operation. | Account password, one-time authentication codes, or recovery answers. |
| Transaction hash or txid | Allows independent inspection of network status and transaction fields. | Private keys or seed phrases. A txid is a reference; it does not require disclosure of wallet secrets. |
| Asset pair and network | Shows the intended direction and blockchain route. | Unnecessary personal profile information. |
| Non-sensitive timestamps | Helps distinguish order creation, broadcast, confirmation, and completion. | Full device logs unless specifically required and reviewed for sensitive data. |
| Displayed send and receive amounts | Supports comparison with wallet and on-chain records. | Unrelated balances or complete account histories. |
| Redacted screenshots of the order status | Preserves visible conditions and error messages. | Seed phrases, private keys, passwords, identification documents, authentication codes, or unrelated personal details. |
The final control is simple: the domain, order, asset, network, full address, required identifier, amount, and expected result must still agree at the moment of authorization. If one critical field cannot be independently reconciled, preserve the reference data and stop before broadcasting another transaction.
