Skip to content
SecurityPro Docs

Transaction Lifecycle

This guide illustrates a typical end-to-end flow in SecurityPro: deposit → order execution → settlement.
Use this to understand which systems interact and where your integration code runs.

High-level sequence

Section titled “High-level sequence”

Transaction Lifecycle Sequence

Notes

  • Webhooks notify you of state changes (deposit.confirmed, order.filled, settlement.completed).
  • Polling endpoints (e.g., /v1/orders/{id}, /v1/account/balances) can be used as a fallback.

State diagram (order)

Section titled “State diagram (order)”

State Diagram

Transitions

  • Created → Rejected when validation fails (insufficient funds, bad params).
  • Queued → Matched when the engine finds a counterparty.
  • Partially Filled → Filled when the remaining quantity executes.
  • Queued → Canceled on user/API cancel.

Related docs