You can trade when withdrawals are temporarily closed because the restriction is applied to the creation and confirmation of a withdrawal request, not to order matching inside the trading engine.
The restriction is recorded in withdrawal request statuses and account parameters, but it is not used by the matching engine when accepting and executing limit and market orders.
Funds remain on the account's internal balance, participate in available margin calculations and change when trades are executed; those changes are reflected in order reports and the trade feed.
🔒 What a temporary withdrawal closure means
A temporary withdrawal closure means that the crypto exchange's payment module prevents the account from completing a transfer of funds outside the platform, while the assets remain on the internal balance.
The restriction is applied at the withdrawal request processing stage and stops the flow before data is passed to an external payment gateway or blockchain.
A withdrawal closure is recorded in the account's operation history as a request status without sending confirmation and as a withdrawal operation with no txid.
| System element | Action performed | Where it is recorded |
|---|---|---|
| Withdrawal form | Blocks confirmation and completion of the withdrawal request | Operation status in withdrawal history |
| Payment module | Stops request processing before it is passed to the external layer | No txid and no sent marker |
| Internal account balance | Continues to account for assets without debiting them outside the platform | Account balance and funds movement report |
Which operation is blocked
The blocked action is the transfer of funds to the external layer through the withdrawal mechanism.
The verifiable sign is that the request remains in withdrawal history without a txid and without a sent status.
Which operations continue
Execution of trading orders and recalculation of the internal balance continue without changes.
The verifiable sign is that trades are recorded in the trade feed and in order reports.
The diagram shows the boundary between withdrawal request processing and trading order execution without detailing internal checks.
⚙️ Why trading continues when withdrawals are closed
Trading continues when withdrawals are closed because the trading engine checks order parameters and the state of the account's internal balance without using withdrawal request status data.
Withdrawal status is processed by the payment module and recorded separately, while the matching engine makes decisions based on the order book and execution priority.
| System component | Action | Where it is recorded |
|---|---|---|
| Trading engine | Accepts and executes orders when sufficient funds are available | Order report and trade feed |
| Order book | Determines execution price and volume based on active limit orders | Order book in the trading interface |
| Payment module | Prohibits transfers of funds outside the platform | Withdrawal history and operation status |
- Order submission: the trading interface sends the order parameters to the trading engine.
- Funds check: the risk module confirms the available balance or margin on the internal account.
- Matching: the matching engine executes the order across order book levels.
- Recording: each fill is recorded in the trade feed and in the order report.
- Accounting: the internal balance is recalculated based on fills and fees.
Record in the order book
The account's limit order is placed at a specific price level and joins the execution queue.
The verifiable sign is that the order volume is visible in the book before execution or cancellation.
Record in the trade feed
A market order creates a sequence of trades when it is matched against available limit orders.
The verifiable sign is that trade feed records correspond to partial fills in the order report.
🧪 How to verify that only withdrawals are blocked while trading is available
The check is performed by comparing account actions and records in three system points of evidence: withdrawal log, order book and trade feed.
If the payment module blocks withdrawals, the withdrawal request does not move to sending and does not receive a txid, while the trading engine continues accepting orders and creating trades.
| System checkpoint | Action | Result record |
|---|---|---|
| Withdrawal history | Create a withdrawal request for an asset and network | Request status without txid and without a sent marker |
| Order book | Place a minimum-size limit order | Order volume appears at a specific price level in the book |
| Trade feed | Execute a minimum-size market order | Trade records with execution price and volume |
| Order report | Review the parameters of the executed order | Recorded price, volume, fee and execution status |
| Internal balance | Check the account state after the trade | Balance or margin changes including the fills |
⛔ Record of the withdrawal block
The withdrawal request remains in the operation log without a transaction identifier and without moving into a sent state.
The verifiable consequence is the absence of a txid while the request status remains unchanged.
✅ Record of available trading
A limit order appears in the order book, and a market order creates one or more trades.
The verifiable consequence is trade records in the feed and a completed order report.
The verification diagram reflects separation between the payment layer and the trading engine without accounting for interface differences between exchanges.
⚠️ When a withdrawal closure starts blocking trading
A closed withdrawal function starts blocking trading only when the risk module changes the account status and prohibits trading operations before an order is passed to the trading engine.
The blocking decision is not made during order matching; it is made at the account-status check stage, which runs before order registration.
- Event record: the security or compliance system assigns a trading restriction status to the account.
- Status check: the risk module checks the account status when an order is being created.
- Order rejection: the order is not passed to the trading engine and is not registered.
- Rejection record: the rejection is recorded in the account action log without records in the order book or trade feed.
🚫 Order creation blocked
The system prohibits sending limit and market orders to the trading engine.
The verifiable consequence is that the order is absent from the order book and has no execution report.
⏸ Position operations blocked
The system prohibits position closing and transfers between internal accounts.
The verifiable consequence is that the operation rejection is recorded in the account action log.
Trading restrictions arise from account status and are checked before an order is passed to the trading engine.
🧭 What to do if withdrawals are closed but trading is available
Actions depend on which operations the trading engine accepts and which statuses are recorded in the account profile and operation log.
The goal is to confirm that the restriction applies only to the withdrawal payment layer and does not extend to order matching or trade recording.
- Record the withdrawal status: open withdrawal history and check that the request has not received a txid and has not been passed to the external payment layer.
- Check the trading layer: place a minimum-size limit order and confirm that it appears at a specific price level in the order book.
- Record execution: execute a minimum-size market order and check the trade record in the trade feed or order report.
- Control activity: keep current order size and order frequency parameters stable, without abrupt changes.
| Action | What is recorded | Recording point |
|---|---|---|
| Withdrawal history | No transfer of the request to the external layer | Request status without txid |
| Limit order | Order registration by the trading engine | Order book |
| Market order | Trade execution fact | Trade feed or order report |
| Account balance | Change in balances after the trade | Balance or margin report |
🧾 Confirmation that trading is available
The trading engine accepts orders and records trades when there is no trading restriction in the account status.
The verifiable consequence is that orders are displayed in the order book and trades are recorded in the trade feed.
🛑 Keeping the current account status
Stable trading parameters do not create new signals for the risk module.
The verifiable consequence is that the account log has no new records about trading operation restrictions.
This framework shows how trading can remain available while the payment layer is closed, but it does not explain which signals lead to a withdrawal block or how the risk module makes that decision. Those mechanisms are covered in the article Why an exchange freezes withdrawals.