Self-Trade Prevention (STP): When Your Orders Meet Each Other

Sometimes an order disappears without executing or being rejected. Its log says canceled, although you never canceled it. The exchange may have removed it automatically when it encountered another order from your account. This rule is self-trade prevention, or STP.

Your own orders do not execute against each other

Buy and sell orders normally match when their prices overlap. If they belong to the same account, an STP-enabled matching engine instead stops that match and cancels one or both.

Trading against yourself can manufacture volume without a genuine change of ownership. Exchanges block this at the engine level for market-data integrity and regulatory reasons. Intentional and accidental collisions are subject to the same rule. See execution priority for order queues and reading the order book for the book itself.

Three modes: Which order disappears?

Names vary by venue, but three common modes determine which order is removed.

The guide highlights ② as particularly dangerous. A separate additional-entry order can overlap a take-profit limit, allowing the entry while silently removing the target. The position remains without its intended exit. Partial executions complicate this further; see partial fills for remaining quantities.

Where it happens ① Grid bots

Grids maintain buy and sell ladders simultaneously. Narrow price ranges or close spacing can bring your own orders together.

A missing grid level does nothing when price returns. Over several days, scattered holes can make the bot behave differently from its design. See grid trading for the structure and grid bot optimization for spacing.

Where it happens ② Simultaneous longs and shorts in hedge mode

Hedge mode allows a long and short in the same instrument. The collision described here involves a long-entry buy and a short-entry sell at the same price; closing a long and opening a short are both sell-side actions and do not themselves form an opposing pair.

A breakout straddle cannot be implemented by two opposing plain limits at the same price. The original guide proposes separating levels, illustrating buy $59,900 / sell $59,800, or using separate conditional triggers. Those quoted plain-limit prices would still cross if simultaneously active; order type and trigger direction must implement the intended separation. See one-way and hedge position modes.

Where it happens ③ Multiple API keys

Different keys do not necessarily mean different STP identities. STP commonly applies at account or subaccount-group level. Two bots using different keys on one account can belong to the same group.

If strategies can oppose one another, the guide suggests separate subaccounts, subject to the venue's STP grouping. See API keys for permissions. Repeated cancellation and replacement consume request capacity before fees, potentially delaying a needed stop request.

How to detect a cancellation

STP cancellation differs from rejection. A rejected request returns an error, whereas an STP order may be accepted first and change state afterward, so the initial response looks successful.

For bot operation, the guide recommends checking order status again after several seconds instead of trusting submission alone. This detects an allegedly resting stop that no longer exists. Other causes of nonacceptance are covered in order rejection reasons.

Ways to reduce collisions

Reduce-only in ② does not disable STP, but prevents an exit from creating new exposure and simplifies its purpose. See post-only, reduce-only and IOC. Rule ③ matters because a new order submitted before cancellation completes can briefly coexist with the old order at the same price, creating a collision window.

Fees and trading volume

A quantity canceled by STP is not executed, so it incurs no execution fee and adds no trading volume. It cannot manufacture volume toward a VIP tier.

STP itself does not debit money. Loss can arise because an order you thought existed is absent. See fee tiers and VIP levels and trading frequency and fee drag.

Recap

An STP cancellation may not produce an obvious alert. If your approach maintains several orders, periodically confirming that supposedly resting orders are still live is part of operating it reliably.

Caution

Prices including $60,100, $60,050, $59,900 and $59,850; quantities of 2, 1 and 0.4 contracts; $50 grid spacing; three-level ladders; and the two-key or subaccount arrangements are hypothetical illustrations, not measured accounts or live quotes. STP details vary by exchange: default mode, per-order configuration, account grouping, reason codes and reduce-only handling must be checked in that venue's API documentation and trading rules. This explains execution mechanics without recommending a particular strategy or bot configuration. Leverage can lose all principal, and accurate order management does not guarantee profit. Decisions and outcomes remain your responsibility.