Deployment and licensing
Trading Core is developed and owned by Qirin X Co., Ltd. Clients use it under a licence from Qirin X, each in its own environment.
Deployment model
Section titled “Deployment model”- Your instance. Each client runs Trading Core in its own environment. Instances are not shared between clients.
- Your data. Customer data, ledger records and transaction history belong to the client and stay in the client’s environment.
- Your providers. Wallet infrastructure, blockchain-analytics screening, the Travel Rule network, market data and liquidity providers are contracted by the client and connected through standard interfaces.
- Your back office. Trading Core connects to Qirin X’s KYC / CDD and back-office platform, 1 Core System, or to the client’s own system, through the same signed event feed and link interface.
What is configurable per client
Section titled “What is configurable per client”- Asset catalogue and networks
- Spreads, rounding, quote validity and instant-trade ceiling
- Confirmation depths, hot wallet cap and reconciliation schedule
- Risk thresholds for screening and name matching
- Role matrix and four-eyes approval roles
- Customer-facing statements in English and Thai
- Branding and display name
Every setting change is logged — see Audit trail.
Integration interfaces
Section titled “Integration interfaces”| Interface | Direction | Purpose |
|---|---|---|
| Event feed | Trading Core → back office | Trades, reversals, deposits, withdrawals, transfers, hedge fills, sweeps, new addresses |
| Customer link | Back office → Trading Core | Customer binding, limits, account restrictions, transfer verdicts |
| Day open / close | Both | Brought-forward positions and completeness files, sealed with SHA-256 |
| Wallet signer | Trading Core → wallet provider | Signing and broadcast of approved transfers |
| Screening | Trading Core → analytics provider | Wallet risk screening |
| Travel Rule | Both | IVMS101 messages with counterparty providers |
| Regulatory reporting | Trading Core → regulator | Electronic report submission over mutual TLS |
| Market data | Provider → Trading Core | Price inputs for the composite mid |
With 1 Core System as the back office, the event feed and customer link meet CDD Core’s message API — see API and Integrations.