Inventory both sides of the connection
Record the platform interface, bridge version, provider endpoint and the rights available to configure each side. Identify symbol names, quantity units, trading sessions and supported order actions. A mismatch can remain hidden until a less common instrument or rejection path is exercised.
Market data and execution may use different paths or contracts. Map them separately, even if the same supplier appears in both diagrams. Technology connectivity does not establish liquidity terms or the brokerage’s execution policy.
Scope the integration deliverables
| Deliverable | Minimum useful content |
|---|---|
| Mapping register | Platform symbols, destination identifiers, units and exceptions |
| Workflow matrix | Supported instructions, final states and external prerequisites |
| Operating view | Connection health, event tracing and escalation ownership |
| Reconciliation method | How platform and external records are compared |
| Recovery runbook | Interruption handling, outstanding-state review and authorised restart steps |
Define which configuration changes are client-operated and which require a provider request. Include the support route for failures that sit between two suppliers.
Review acceptance through more than a successful order
Illustrative bridge test: a supported instrument is routed successfully, while a deliberately unmapped test identifier is rejected. The reviewer checks that both outcomes can be traced and that the rejection cannot silently become an unintended default route.
Add an agreed connection-interruption test in a safe environment and review unresolved instructions before normal operation resumes. Your acceptance record should state the tested interfaces, configuration baseline and open limitations. For platform-specific work, review the MT4 connection scope or MT5 connection scope.