MT5 White Label Launch Checklist

What this checklist helps you decide

An MT5 White Label project connects platform configuration with the surrounding operating stack. A proposal may cover only part of that stack. Use the checklist to identify missing decisions, supplier dependencies and the evidence you want to see before handover.

For a new brokerage, work from requirements to a testable scope. For an existing broker, include the current environment and continuity requirements. Confirm commercial availability and applicable rights with the suppliers; this checklist does not establish a licence, approval or a promised deployment time.

12 implementation workstreams to review

Tick an item when you have reviewed its decisions and supporting evidence. Entries are processed in this browser and are not stored between visits.

0 of 12 planning items reviewedThis count is a worksheet aid; it is not a go-live approval.

1. Define the scope and dependenciesRecord instruments, account currencies, intended markets, integrations and existing systems. Identify who supplies each component and which approvals or agreements are prerequisites.Evidence to retain: Signed scope, supplier contacts and a dependency list.2. Confirm the platform arrangementIdentify the contracting parties, permitted branding, access and responsibilities. Obtain written confirmation that the proposed arrangement can support your use case before making a launch commitment.Evidence to retain: Commercial scope and rights confirmed by the relevant suppliers.3. Design account groups and accessSpecify demo and live groups, account currencies, permissions, leverage rules and who can approve changes. Separate ordinary operational access from administrative access.Evidence to retain: Approved group matrix and named access owners.4. Approve instrument specificationsDocument symbols, mapping, contract size, digits, trading sessions, commissions, swaps and margin settings for the selected instruments. Reconcile platform settings with the execution connection.Evidence to retain: Instrument sheet reviewed by the responsible operations team.5. Agree the client experienceList the approved brand assets, domains, available client access methods and support contacts. Confirm what the supplier can deliver instead of assuming every client or application can be rebranded.Evidence to retain: Approved branding scope and client access instructions.6. Map CRM and account workflowsDefine identifiers and states shared by the CRM, client portal and platform. Cover account creation, demo-to-live transitions, permission checks and error handling. Identify separate verification and payment dependencies.Evidence to retain: Workflow map with test cases and ownership of failed requests.7. Map execution connectivityList bridges or gateways, instruments, quantity mapping, execution routes and available test environments. Specify what should happen during disconnects and rejected requests.Evidence to retain: Connection diagram, mapping sheet and operational escalation path.8. Reconcile balances and reportingDefine which system owns each record and how account balances, transactions, fills and reports are checked. For a migration, specify the cutover boundary and reconciliation before reopening activity.Evidence to retain: Reconciliation procedure and exception log.9. Run acceptance testsTest account creation, quotes, order processing, charges, reports, reconnect behaviour and recovery in the agreed environment. Record expected and observed results; assign an owner to every unresolved issue.Evidence to retain: Test evidence with explicit pass/fail results and issue owners.10. Review monitoring and recoveryIdentify alerts, backup ownership, restore procedures and recovery dependencies. Review the agreed support coverage and escalation process. A backup plan needs a tested restore procedure.Evidence to retain: Monitoring contacts and a recorded recovery exercise.11. Prepare operational handoverDocument routine tasks, access changes, maintenance windows and approved configuration changes. Confirm who supports the CRM, platform, execution connection and infrastructure after handover.Evidence to retain: Operating runbook and a responsibility matrix.12. Make the release decisionReview unresolved issues and prerequisites with the responsible owners. Agree release timing, communications and rollback criteria. Completing this worksheet is not regulatory approval or a substitute for acceptance sign-off.Evidence to retain: Release decision, rollback plan and sign-off by the responsible owners.

Acceptance tests to agree before configuration starts

Agree representative scenarios and expected outcomes with the teams responsible for the selected systems. Record the environment, configuration version, result and evidence for every test.

Scenario	What to inspect	Evidence
Account creation	CRM and platform identifiers, intended group, currency and permissions.	Matching records and the account request result.
Instrument configuration	Symbols, contract size, session settings and the agreed charge configuration.	Approved specification and a configuration export.
Execution request	Routing, quantity mapping, fill or rejection handling and reporting.	Correlated request, execution and platform records.
Disconnect and reconnect	Expected degraded behaviour, alerts and reconciliation after reconnection.	Alert timeline and resolved exception records.
Recovery exercise	Restore procedure, required access and checks before activity resumes.	Restore record and recovery verification.

Use a test environment and the scope agreed with your suppliers. These examples describe review work; they do not promise that a particular integration supports every scenario.

What determines an MT5 White Label launch timeline?

Timing depends on supplier onboarding, the confirmed platform arrangement, branding, instrument approval, test access and integration work. Existing connectors and approved specifications can reduce implementation work; custom workflows and migration introduce further dependencies.

Ask for milestones with owners and prerequisites: scope approval, configuration, connectivity tests, acceptance, handover and release. A calendar date without these dependencies is difficult to assess. Use the provider evaluation checklist to compare responsibilities and the cost breakdown to identify recurring charges.

For an established environment, include a separate MT4 to MT5 migration plan with reconciliation, client communication and rollback arrangements.

Prepare a useful implementation enquiry

Send your platform preference, instruments, account currencies, CRM, execution dependencies, existing environment and desired timing. Identify the checklist items that are already defined and those needing clarification.

Review the MT5 White Label project scope, prepare a quote brief and contact us on WhatsApp or Telegram to discuss the required work.

What this checklist helps you decide

12 implementation workstreams to review

Acceptance tests to agree before configuration starts

What determines an MT5 White Label launch timeline?

Prepare a useful implementation enquiry