A clear MT5 White Label brief connects the trading platform, client journey and operating responsibilities. Use this checklist to define what must be demonstrated before you accept a configuration.
Start with the business workflow
Write down the intended trading instruments, client interfaces, languages and account structure. Separate launch requirements from later improvements. A small set of complete scenarios is more useful than a long feature list with no acceptance criteria.
The official MetaQuotes platform documentation describes desktop, web and mobile access, distributed server architecture and APIs with distinct purposes. Your project still needs an agreed scope: which interfaces, access rights and connections are included in the proposed MT5 White Label configuration?
Give every requirement an owner
For each component, record who supplies it, who configures it and who accepts the result. The same company may own several tasks, but those tasks should remain explicit. This helps expose gaps between a trading terminal, the client portal and the surrounding infrastructure.
| Requirement | Owner to identify | Evidence to request |
|---|---|---|
| Brand and client access | Branding and platform configuration owner | Approved identity assets, interface list and access walkthrough |
| Account operations | CRM and account workflow owner | Account journey, roles and status changes |
| Data and connectivity | Feed, bridge and provider owners | Symbol mapping and the agreed data/order scenarios |
| Operating environment | Hosting and server operations owner | Access, monitoring, backup and recovery procedures |
| Acceptance and handover | Named project approver | Test record, exceptions and handover checklist |
Map the connections separately
List the responsibilities of the CRM and client portal, payment workflow, market-data source and FIX bridge. A price feed and an order connection serve different purposes. Ask which system owns each account identifier and operational status, and how mismatches will be investigated.
For an existing MT4 environment, inventory the tools and processes you need to retain. Review platform differences against that inventory. The MT4 White Label page remains a separate starting point for an MT4 brief.
Ask for evidence from complete scenarios
- Client access: demonstrate the agreed registration, account access and interface journey.
- Trading workflow: inspect a supported order scenario and the corresponding account records.
- Team permissions: test an allowed action and an action the role should not be able to perform.
- Connected operations: follow one CRM or payment-related workflow through its status changes.
- Operational handover: identify the logs, contacts and procedures used when a connection or service needs attention.
Record the environment, expected outcome, observed outcome and unresolved questions for each scenario. Treat an exception as a follow-up item with an owner; avoid accepting a feature solely because it appears on a presentation slide.
Finish with an operating record
Confirm licensing and package boundaries, administrator access, configuration ownership, support arrangements and the process for future changes. Review trading server management and brokerage launch planning alongside the platform requirements.
You can prepare a shortlist with the brokerage blueprint configurator. For the broader product introduction, read MT5 White Label: Build Your Brokerage Brand.
Reference material
Platform-level reference: MetaQuotes — MetaTrader 5 for brokers. The checklist above is a TradeToolsFX planning framework; the exact deliverables are established in your project scope.
Bring a checklist to the conversation.
Share your preferred platform, interfaces, required connections and acceptance scenarios.
Discuss your MT5 launch on Telegram ↗