Account-type and group policy
Brokers can configure account types and validated MT5 group routes.
Built and tested
MT5 Manager API integration
Connect broker operations to MT5 through a controlled boundary.
Use broker-approved platform data for CRM servicing, partner attribution, commissions, account routing and engagement progress under explicit deployment controls.
MT5 integration
SettingsSearch settings
TS
Account type to MT5 group mapping
Broker-approved| Account type | Individual IB override |
|---|---|
| Standard | Not set |
| Pro | real\NL\vp-pro |
| Raw spread | Not set |
| Demo | Not set |
Route resolution order
Deterministic- 1 · Individual IB overrideChecked first
- 2 · General IB groupIf partner attributed
- 3 · Account-type groupDefault route
- Group catalogueRead from Manager API
- Free-text group namesNot permitted
Manager API boundary
Per-tenant adapter- Client and account snapshotsRead
- Deal volume for challengesRead
- Group catalogueRead
- Account creationControlled write
- Order placementOut of scope
- Margin and risk decisionsOut of scope
Integration architecture
What the adapter actually does.
- Tenant-pinned adapters
- Explicit broker-host configuration, isolated per tenant.
- Read-only snapshots and pumps
- Clients, accounts, groups, deals and balance operations required by CRM workflows.
- Durable event transport
- Replay-safe, with idempotent projection boundaries.
- Exact volume normalisation
- Deal volume normalised for lots-traded trader and attributed-IB challenge progress.
- Live group catalogue
- Back Office selects read the group catalogue so staff cannot invent MT5 group names.
- Route resolution
- Individual IB override, then general IB group, then the standard account-type group.
- Authoritative attribution
- Partner attribution comes from CRM records, never from trader-supplied input.
Controlled account opening
Status, stated plainly.
Route resolution
The CRM resolves standard, general-IB and individual-IB destinations deterministically.
Built and tested
Manager UserAdd
Account creation is enabled through a separately reviewed, idempotent Manager API workflow.
Pilot dependency
Credential delivery
Credential issue and delivery require an approved broker-specific security design.
Pilot dependency
Broker staging evidence
Account-opening claims require signed staging proof for that deployment.
Pilot dependency
Non-negotiable boundary. HX Nexus does not manage trading execution, dealer decisions, leverage, margin, liquidation, hedging or exposure. These are not product capabilities.
Bring your MT5 topology.
We will walk the adapter, the data classes and the deployment ceremony with your technical team.