From signal to exchange position
A typical flow has five distinct steps: read market data, evaluate a trading rule, apply account limits, submit an order, and confirm the exchange result. The distinction between submitted and filled matters. A request can time out after Binance has accepted it, or Binance can reject it before any position opens.
For example, a qualified short signal may arrive while the account already has its maximum number of bot-managed positions. A responsible execution layer skips the new order instead of sending it. If the account is eligible and Binance accepts the request, the service should use exchange order and position data—not just its own initial request—to show the current state.
Which API permissions matter?
Public market-data endpoints and signed account/order endpoints are different. Binance's API security documentation explains endpoint permission types and signed requests; Futures endpoints have their own product documentation. Trading permission allows an application to submit orders, which can create losses. It is not the same as withdrawal permission.
MW Trader checks for Futures access and a trusted server IP, and rejects withdrawal-enabled keys. The account holder can revoke the key in Binance. The key-security guide explains how to evaluate those controls.
What the MW Trader dashboard adds
MW Trader exposes connection status, execution settings, bot-managed positions and historical records for the connected account. The backend performs execution and reconciliation; the browser displays account state and lets the member change allowed settings. Leaving a browser tab open is not the execution mechanism.
A paused or stopped new-entry state does not mean an existing position has closed. Always distinguish new order permission from open-position management. The site's How It Works page shows the current product flow.
Where automation can fail
- An expired or revoked key prevents authenticated requests.
- A changed IP restriction can make a previously working connection invalid.
- Binance can reject an order because of symbol rules, balance, risk limits or service conditions.
- Network interruption can leave the browser unsure whether a request succeeded.
- Exchange position data may take time to reconcile after a manual close or partial fill.
When the state is uncertain, inspect Binance directly before retrying a close or changing settings. Read the connection failure checklist.