Matching Engine & Core Modules

A white-label exchange requires more than a frontend shell. The user experience depends on reliable core modules behind trading, accounts, risk, and settlement.

Core modules

Module	Role
Matching and order lifecycle	Handles order submission, matching state, cancellation, and execution records.
Account and position system	Maintains balances, margin state, positions, and trading availability.
Risk controls	Coordinates leverage, margin, liquidation, and abnormal market behavior.
Market data	Distributes prices, depth, trades, and chart data to trading interfaces.
Settlement and records	Keeps trading history, balance changes, and operational records aligned.

Documentation path

Start with trading rules before API integration. Product, operations, and development teams should share the same understanding of order types, margin behavior, fees, and liquidation logic.

Order Types

Review supported order behavior.

Margin Rules

Understand margin requirements.

REST API

Connect backend workflows.

Implementation questions

Which order and condition-order types are exposed to users?
Which service owns symbol rules, precision validation, and trading availability?
How are order, trade, position, balance, and settlement records reconciled?
Which identifiers remain stable across REST responses, WebSocket events, and partner records?
What monitoring and rollback path applies when matching, risk, or market data becomes unavailable?

Answer these questions before frontend development so product behavior, API handling, operations, and support use the same trading model.