What it covers
An eligible order that executes materially outside its published protected benchmark because of a failure Orbitra controls.
ApexMatch execution protection
An order does not simply meet the book. It receives candidate prices from native depth, from firm market-maker quotes and from a protected price-improvement auction at the same moment, and it fills at the lowest expected all-in cost — with a receipt that explains the decision.

Best execution
Execution receipt
The candidate with the lowest expected all-in cost is selected
Candidate prices arrive together from the native book, from firm RFQs and from a protected auction. A reference-price ring validates market quality, ApexMatch selects the lowest expected all-in cost, and the receipt records the benchmark, the candidates, the decision, the fees and the finality proof.
Sequence
The signed order enters the protocol with its constraints: side, size, limit, time in force and routing preferences.
Native book depth, firm RFQs and a protected auction produce executable candidate prices in the same window.
Each candidate is validated against the published reference price, so an improved price is measured, not asserted.
Aegis evaluates margin, policy and liquidation distance before anything is committed.
ApexMatch selects the lowest expected all-in cost — price, fees and expected impact together, not price alone.
The fill is written with its evidence and a QSE finality certificate, and the receipt is retrievable through the API.
Order types, time-in-force and algorithmic behavior are documented on the execution page.
Evidence
Receipts are available for eligible orders through the institutional API and the Orbitra Prime interface.
The policy
Execution Protection is a defined policy with published boundaries. It is not insurance, and it never compensates for market direction, volatility or your own risk decisions.
An eligible order that executes materially outside its published protected benchmark because of a failure Orbitra controls.
Defined by market, order type, size band and market state at decision time. Eligibility is shown before the order is sent.
Halted or circuit-broken markets, self-crossing, non-eligible order types, client-side delay and force-majeure events.
A published tolerance before any credit applies, and per-order and per-period caps that are disclosed in the policy schedule.
The claim is evaluated from the execution receipt and the reference source, not from a screenshot or a recollection.
A published dispute path with defined response stages. Credits are funded by Orbitra, never by other customers’ collateral.
Execution Protection is not protection from market losses.
It addresses one specific failure: an eligible order executing materially outside its protected benchmark because of something Orbitra controls. Market movement, slippage inside tolerance and the consequences of your own leverage are not covered. Read the risk disclosure and the trading and leverage risk disclosure.
By the published tolerance for that market and size band, measured against the reference price recorded in the receipt. Below the tolerance, no credit applies.
The auction window is short and bounded, and it runs only where it can improve the expected all-in cost. Orders that require immediacy are not delayed for it.
Yes. Routing preferences are part of the order, and institutional accounts can express them as policy rather than per order.
From Orbitra’s own resources under the published policy. Customer collateral and the protection fund are separate and are never used for this purpose. See the liquidity network.
The Net Outcome Index defines how improvement is measured. Every market page shows the complete cost of holding.