A broker without a client area is running a manual back office whether it intends to or not. Every
account opening, every leverage change, every withdrawal request arrives as a message that a person
has to read, verify against a document folder, and re-enter into the trading server. That model
survives the first hundred clients and breaks somewhere shortly after.
The conventional answer is to buy a full CRM in order to get the portal that comes attached to it.
The two components on this page separate those concerns. The cabinet is the client-facing surface
of the platform's client-management layer; where a broker already runs a CRM of its own, the same
cabinet connects to that instead and leaves identity where it is.
ComponentTrader Cabinet
A white-label client portal on the broker's own domain. It covers registration and onboarding,
KYC document collection and the verification workflow behind it, account management — opening
live and demo accounts, leverage changes, password resets — deposits, withdrawals and internal
transfers between a client's own accounts, trading history and statements, and single sign-on
into the web terminal.
The structural idea is one identity holding many accounts. The client registers once; live
accounts, demo accounts, an investment account and a challenge account all hang off that single
record, which makes a second account a two-click operation instead of a second onboarding. Single
sign-on carries the same session into the terminal. KYC state lives on the identity too, so the
portal gates funding, trading and withdrawals on a verification level rather than on a support
agent remembering to check.
Deployment comes in two shapes. Where the broker has no system of its own, the cabinet runs on the
platform's client-management layer as it ships. Where a CRM is already in place, the cabinet
integrates as a service layer instead: client identity and KYC status remain in the existing
system as the single source of truth, synchronised both ways, so there is no second copy of the
client to reconcile.
What it solves
- Removes the "buy an entire CRM just to get a client portal" problem
- Self-service on routine operations, which is where the bulk of support ticket volume comes from
- Compliant onboarding by construction — verification gates funding and withdrawal, automatically
- One branded entry point tying terminal, payments and services together on the broker's domain
ComponentIB & Partner Program
A multi-level introducing-broker module. Partners onboard through the same portal, receive
referral links and tracked sign-up pages, and are paid under a commission structure the broker
defines: per-lot rebates, revenue share, fixed acquisition payments, or a combination,
differentiated by symbol group and account type. Commission is calculated on every trade in real
time. The partner cabinet shows referred clients, volume, accrued and paid commission, and holds
the marketing materials the broker publishes. Payouts are managed in the same place.
Attribution happens at registration: the referral link binds the new client to the partner on the
client identity, before any account exists. Accrual then happens per deal, computed from the
server's trade record as the deal is written, at the rate applying to that partner and symbol
group, and each accrual keeps the deal reference it came from. That is the difference between a
statement a broker can defend and a monthly total nobody can explain: when a partner disputes a
figure, the answer is a list of deals, not a recalculation.
The structure is multi-level by design. A master partner introduces sub-partners, and a
configurable share of what each level earns passes up the chain, applied at accrual time rather
than reconstructed later from reports. Depth, rates and eligibility are set per programme, so
different terms for a regional master IB and for an affiliate network do not mean two systems.
What it solves
- Makes the dominant acquisition channel in FX and CFD manageable at scale rather than by hand
- Replaces spreadsheet rebate calculation, which is slow, error-prone and permanently disputed
- Real-time, per-deal transparency, which is what keeps productive partners loyal
- Multi-level structures let master partners build their own sub-networks under the broker's brand
How it ships. A web application served on the broker's domain under the broker's brand,
with the partner cabinet running on the same identity and the same session. It talks to the MT5
server for account operations and trade data, to the payment layer for deposits, withdrawals and
partner payouts, and to the notification gateway for verification, money and commission events.
The client-management layer behind it is either the platform's own or the broker's existing CRM,
chosen at deployment.
What has to be right
A client area is the only part of the platform a client sees before they trade, and the only part
that touches money without a dealer in the loop. These are the points where implementations fail.
One identity, many accounts. Modelling the trading account as the identity is the mistake
that makes everything downstream harder: a client with four accounts becomes four clients, KYC is
duplicated, and partner attribution splits. The identity has to sit above the accounts from the
start.
Verification gates are enforced server-side. Hiding a withdrawal button from an unverified
client is presentation. The check is applied where the operation executes, so a request submitted
any other way is rejected on the same rule.
Withdrawals need a maker-checker path. A withdrawal is an irreversible outbound payment. It
passes through an approval workflow with requester and approver recorded, and returns to the origin
of the funds where the licence requires it. The audit trail is the product.
Commission arithmetic must be reproducible. Accruals are written per deal and never
recalculated in bulk at month end. A rate change applies from a point in time and does not restate
history. Self-referral and circular partner structures are blocked at attribution, because they are
the standard way a rebate programme is drained.