Skip to content
All library documents

Exchange Self-Trade Prevention Modes and Prevented Match Accounting

Article Binance API docs

Summary

The document explains how an exchange prevents orders from the same account or trade group from matching. It describes six modes: allowing a match, expiring the taker or maker remainder, expiring both, decrementing both orders’ available quantities, and transferring value in a specific cross-account case. Usually the incoming taker’s mode controls; transfer requires both orders to specify that mode, otherwise decrement applies. Symbol settings determine which modes are allowed and the default used when a trader omits one.

Examples and API response fields show how prevented matches and quantities are recorded, how accumulated prevented quantity affects the amount still available, and why an order may receive an expired-in-match status. The transfer example also illustrates changes to account balances when group-linked accounts prevent a match. These details support order handling and reconciliation. The document is exchange-specific operational guidance rather than a trading strategy; configured modes and available fields may vary by symbol or API, so implementations should verify current exchange rules.

Key ideas

  • Self-trade prevention can apply to orders from one account or from accounts sharing a trade group.
  • The taker’s selected mode usually determines the response, while transfer requires both orders to select transfer.
  • Expire modes cancel specified remaining quantities, whereas decrement reduces the available quantities on both orders.
  • Prevented match records and prevented quantity fields help explain order status and reconcile remaining size.
  • Allowed modes and defaults depend on symbol configuration.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.