White label
The terminal traders already know, under your name
In markets where traders arrive with a platform preference already formed, meeting that preference is cheaper than arguing with it. This puts the terminal they expect inside a stack that carries your brand everywhere else.
Signup, verification, funding and withdrawal on your domain.
The console your desk works in, carrying your identity.
Confirmations and reports in your format and your name.
Every email the trader receives, sent from you.
See it live
The integration surface, documented not implied
FIX sessions, REST endpoints and webhooks listed with real request and response samples, for the engineer who has to actually wire it up.
What your desk gets
Six administration surfaces, in one console
The terminal is what the trader sees. This is what your team spends its day in, and it covers the third-party platform alongside everything else you run.
Accounts and groups
Create, segment and set conditions per client group without a support ticket.
Exposure view
What the book holds right now, aggregated across the platform and your other products.
Trade history
Every order, fill and adjustment, filterable and exportable.
Reporting
The reports your regulator and your finance team both need, from one place.
Instruments and margin
Symbol lists, spreads, swaps and leverage set per group.
Risk controls
Limits and interventions applied before an order reaches the book.
How it goes live
Four stages, with certification before exposure
Scope
Which platform, which markets, and what your traders expect to see when they arrive.
Integrate
Platform connected into the client area, payments and back office against one account model.
Certify
Sessions tested end to end before anything is exposed to a client, not after.
Brand and launch
Your identity applied across every surface, then a staged cutover.
FAQ
Third-party platform white label: common questions
6 short answers to what teams ask before a demo.
The platform vendor does, and that relationship is theirs to grant. We handle the integration, the configuration and everything around the terminal — the client area, payments, back office and reporting — under your brand.
Familiarity. If your target traders arrive already knowing a platform, asking them to learn a new one is a real acquisition cost. In markets where traders are new to trading entirely, that cost is close to zero and the calculation changes.
Yes, and many firms do. One client record and one back office sit behind both front ends, so traders pick the terminal they prefer without doubling your operations work.
Branding and configuration within what the platform exposes. Anything deeper is a request to its vendor rather than to us, which is the honest limit of any third-party white label.
We do, on the vendor's release schedule rather than ours. That is one of the practical reasons to have somebody else administer it: platform updates arrive whether you were ready or not.
Yes. Because the account model, payments and back office are shared, changing the front end is a migration of traders rather than a rebuild of the brokerage.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistWhich platform do your traders ask for?
If they do not ask for one, our own terminal is usually the better answer. That is worth establishing before anything else.