Align the platform and external instrument definitions
| Decision | What must be agreed |
|---|---|
| Instrument match | Source identifiers, contract conditions and the intended platform symbol. |
| Route | Destination selection and the party allowed to change it. |
| Outcome records | Available identifiers and the method used to reconcile requests and responses. |
| Exceptions | Treatment of rejection, interruption and an uncertain result. |
Compare the actual instrument and connection scope with the external provider. Do not treat a similar symbol name as proof that the contracts or supported actions are equivalent.
Demonstrate outcomes before extending the connection
Use the approved test arrangement to trace representative flows. Include a normal result, an explicit rejection and a connection interruption. Document which system owns each acknowledgement and where an operator finds the evidence needed for investigation.
For an uncertain result, establish the supported lookup or reconciliation procedure before resubmission. Automatic retries or route changes need to be evaluated with the connector and destination providers; they are not universal features of an MT5 liquidity integration.
Keep commercial and operational boundaries visible
Identify the contracts and permissions required for the platform, connector and external service. Record which provider configures the connection, which team monitors it and who can authorise a production route change. A technical project should not imply that external commercial terms are bundled unless the proposal says so explicitly.
The handover should include an instrument map, connection diagram, test record, monitoring signals and escalation process. Use the MT5 bridge integration brief for the underlying connector scope and the MT5 deployment page for the wider operating environment.