An order is not a transaction guaranteed to be completed.
Placing an order signifies the submission of an intent to the trading system; an execution indicates that all or part of that intent has been matched. A limit order may remain unfilled for an extended period or be executed in multiple stages. Before reviewing Binance spot orders, ensure you have verified the account entity, trading pair, order direction, and product type; do not assume that terminology used for other products applies here. This text explains publicly visible fields; it does not constitute trading advice, nor does it confirm that the service is available in your jurisdiction.
Partial execution and order cancellation can occur together.
After a portion of an order has been executed, the remaining part may be cancelled. A successful cancellation typically affects only the unfilled quantity; it cannot reverse trades that have already been completed. To understand the full picture, verify the original quantity, cumulative executed quantity, remaining quantity, and final status, and examine the individual trade records and associated fees. Simply noting that an order is "cancelled" does not mean that no change in assets occurred.
Order validity types influence how the remaining quantity is handled.
In applicable interfaces, parameters such as GTC, IOC, and FOK define specific validity or execution conditions. IOC (Immediate-or-Cancel) allows for the immediate execution of any matchable portion, with the remainder being cancelled; FOK (Fill-or-Kill) requires the entire order to be executed according to its rules, otherwise, it is cancelled. Specific support depends on the trading pair, the interface used, and current documentation. Do not interpret these conditions as a guarantee of a better-than-market price or as a guarantee that an order will necessarily be accepted by the system.
Reconciling executions using a hypothetical order.
Suppose you place an order to sell 10 units; if only 4 units are executed and the remaining 6 are subsequently cancelled, your ledger must reflect the 4 units actually traded along with the corresponding fees. The limit price of an order is not necessarily equal to the final weighted average price of all executed trades; the asset used for transaction fees may also differ. The examples provided are intended solely to illustrate quantitative relationships and do not represent any specific cryptocurrency or actual market price; please refer to the official transaction receipts from your own account for accurate calculations.
Do not blindly place new orders following a network error.
A request timeout does not necessarily mean the server failed to receive your order. Before retrying, verify the order status using the order ID, client-side identifier, or official inquiry channels. Be aware that there may be a time lag between an inquiry or cancellation request and its processing; ensure you save the responses and subsequent status updates. Never share your API keys, signatures, or full account details with unknown individuals claiming to provide troubleshooting assistance, and never grant elevated permissions in an attempt to resolve errors.
Maintain the link between an order and its subsequent executions.
Record the order ID, trading pair, timestamp, quantity, order type (validity condition), status, individual trade executions, fees, and any error messages. When exporting data in bulk, preserve the relationship between the order level and the execution level to avoid double-counting. Platform rules are subject to change; this text does not replace the latest API documentation or account terms, nor does it guarantee that any specific order will be completed at an expected time or price.