A white-label platform can present a familiar trading interface under a broker’s brand. It does not settle who serves the client, manages the infrastructure or meets local obligations.
Follow the evidence
Trace how the event could reach markets, then inspect a competing explanation.
Compare explanations
Switch lenses to see what each account explains—and what remains uncertain.
Ask about uptime measurement, maintenance windows, backups, incident communication, version updates and the steps for restoring service. Test how the system behaves when an upstream connection or an internal integration fails. Review the full cost model, including licences, user or account limits, integrations and exit assistance. Confirm whether logs and client data can be exported in a usable format if the relationship ends.
Ask about uptime measurement, maintenance windows, backups, incident communication, version updates and the steps for restoring service. Test how the system behaves when an upstream connection or an internal integration fails. Review the full cost model, including licences, user or account limits, integrations and exit assistance. Confirm whether logs and client data can be exported in a usable format if the relationship ends.
Who is responsible for onboarding, client complaints, execution records and financial promotions? Which permissions are granted by the vendor, and which remain with the brokerage? Get each responsibility into the contract and operating procedure. Validate current licensing and local requirements with qualified advisers and the relevant regulator. A branded platform, vendor assurance or technical demonstration does not amount to regulatory approval.
Map the product from client login to order record
The trading terminal is connected to server infrastructure, instruments, pricing, risk controls and reporting. A branded front end may depend on separate agreements for hosting, market data, bridges or customer support.
Identify every legal entity in the chain and the service each one supplies. A platform brand alone does not prove who operates an account or how a client order is processed.
Compare service levels against a realistic operating day
Ask about uptime measurement, maintenance windows, backups, incident communication, version updates and the steps for restoring service. Test how the system behaves when an upstream connection or an internal integration fails.
Review the full cost model, including licences, user or account limits, integrations and exit assistance. Confirm whether logs and client data can be exported in a usable format if the relationship ends.
Check permissions, authority and regulatory fit independently
Who is responsible for onboarding, client complaints, execution records and financial promotions? Which permissions are granted by the vendor, and which remain with the brokerage? Get each responsibility into the contract and operating procedure.
Validate current licensing and local requirements with qualified advisers and the relevant regulator. A branded platform, vendor assurance or technical demonstration does not amount to regulatory approval.