After reading this guide, you should be able to open a BTC, ETH or USDT exchange order, understand what its current status means, and decide what to check next without guessing. You will also know which order details must match your wallet transaction before you send funds.
Only a few concepts are needed. An exchange order records the terms of a proposed swap. A blockchain transaction moves the crypto. A network confirmation shows that the transaction has been included in the blockchain’s history. These are connected events, but they are not the same event.
Why an order can be open while the transaction is still pending
Think of an exchange order as a shipping instruction and the blockchain transaction as the parcel. Creating the instruction does not mean the parcel has been sent. A tracking number proves that a shipment was registered, but it does not prove that the recipient has accepted it.
The analogy stops there. Cryptocurrency transfers are processed by blockchain networks rather than delivery companies, and a confirmed transfer usually cannot be recalled simply because the sender made a mistake. Ethereum’s official guidance states that a transaction sent to the wrong address cannot normally be reversed. [1]
An exchanger therefore tracks at least two layers of progress:
- Order progress: whether the service has created the order, detected the deposit, checked it, calculated the exchange and prepared the payout.
- Blockchain progress: whether the deposit or payout was broadcast, included in a block and given the required confirmations.
The exact labels and their order vary between services, assets and exchange directions. Compliance checks can also affect what information is requested and whether an order moves to manual review. Current requirements should be checked before creating the order.
Common exchange order statuses in plain English
Created or awaiting payment
The order exists, but the service has not yet matched an incoming transfer to it. At this stage, check the send asset, network, deposit address, required amount and any Memo or Tag displayed in the order.
Do not interpret “created” as “funds received.” If you have already sent the crypto, compare the order’s deposit details with the completed withdrawal in your wallet. A delay may mean that the transaction has not been broadcast, has not reached the address, or has not yet been detected.
Payment detected or received
The system has found a transaction associated with the order. This does not always mean the deposit is ready for exchange. The transaction may still need blockchain confirmations, and the received amount or network may require checking.
Bitcoin transactions are broadcast to the network and then confirmed through inclusion in blocks. Bitcoin documentation also explains that additional confirmations increase confidence in the transaction. [2]
Confirming
The deposit is visible on the relevant blockchain, but the service is waiting for its required confirmation state. The threshold is a service policy and may differ by asset, network, risk assessment and current operating conditions. Do not assume a fixed number from another exchange or an old order.
A transaction may appear in your wallet before the exchanger marks the deposit as sufficiently confirmed. That difference is not automatically an error: the wallet and the service may apply different acceptance rules.
Processing or exchanging
The deposit has moved beyond initial detection and the order is being handled under its stated terms. Depending on the service workflow, this stage may include amount verification, compliance review and preparation of the outgoing transfer.
“Processing” is an order status, not a promise of a specific completion time. Avoid estimating a deadline unless the order itself provides a current, clearly defined time condition.
Sending or payout in progress
The service is preparing or has initiated the outgoing side of the exchange. Look for a payout transaction ID, often called a txid or transaction hash. If one is displayed, it can be checked in a block explorer for the correct network.
Ethereum block explorers can show a transaction hash, status, sender, recipient, transferred value, fee and block information. The transaction hash is generated when the transaction is submitted. [3]
Completed
The exchanger considers its order workflow finished. You should still verify the practical result: check the receiving wallet, confirm the asset and network, and compare the incoming amount with the order record.
If a txid is available, use the appropriate blockchain explorer rather than relying only on a screenshot, email or support message. A valid txid lets you check the recorded sender, recipient, amount and transaction state. Bitcoin Core documentation describes the TXID as the transaction’s identifier. [4]
Expired, failed, cancelled or under review
An expired order may have passed its payment window before a matching deposit was detected. A failed or cancelled label means the normal workflow did not complete, but it does not by itself explain what happened to funds already sent. “Under review” usually means automated processing has paused while details are checked.
Before sending a second payment or creating a replacement order, establish whether the first transfer was broadcast. Save the order identifier and txid, then follow the support procedure shown by the service. Never send a private key or seed phrase as proof of payment.
Anatomy of a hypothetical exchange
Consider a neutral training example: a user wants to send USDT and receive ETH. This is not a claim that a particular pair or network is currently available. The user must first check the live exchange form because supported assets, pairs, networks and directions can change.
The exchanger in this example supports assets including USDT, BTC and ETH, while adding assets gradually. That does not imply that every possible pair or blockchain network is available at a given moment.
Selected send asset: USDT
What it means: USDT is the asset leaving the user’s wallet.
Where it comes from: the user selects it in the exchange form and confirms that the wallet actually holds the same asset.
What to compare: match the ticker and, where displayed, the token or contract information. USDT exists on multiple blockchain protocols, so the asset name alone is not enough to identify the transfer route. Tether directs users to its supported-protocol information for the current list. [5]
What an error causes: sending another token because it has a similar name or appears in the same wallet can prevent automatic crediting and may make recovery difficult or impossible.
Selected network
What it means: the network is the blockchain route used to carry the deposit. It is part of the transfer instruction, not a cosmetic preference.
Where it comes from: the exchanger shows a supported deposit network, and the sender chooses the matching withdrawal network in the wallet or platform holding the USDT.
What to compare: read the complete network name on both sides. Do not decide based only on a familiar address format or a lower fee shown by the sending platform.
What an error causes: the transfer may go to a network the receiving service does not monitor for that order. The address can look plausible while the route is still wrong.
Deposit address
What it means: this is the destination to which the user sends the deposit.
Where it comes from: it is generated or displayed on the order page after the relevant order details are selected.
What to compare: compare the beginning, middle and end of the address after pasting it into the wallet. Also verify that it still matches the current order and selected network. Clipboard-replacement malware and phishing pages can substitute an attacker’s address.
What an error causes: a transfer to another valid address may be irreversible. Do not type a long address from memory or copy it from an old order.
Memo or Tag, if displayed
What it means: a Memo or Tag is an extra identifier used by some receiving systems to associate a shared deposit address with the correct customer or order.
Where it comes from: the order page supplies it when the selected asset and network require one.
What to compare: copy the value into the matching Memo, Tag or destination-tag field in the sending interface. If the order does not show such a field, do not invent one.
What an error causes: the blockchain transfer may reach the service’s address but fail to attach automatically to the correct order. Contacting support may then be necessary, and recovery is not guaranteed.
Amount to send
What it means: this is the deposit amount expected by the order.
Where it comes from: it is calculated from the amount entered in the exchange form and the order conditions shown before confirmation.
What to compare: determine whether the wallet or withdrawal platform deducts its network or withdrawal fee from the entered amount. The amount that arrives matters, not only the amount typed into the send box.
What an error causes: an underpayment or overpayment may prevent automatic processing or change how the order is handled. Do not split a payment into several transactions unless the order instructions explicitly allow it.
Expected amount, rate and fee
What they mean: the expected amount is what the order indicates the recipient should receive under the displayed terms. The rate describes the conversion between the two assets. A fee is a stated charge associated with the service or transfer.
Where they come from: they must be taken from the current order interface, not from a search result, an earlier order or a market-price widget.
What to compare: check whether the receive amount is described as estimated or fixed, what event locks the rate, and which charges are already included. Cryptocurrency prices can move while an order is open.
What an error causes: assuming that every displayed number is final can create a false expectation about the payout. If the pricing terms are unclear, pause before sending.
Status and txid
What they mean: the status describes the exchanger’s current processing stage. The txid identifies a blockchain transaction.
Where they come from: the order page supplies the status. The sending wallet supplies the deposit txid after broadcast, while the exchanger may later provide a separate payout txid.
What to compare: do not confuse the order number with either transaction ID. Check each txid in an explorer for its own network and compare the destination and amount with the relevant side of the order.
What an error causes: checking a deposit txid as if it were the payout can make a normal order look stuck. Searching the wrong network’s explorer may also produce no result even when the transaction exists elsewhere.
The pause before sending
Before approving the withdrawal, stop and explain the operation to yourself in one sentence: “I am sending this asset, over this network, to this address, with this Memo or Tag if required, and the recipient should receive this asset at this address.”
If you cannot state each element without looking at several conflicting screens, the operation is not ready. Recheck:
- The send asset and receive asset.
- The exact deposit network selected in the order.
- The network selected in the sending wallet.
- The full destination address after pasting.
- The Memo or Tag when one is displayed.
- The amount expected to arrive after applicable withdrawal deductions.
- The rate rule, shown fees and expected receive amount.
- The order’s current payment instructions and validity conditions.
Never disclose a seed phrase, private key, wallet password or remote-access code to complete this check. Those secrets are not required to locate a public blockchain transaction.
Beginner mistakes: appearance, cause and prevention
The wallet says “sent,” but the order says “awaiting payment”
How it looks: the wallet displays a transaction, while the order has not changed.
Why it happens: the transaction may be pending, sent through another network, directed to the wrong address, missing an identifier, or not yet matched by the service.
What to do before sending: copy the deposit details directly from the active order and compare them with the wallet’s final confirmation screen. After sending, use the txid to inspect the actual blockchain record.
The correct asset is sent over the wrong network
How it looks: both interfaces say USDT, yet the order does not detect the deposit.
Why it happens: the sender treats USDT as one universal balance and overlooks that tokens can operate through different blockchain protocols.
What to do before sending: match the complete network labels. If the order does not offer the network available in your wallet, do not improvise or choose a “similar” option.
An address was copied from a previous order
How it looks: the address format appears valid, but it is not the destination shown in the current order.
Why it happens: browser history, saved notes or wallet address books are used instead of the live order page.
What to do before sending: treat every order as a separate instruction. Copy the address again and compare multiple sections after pasting.
The order number is mistaken for a txid
How it looks: a block explorer returns no transaction.
Why it happens: both values can be long strings, but they belong to different systems.
What to do before sending: note where each identifier appears. The order number is used with the exchanger; the txid is generated when a blockchain transaction is submitted.
A status message is treated as proof of receipt
How it looks: “completed” appears, but the user has not checked the receiving wallet or payout transaction.
Why it happens: the service status is mistaken for the final wallet balance.
What to do before sending: decide in advance how the outcome will be verified: the correct asset in the intended wallet, supported by a matching payout txid when one is provided.
A first independent check
Start with a currently available pair and network rather than assuming that every BTC, ETH or USDT direction is supported. Read the live conditions, confirm any verification requirements, and then open the exchange form and compare the order fields with the wallet you intend to use.
- Create the order only after confirming the asset pair and network.
- Read the deposit address, amount and Memo or Tag requirement from that order.
- Match those details on the wallet’s final send screen.
- Pause before approval and restate the operation in plain language.
- After broadcast, save the order identifier and deposit txid separately.
- Track both the blockchain transaction and the exchanger’s status.
- When the order is completed, verify the received asset, network, address and amount.
- If the details disagree, stop. Do not send a second transfer until the first one has been traced.
This process cannot remove volatility, phishing, compliance delays or the consequences of entering incorrect data. It does replace vague status watching with a checkable sequence: order details, wallet transaction, blockchain record and final receipt.