Forex bridge & gateway solutions.
The bridge is where liquidity becomes tradable: FIX sessions, symbol mapping, markup and routing between your trading platform and your LPs. Gateways connect the same platform to payments, CRM and the rest of the business.
What happens inside the bridge.
Select a scenario to see which bridge stages it passes through, the state of each LP session and the FIX messages on the wire.
35=V MarketDataRequest35=W / 35=X MarketDataQuote path
- 1Each LP streams prices on its own FIX session
- 2LP symbols are mapped to platform symbols and digits
- 3Group and session markup is applied
- 4The resulting quote is published to the platform
Order path
- 1A client order leaves the platform
- 2Routing rules decide A-book, B-book or partial cover
- 3A-book flow is sent to the selected LP as a FIX order
- 4The execution report returns the fill to the client's position
Reject & re-route
- 1The first LP rejects the order or times out
- 2Reject handling applies the configured policy
- 3The order is re-sent to the next LP in priority
- 4The outcome and reason are logged for execution review
Session failover
- 1Heartbeats from one LP session stop arriving
- 2The session is marked down and removed from routing
- 3Pricing and orders continue on the remaining sessions
- 4On reconnect, sequence numbers are reconciled before re-admission
Reference topology using standard FIX 4.4 message types. Bridge vendor, LP count and reject policy are configured per deployment.
Bridge and gateway are different jobs.
Bridge
Connects the trading platform to liquidity. It holds the FIX sessions, maps symbols, applies markup and decides where each order is executed.
Gateway
Connects the platform and back office to everything else — PSPs, CRM, KYC, reporting and proprietary systems — over REST, WebSocket or custom adapters.
Where they meet
Liquidity relationships decide what pricing is available. The bridge decides what clients receive and how it is executed. Gateways keep the rest of the business in sync with it.
What we configure, and where it lives.
Every item below is explicit configuration, documented per deployment — not a vendor default.
| Area | What is configured | Layer |
|---|---|---|
| FIX sessions | Session credentials, heartbeat interval, reconnect and sequence-number policy per LP | Bridge |
| Symbol mapping | LP symbol, digits, contract size and trading hours mapped to platform symbols | Bridge |
| Markup & spread | Markup by group, symbol and session; minimum spread and rounding | Bridge |
| Routing rules | A-book, B-book or hybrid by group, symbol, volume or account attribute | Bridge |
| Reject handling | Re-route, re-quote or reject; LP priority order and timeouts | Bridge |
| Payments & CRM | PSP callbacks, balance posting and account events between back office and platform | Gateway |
| Monitoring | Session status, reject rates, latency and fill reporting with alerting | Both |
How a bridge project runs.
Topology design
Platforms, LP sessions, protocols, hosting location and failover order documented before build.
Build & configuration
Bridge and gateway configured with every LP, platform and third-party connection in scope.
Testing
Session, reject and failover scenarios tested on a staging server; latency measured from the hosting location.
Production & monitoring
Cutover with session monitoring and alerting in place, within the agreed support scope.
Protocols
- FIX 4.2 / 4.4
- Standard for LP pricing and order sessions.
- REST & WebSocket
- For PSPs, CRM, KYC and reporting integrations.
- Custom adapters
- For proprietary or legacy systems without a standard API.
Execution connectivity is usually one layer inside turnkey brokerage infrastructure, scoped together with platform, liquidity and risk.
Bridge & gateway — common questions.
What is a forex bridge?
Software that connects a trading platform such as MT4, MT5 or cTrader to one or more liquidity providers. It manages FIX sessions, maps symbols, applies markup and routes orders according to the broker's execution model.
What is the difference between a bridge and a gateway?
A bridge handles platform-to-liquidity execution. A gateway connects the platform and back office to other systems such as payment providers, CRM and KYC tools.
Which bridges do you work with?
We work with established bridge vendors such as oneZero, PrimeXM, Centroid and others, or with a bridge you already run. Selection depends on platform, LP panel and execution model.
What happens when an LP session drops?
The session is marked down and removed from routing; pricing and orders continue on the remaining sessions. On reconnect, sequence numbers are reconciled before the session is re-admitted.
Where should the bridge be hosted?
Close to the trading server and the LPs' pricing venues — typically in the same data centre or a nearby one — so latency between platform, bridge and LP stays low.
Review your execution path with us.
Explore Execution Research
Operator-level analysis supporting bridge & gateway.