Native MT5 gateway
Streams prices into MetaTrader 5 and sends dealer requests into the AFX execution path without a separate client terminal.
Execution infrastructure for brokers
One execution layer.Every route under control.
Connect MetaTrader 5, route intelligently across liquidity and expose standard FIX 4.4 sessions through one operating stack.
Reference execution flowroute ready
Ingress
GatewayMT5
ProtocolFIX 4.4
Decision
AFXSmart order routerpolicy · depth · state
Liquidity
Route 01LP direct
Route 02LP depth
Route NLP configured
Native MT5 gatewayDirect + aggregate routingFIX 4.4 pricing + tradingOperational route evidence
The AFX Flow stack
Three surfaces. One execution core.
Use the whole stack or integrate at the boundary that fits your operation. Each service is built around the same route, execution and delivery state.
01 / Bridge
Put AFX beside yourMetaTrader 5 server.
A native gateway moves market data and dealer requests between MT5 and the AFX execution fabric. Your platform keeps the MetaTrader workflow; AFX handles the route beyond it.
Controlled symbol mapping
Use explicit source-to-MT5 mappings or automatically register symbols as they arrive from the configured market-data source.
Delivery safeguards
Execution acknowledgements, duplicate-execution suppression and duplicate-close protection keep MT5 state aligned with the route.
02 / Smart order routing
Decide the route.Keep the evidence.
Route directly to a named provider or aggregate available depth across multiple LPs. Every path is expressed as execution state, not a black box.
Direct
Pin an order flow to a configured liquidity provider when the route is predetermined.
Aggregate
Use available depth to split eligible orders across liquidity providers and combine the resulting fills.
Control
Apply account kill switches and routing overrides before an order leaves the execution boundary.
Recover
Track partial fills, timeouts, retry paths and MT5 delivery acknowledgements as explicit execution states.
Order intentPolicy + depthLP child ordersAggregated resultMT5 delivery
03 / FIX services
A standard protocol.A controlled boundary.
Give an entitled client separate pricing and trading sessions over FIX 4.4. AFX handles session rules, market-data delivery, order entry and account snapshots at the edge of the same execution stack.
SurfaceCapabilityBehaviour
ProtocolFIX 4.4
Standard fields; no custom client-supplied tags
PricingSecurity list + market data
Snapshot requests, streaming subscriptions and cancellation
TradingOrders + account state
Market orders, collateral snapshots and open positions
AccessProvisioned sessions
Separate credentials, symbol entitlements and source-IP allowlists
35=x35=V35=D35=BB35=AN35=8
Built to be operated
The route is only useful if your team can explain it.
Route evidence
Retain the route decision, LP children, execution outcomes and delivery state needed to explain how an order moved.
Execution controls
Manage direct or aggregate behaviour, per-flow overrides and account kill switches from the operating layer.
Failure visibility
Surface rejects, partial fills, timeouts and delivery gaps as operational states rather than hidden edge cases.
RECEIVEDorder intent
DECIDEDaggregate route
EXECUTEDmulti-LP result
DELIVEREDMT5 acknowledged
Integration path
Start with the boundary you need.
- 01Map the flow
Define platform, account, symbol and liquidity-provider boundaries.
- 02Provision access
Configure the MT5 gateway or FIX credentials, entitlements and network access.
- 03Prove the route
Exercise pricing, rejects, fills, timeouts and delivery acknowledgements before production.
afx Flow