Check your risk rulesbefore an order is routed.

Keep your trading stack. Check proposed orders against the policy for each account. Connect the decision to the order route, with clear rules for stale inputs or an unavailable check.

Contact

Explore the foundation

Gateway / Order decision

A decision with a reason.

PermitDECISION / 0142

Within the approved policy.

Required inputs are current and the proposed order fits the available capacity.

Policy
MANDATE-A / v3
Evidence
Current for this check
Route response
Proceed within decision scope

The execution route must enforce the result.

Each result reflects the account, policy and evidence used for the check.
01

Permit, reject or hold for each request

02

Policy version and evidence behind the result

03

Decision records linked to the order route

Product view

Review the reason behind each risk decision.

Keep the proposed order, policy result and connected route response together for review.

gateway decision log with permit, reject and hold outcomes, order scope and execution connector enforcement details.
Decision and evidence
Policy version
Policy version
Connected route response
Connected route response

What it covers

Give every order check a clear contract.

A decision includes an account, policy version, evidence timestamp and expiry. Define this contract alongside pending-order reservations and failure behavior.

Assess the proposed order

Evaluate the requested action against the relevant account and policy. Consider existing exposure, pending-order reservations and the freshness of the inputs.

  • Order, account and policy context
  • Pre-trade limits and reserved capacity
  • Permit, reject or hold with a reason

Integrate with the manager’s existing trading system

Agree the decision contract and enforcement point with the external manager or execution provider. Cover order amendments, cancellations and retries as part of that design.

  • External manager or order and execution management system (OEMS) integration
  • Decision identifiers, policy versions and expiry
  • Order lifecycle and reconciliation of reservations

Make failure behavior explicit

A failed or incomplete check grants no permission. Define the desk’s response and verify that the order route applies it during delay, stale data and service interruption.

  • Timeout and stale-data handling
  • Unknown account or missing-limit behavior
  • Bypass prevention, incident ownership and recovery

Where it connects

The decision needs an enforcement point.

Agree where the call sits in the manager’s order route and how that route handles every result.

The external gateway integrationAn external manager requests a decision. A connected order route must enforce the response before reaching the venue. A policy and evidence service supports the assessment. Bypassed routes are outside this control.RISK GATEWAY / ORDER ROUTEExternal managerExisting trading stackRisk decisionPolicy + evidenceEnforced routeHonors the resultCovered venueOrder and fill recordDECISION CONTEXTAccount · Policy version · Exposure · Reservations · FreshnessEnforcement is part of the integration. An API response alone does not block a bypass route.
  1. 01

    External manager

    The existing trading stack proposes an order.

  2. 02

    Risk decision

    Policy, exposure and current evidence determine the result.

  3. 03

    Enforced route

    The connected route honors permit, reject and hold.

  4. 04

    Covered venue

    The order and later fill retain their decision context.

An API response alone cannot block a route that bypasses the integration.

Route coverage and failure behavior follow the agreed integration and its validation.

In practice

The limit travels with the order decision.

A proposed order exceeds the available account limit. The gateway returns Reject with the policy and evidence used. The connected route holds the order back and retains the decision record.

01

Request

Proposed order with account and policy scope.

02

Assess

Current exposure, pending reservations and input quality.

03

Enforce

The connected route honors permit, reject or hold.

04

Record

Keep the decision, order and later outcome linked.

Implementation

Plan your implementation.

Define the inputs, responsibilities and checks for your operation.

Your inputs
Risk ownership, covered order routes and failure policy.
Corbel configures
Decision contract, policy evaluation and integration evidence.
Validation & controls
Test latency, concurrency, capacity reservations, expiry and bypass handling.

Corbel, configured for you

We build your risk policy into connected order routes.

Share your order routes and risk policy. We’ll define the decision contract and validate enforcement with your execution provider.

Contact

Your privacy

Cookie settings

Choose whether to allow optional analytics on this website.

Your saved choice

Essential

When available, browser storage remembers your choice. This preference is kept in your browser and is not sent to an analytics provider.

Optional analytics

Off

Optional analytics is not enabled on this site.