Outsourced Dealing Desk for MT4 Brokers

MT4 Manager API Integration

Access is provisioned as a read-only Manager API account, with server reports used to fill the gaps the API leaves. From there we build a working picture of your book: open trades and pending orders, account and group assignments, leverage and margin settings, security group configuration, swap and session schedules. Nothing we hold allows an order to be placed, a position to be closed or a balance to be touched. Because the MT4 Manager API returns less structured history than MT5, we snapshot state on a fixed cycle and keep our own record of what the book looked like at each point in the session. That record is what makes a dispute about a fill, a stop-out or a hedge answerable weeks later.

Legacy Server Considerations

MT4 servers accumulate history. Symbol sets get edited for a campaign and never reviewed, plugins are installed by a vendor who has since moved on, staff accounts keep leverage nobody would grant today. Our first pass documents what is actually on the server rather than what the last handover said, then keeps that document current. We also treat plugin behaviour as part of the risk surface: anything that intercepts or modifies order flow is named, described and monitored for effect on execution.

• Plugin inventory and effect on order flow
• Symbol, security group and swap configuration review
• Leverage and account group anomaly checks
• Fixed-cycle state snapshots for audit

Exposure Monitoring on MT4

MT4 has no netting model of its own, so exposure has to be assembled rather than read off a screen. Verix aggregates positions across symbols, groups and books and compares the result to the limits in your policy, which means our operators see one-sided flow, concentration in a single instrument and margin pressure while it is still manageable. We pay particular attention to instruments where MT4 pricing and the bridge feed can diverge, and to accounts whose position size no longer matches the equity behind it.

Routing, Hedging and Bridge Management

Hedging on MT4 usually runs through a bridge layer that has been extended over years. We check that routing rules, symbol mapping and markup profiles still match the documented intent, and that every symbol you believe is hedged actually maps to a provider. Unmapped or misspelled symbols are one of the most common and most expensive findings on a legacy MT4 stack, because the flow looks covered in the reporting and is not covered at all in the market.

• A-book hedge confirmation through the bridge
• B-book residual against agreed ceilings
• Symbol mapping and unmapped instrument detection
• LP fill ratio and rejection monitoring

Running MT4 and MT5 in Parallel

Brokers migrating to MT5 rarely switch in one move; the two servers run side by side for months or years, often with the same clients trading both. Split coverage is where limits get missed, because each platform looks acceptable on its own while the combined book is not. We monitor both servers as a single exposure picture, keep one escalation matrix, and deliver one report. If you are consolidating onto MT5, our outsourced dealing desk for MT5 brokers is the sister service and the same operators cover both.

24/5 Coverage, Reporting and Pricing

Coverage runs from the Asian open to the US close in rotating shifts, with written handovers and playbooks for news windows, rollover and platform incidents. You receive a written dealing report every trading day and a weekly operations review. Engagements begin with a fixed-scope Health Check at $1,000; ongoing coverage is a monthly retainer scoped to your symbol and group count, bridge and LP setup, and the overnight or weekend cover you need, agreed upfront and reviewed quarterly.

Frequently Asked Questions