Electronic trading systems use predefined rules to determine how orders interact when they could match against orders from the same participant or account. One such control is self-trade prevention, which helps venues prevent certain transactions from occurring between orders associated with the same user, trading group, or account, depending on platform configuration.
The specific behavior depends on the venue’s implementation. Some systems cancel the resting order, others cancel the incoming order, and some reduce the quantities involved rather than canceling both orders entirely. These differences can affect order status, remaining quantity, execution records, and subsequent reconciliation.
Understanding cancel-maker, cancel-taker, and decrement rules is therefore an operational requirement. Each instruction produces a distinct result, and assuming that all self-trade-prevention controls behave alike can lead to incorrect interpretations of order histories.
What Is Self-Trade Prevention?
Self-trade prevention, often abbreviated as STP, refers to exchange or platform controls designed to stop an order from executing against another order identified as belonging to the same participant or related trading entity.
In a simplified order book, a resting order is already available in the book, while an incoming order is newly submitted and may match against it. If the venue identifies both orders as belonging to the same configured STP group, its rules determine what happens next.
These controls are not identical across platforms. Venues may differ in how they identify related orders, which order instructions they support, and whether prevention applies at the account, user, or group level. The applicable documentation should therefore be treated as the authoritative description of a venue’s behavior.
Cancel-Maker: Remove the Resting Order
Under a cancel-maker instruction, the venue cancels the resting order that would otherwise match with the incoming order. The incoming order may then continue processing, depending on its type, remaining quantity, and the venue’s rules.
For example, suppose a resting sell order offers 50 units at a particular price. An incoming buy order from the same STP group would match against it. If cancel-maker applies, the resting sell order is canceled rather than matched against the incoming buy order.
The operational consequence is that the incoming order may remain eligible to match with other orders. However, this is not a guarantee that it will execute. Its subsequent outcome depends on available liquidity, price conditions, order instructions, and other venue controls.
Records should distinguish the cancellation of the resting order from any later execution or cancellation involving the incoming order.
Cancel-Taker: Cancel the Incoming Order
Cancel-taker applies the opposite priority. Instead of removing the resting order, the venue cancels the incoming order that would create the prohibited match.
Consider the same resting sell order for 50 units. When a matching buy order arrives from the same STP group, the venue cancels the incoming order under cancel-taker behavior. The resting sell order remains in the book unless another event changes its status.
This distinction affects order continuity. The resting order retains its existing status, while the incoming order receives a cancellation outcome under the applicable venue rules.
For operational reviews, the key questions are which order was canceled, what quantity was affected, and whether the incoming order was canceled entirely or handled according to additional venue-specific rules.
Decrement Rules: Reduce Quantity Instead of Treating Both Orders Alike
Decrement behavior generally reduces the quantity associated with orders that would otherwise self-match. Depending on the venue, the system may decrement both orders by the overlapping quantity or apply another specifically documented quantity-adjustment rule. Some implementations may also cancel an order if its remaining quantity reaches zero.
For example, a resting order has 50 units and an incoming order has 30 units. If the venue’s rule decrements both by the overlapping quantity, 30 units are removed from each order’s quantity. The incoming order is fully depleted, while 20 units remain on the resting order.
The outcome differs from cancel-maker and cancel-taker because the venue applies a quantity adjustment rather than simply selecting one order for cancellation. This can complicate reconciliation if the system records the decrement as a specialized order event rather than a conventional fill.
A decrement should not automatically be interpreted as an executed trade. The event’s meaning must be confirmed through venue documentation and the corresponding order reports.
Comparing the Three Instructions
The following comparison assumes the venue supports these behaviors in the simplified form described. Actual implementations can differ.
- Cancel-maker: The resting order is canceled; the incoming order may continue.
- Cancel-taker: The incoming order is canceled; the resting order may remain active.
- Decrement: The overlapping quantity is reduced according to the venue’s defined rule; remaining quantities depend on the original sizes and implementation.
These rules create different downstream records. Cancel-maker can remove existing book liquidity. Cancel-taker can prevent the incoming order from continuing. Decrement can change quantities without producing a conventional execution.
For this reason, order status alone may not explain the full result. Reviewers should also inspect order identifiers, event types, quantity changes, timestamps, and any venue-specific STP indicators.
Operational Records and Reconciliation
Reliable self-trade prevention monitoring requires a record of both the configured instruction and the resulting order events.
Useful fields include the original order quantity, remaining quantity before and after the event, resting and incoming order identifiers, STP mode, cancellation reason, event timestamp, and venue sequence information where available.
When reviewing a discrepancy, establish which STP instruction applied and whether the platform generated a cancellation, decrement, or other event. Compare the reported quantity changes with the documented rule. If the records do not align, preserve the original messages and investigate rather than rewriting the order history based on assumptions.
These controls also matter when data from multiple systems is combined. An internal dashboard may simplify venue-specific event types, potentially hiding distinctions that are necessary for accurate reporting.
The Kenson Perspective: Deterministic Controls Need Clear Records
At Kenson Investments, operational discipline begins with understanding how system rules affect recorded activity. Self-trade prevention illustrates why a control’s label is not enough: its actual behavior depends on the venue’s implementation, configuration, and event reporting.
A disciplined review connects the configured instruction to the resulting order states and quantity changes. This supports clearer records, more consistent reconciliation, and better visibility into operational exceptions.
The broader principle is that controls should be understood before their outputs are interpreted. Documenting expected behavior and comparing it with actual event records helps maintain accountability without assuming that different platforms operate identically.
Continue Learning with Kenson Academy
For more educational resources on digital asset infrastructure, market mechanics, and operational risk, visit Kenson Academy and the Kenson Knowledge Center. Understanding venue controls and their reporting behavior helps readers interpret digital market activity with greater precision. Connect with us today.
Disclaimer: The information provided on this page is for educational and informational purposes only and should not be construed as financial advice. Cryptocurrency assets involve inherent risks, and past performance is not indicative of future results. Always conduct thorough research and consult with a qualified financial advisor before making investment decisions.
“The cryptocurrency and digital asset space is an emerging asset class that has not yet been regulated by the SEC and the US Federal Government. None of the information provided by Kenson LLC should be considered as financial investment advice. Please consult your Registered Financial Advisor for guidance. Kenson LLC does not offer any products regulated by the SEC, including equities, registered securities, ETFs, stocks, bonds, or equivalents.”
