Your trading platforms. Your rules.
Trading is part of TradeCore's BrokerIQ CRM core for FX/CFD brokers: it opens, provisions and governs client accounts across 8 trading platforms, with every account's trading group and leverage resolved from rules the broker authors.
100+ brokerages run on TradeCore, including MultiBank Group, AvaTrade, IC Markets, FP Markets and Trade Nation.
Why is trading part of the CRM core and not a module?
BrokerIQ is TradeCore's modular CRM and back-office product line for FX/CFD brokers, and trade data is what the rest of it runs on. IB commission, cashback, bonus conversion, prop challenges and automation triggers all read closed trades. Trading opens accounts on your platform, or mirrors the platform you already run.
- BrokerIQ opens and manages the accounts on your trading platform: New accounts are provisioned on the platform from the rules you author. Leverage, account type, password and archive changes are pushed to the platform. Every fact the platform sends back lands in the append-only trade ledger.
- BrokerIQ mirrors the trading platform you already run: Clients, trading accounts and closed trades are mirrored from your platform, with nothing migrated. IB commission and cashback work on real trade data from day one. You author the same catalogs and rules — backends, groups, leverages, account types, binding and availability. Mirrored accounts are marked as mirrored, and the credential stays with you.
- MetaTrader 4
- MetaTrader 5
- cTrader
- DXtrade
- MatchTrader
- TradeLocker
- ScaleTrade
- TraderEvolution
- TradeCore Wallet
The BrokerIQ CRM core
Every account governed here. Every fact the platform sends kept in an append-only ledger.
Who decides a client’s trading group and leverage?
A binding rule does, and you write it. It takes a condition on the client, a cell of backend plus optional currency and account type, and outputs the trading group, the leverage or both. Rules are priority-ordered, and a priority-zero Default cannot be deleted.
1 · A client opens an account
Availability rules
Allow or deny account types by country of residence, introducing broker, source campaign or referring client.
- Client picksThe client chooses from what the rules left standing.
- Auto, highest priorityThe winning account type is applied without asking.
- Operator onlyNobody self-serves — your team sets it.
2 · Binding rules, highest priority first
If Country of residence is one of the EEA list
On MT5 Live · EUR
If Introducing broker is set
On MT5 Live
If Everyone the rules above did not match
On MT5 Live
3 · The account that gets opened
- Trading group
- Leverage
The rule that produced an account’s group and leverage is stamped on it, so the answer can be read back months later.
- Same-priority overlap: 3 active rules share priority 0 on MT5 Live — the resolver breaks the tie by creation order.
- Missing Default: No active Default supplies leverage for MT5 Live — a new account on this cell would fail to resolve a leverage.
Warnings, not errors. The rule still saves — the platform tells you what it will do rather than refusing and leaving you guessing.
Six screens hold the whole trading configuration, and a broker fills them in without a developer
Backends
Which platform servers you are connected to.
One row per platform server, in demo or live mode · Credential fields declared by the platform itself · Maximum accounts per client · Health status and circuit state · A starting demo credit on demo backends
Trading groups
Where on the platform an account is actually placed.
Named per backend, each carrying its currency · Kept internal — clients never see a group name · Deactivation shows its impact first
Leverages
What leverage you offer, and on which platforms.
Labelled values on the backends you choose · Your own sort order · Immutable — add the new value and retire the old one
Account types
The product names your clients choose between.
Named by you, bounded by backends, currencies and leverages · Minimum deposit, display order and expiry · Client-pickable and swap-free switches · Hedged, netted or spread betting
Binding rules
Which group and leverage a new account gets.
A condition, a cell, and the group and leverage it outputs · Priority-ordered, with an undeletable Default · Plain-English warnings on every save
Availability rules
Which account types a client may even see.
Allow or deny by country, introducing broker, campaign or referrer · Client picks, highest priority applies, or operator only · Permissive or strict as each brand's default posture
Retiring a group tells you what breaks
Deactivating a trading group or a leverage shows how many binding rules fall out of resolution first, and refuses outright while an active Default still outputs it.
- impact preview
- refuses while a Default outputs it
A rule that lost its output goes back to Draft
Every active rule that pointed at a deactivated group or leverage moves to Draft — out of resolution and flagged for review, never left dangling.
- out of resolution
- flagged for review
- reactivation
Changing the rules doesn't move existing clients
A bulk re-evaluation reports which accounts would now resolve to a different account type and leaves every account alone. Moving one is a decision a person makes.
- bulk re-evaluation
- report only
- a person decides
The rules read the record you already keep. Country of residence, introducing broker, campaign and referrer all sit on the BrokerIQ client record, with attribution captured at signup — so the rule that decides an account’s terms reads the same data your sales and compliance teams work from.
What happens between opening an account and it going live?
Seven states, and you decide which of them needs a person. A backend can hold new accounts until the client reaches a profile state you name, or open them the moment signup completes.
Trading account lifecycle
Pending approval
Parked for a person. Approving resumes provisioning; rejecting archives it, with the reason on the record.
Created
The record exists in the CRM. Nothing has been asked of the platform yet.
Provisioning
The platform is being asked to open the account. Retries are automatic.
Active
Live on the platform and trading.
Disabled
Switched off by an operator. Reversible.
Error
The retries are exhausted. An operator can retry or cancel the provision from the CRM.
Archived
Terminal. The record stays; the account does not come back.
Created to Provisioning to Active is the happy path. Approval is inserted ahead of provisioning when you ask for it. Active and Disabled go both ways. Archived is terminal.
You choose when an account goes live
A backend can hold new accounts until the client reaches a profile state you name, or open them the moment signup completes. Point the trigger at a state that does not exist and it becomes a kill switch: accounts pile up visibly instead of going live.
An automation can open the account — or park it
Creating a trading account and holding one for approval are both actions in the automation builder, so the rule that verifies a client can be the rule that opens their account.
Approval is a decision with a name on it
A held account waits until a person approves or rejects it with a reason. Approving resumes provisioning where it stopped; rejecting archives the account.
The rule that verifies a client can open their account. Creating a trading account and holding one for approval are actions in the Automations & AI rule builder, beside six ready-made trading rules, and each platform connection is registered in TradeCore’s integration layer.
Can my team run a trading account without the platform’s admin panel?
Fourteen actions, each gated on the account’s state and the operator’s permission, and each writing a record that carries the value before and the value after.
- Refresh balanceAnyPull a fresh figure from the platform.
- ApprovePending approvalResume provisioning.
- RejectPending approvalArchive the account, with a reason.
- Change leverageActivePushed to the platform.
- Change account typeActiveRe-resolves the group if the rules say so.
- Change passwordActivePushed to the platform.
- Set read-onlyActiveRecorded with a reason.
- Adjust balanceActivePermission-gated money movement.
- EditActiveEvery field change logged old-to-new.
- DisableActiveReversible.
- EnableDisabledBack to active.
- ArchiveActive or disabledTerminal.
- Retry provisioningProvisioning or errorAsk the platform again.
- Cancel provisioningProvisioning or errorStop asking.
An action an operator is not permitted to take is not shown to them, and an action the account’s state does not allow is not offered.
Leverage changed
Old leverage and new
Account type changed
Old type and new, plus the operator's reason
Trading group changed
Old group and new
Read-only changed
Before and after, plus the reason
Account edited
The field, its old value and its new one
Enabled / disabled / archived
Who did it, and why
Approved / rejected
Who decided, and the reason
Password changed
Where the change came from — back office, portal or reset
Credentials revealed
Who revealed them and in what capacity. Never the password itself
The client’s activity stream
A change made here reaches the platform
Leverage, account type, password and archive changes are pushed to the trading platform. If that platform's circuit breaker is open the work waits and is redelivered — it is not lost, and it is not silently dropped.
Only a password the platform generated can be revealed
Master passwords are encrypted at field level. One a client chose is never echoed back to them, and a mirrored account holds no secret to reveal at all.
The group is yours; the account type is theirs
A trading group name is the broker's own segmentation and stays internal. The account type is the product name, and that is what the client sees.
One audit trail for the account and the client. Every trading-account change lands on the client’s activity stream, credential reveals included; every mutating action in TradeCore is audited, and TradeCore never deletes the record.
How do I know the trade data I bill on is right?
Every fact a trading platform sends lands first in an append-only ledger, one row per fact, payload kept verbatim. Trades and positions are a projection folded from it, so the numbers can always be rebuilt from what the platform actually said.
What just happened
Facts land in the ledger as the platform sends them.
- Facts land in the ledger as the platform sends them.
- The connection drops. Nothing is invented while it is down.
- On reconnect the outage window is re-pulled — every healed row is logged.
- The same deal arrives again and is deduplicated. Nothing changes.
Append-only, payload verbatim
Every fact a trading platform sends lands first in an append-only ledger, one row per fact. Trades and positions are a projection folded from it, so the numbers can always be rebuilt from what the platform actually said.
The same deal twice is one deal
Identical facts are deduplicated at the database. A re-delivery that changes nothing does nothing.
A cancelled trade is kept, not deleted
The row is retained with its money zeroed and its cancellation recorded. Nothing is removed from the history.
A correction announces itself
A corrected trade is published as an amendment naming the fields that changed, rather than being quietly overwritten.
An outage is filled, and every heal is logged
When the connection to a platform drops, the outage window is re-pulled on reconnect and every row that had to be healed is logged. There is no silent healing.
A sweep re-asks anyway
A scheduled sweep re-pulls each account's recent trades and reconciles the difference, whether or not the stream ever dropped.
The platform's own count is checked
Where a platform can answer it, its count for a window is compared with the ledger's, and a mismatch raises a warning.
An early trade is held, not dropped
A trade that arrives before its account exists is held and projected the moment the account is provisioned. A hold that stays unresolved raises an alarm.
What stops a retried transfer from paying twice?
An idempotency probe. Before issuing a balance operation, BrokerIQ searches the trading platform’s own deal history for that leg’s anchor — a hit means the earlier attempt landed, so the leg completes by adopting that deal instead of crediting again.
The transfer is registered
A leg is written before anything is asked of the platform, with its own status.
The platform's own history is searched
BrokerIQ looks for this leg's anchor in the trading platform's deal history first.
Adopted, or issued once
A hit adopts the deal that already landed. A miss issues the balance operation once.
- The leg is retried: The probe finds the earlier attempt's anchor in the platform's own deal history, so the leg completes by adopting that deal. No second credit is issued, and the record says so.
- A reversed leg is re-driven: The leg failed and its wallet side was already reversed. Re-driving it would pay twice, so the platform refuses the re-drive outright.
A retry can't pay twice
Before every balance operation, BrokerIQ searches the trading platform's own deal history for the leg's anchor, so a retried leg adopts the deal that already landed. Re-driving a stuck leg needs a reason, and a leg whose wallet side was already reversed refuses.
- deal-history probe
- re-drive needs a reason
- reversed leg refuses
Withdrawal caps read live
Before a withdrawal is capped, the balance and free margin are pulled fresh from the trading platform. If the platform cannot answer, the request is refused rather than settled against a cached figure.
- fresh balance
- fresh free margin
- no cached figures
Bonus credit and close-out on the same rails
Credit onto and off a trading account moves through the same tracked legs as a wallet transfer. Closing out a negative-equity account — read-only plus closing its open positions — is one recorded operation that cannot fire twice.
- bonus credit legs
- negative-equity close-out
- deduplicated
The wallet on the other end of the leg. TradeCore Payments runs deposits and withdrawals through 100+ PSPs on two linked ledgers, and a deposit can credit a trading account directly.
What can a client do in the portal on their own?
Open their own live and demo accounts, choosing platform, currency, leverage and account type from exactly what your rules left standing for them — then manage those accounts without opening a ticket.
Open a live or demo account
Platform, currency, leverage and account type — from exactly what your rules allow them.
Receive their login details
Delivered as soon as the trading platform provisions the account.
Reveal login and passwords
Master and investor credentials, with the reveal recorded.
Change leverage
Within the bounds their account type permits.
Change password
Propagated to the trading platform.
Rename the account
A nickname of their own.
Open the platform
Straight through to the platform the client trades on.
Archive an account
Closed off by the client, on the record.
Read trading and ledger history
Across every account they hold.
Top up a demo account
Demo balances only.
Who may open what is gated on the client's state
Live accounts and demo accounts have separate eligibility, resolved from the client's profile state — so an unverified client cannot open a live account by finding the button.
The portal is yours, per brand
The client portal is white-label per brand, and each page can be switched off for a brand that does not want it.
Every account in your own app. In TradeCore’s Mobile App, a client sees every live and demo account across the 8 integrated trading platforms on one screen, with balance, equity and margin, and every account links straight to the platform the client trades on.
Trading on every plan
TradeCore's free plan connects one trading platform of the 8, with two trading accounts per client — up to 5 through the free plan's shop at €40 a month each — and trades syncing into the CRM every 30–60 minutes. TradeCore's Core plan adds unlimited trading accounts per client and live trade import. Each further platform is €200 a month, on either plan.
TradeCore's free plan
€0Trades arrive in batches
- One trading platformAny one of the 8: MetaTrader 4, MetaTrader 5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade, TraderEvolution.
- Further platforms at €200 a month eachStackable, with no ceiling.
- Two trading accounts per clientUp to 5 through the free plan's shop, at €40 a month each, bought one at a time.
- Trades sync every 30–60 minutesTrades from the connected platform arrive in the CRM in batches.
- The whole trading layerBinding and availability rules, the seven-state lifecycle, the 14 operator actions, the trade ledger and client self-service in the portal.
Core
€2,500 a month, flatTrades import live
- One trading platform includedChosen from the same 8 platforms.
- Further platforms at €200 a month eachStackable, with no ceiling.
- Unlimited trading accounts per clientA broker can still set a maximum per backend.
- Live trade importTrades arrive from the connected platform as they happen.
- The whole trading layerEverything on the free plan's lane.
Every price on one page. Further trading platforms, seats, brands and payment providers are priced side by side on TradeCore’s pricing page. No per-trader fees, no per-trade fees, no setup fees.
What’s inside Trading
Every part of TradeCore Trading, by area — the platforms, the configuration, the rules, the account lifecycle, the trade data, the money, the client portal and governance.
Platforms
The 8 trading platforms and the Wallet, each server a backend with its own credentials and health.
- 8 trading platforms: MetaTrader 4, MetaTrader 5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade and TraderEvolution
- TradeCore Wallet alongside them, for balances that are held rather than traded
- Custom trading backends supported through the open API
- Multiple servers per platform — demo and live are separate backends with their own credentials
- Credential fields declared by the platform adapter, so a new platform brings its own form
- Secrets are write-only: the platform reports that a credential is configured, never what it is
- Per-backend health status an operator can override, and a circuit state
- Per-brand backend opt-in, so each brand offers its own set
TradeCore Trading — Platforms
The 8 trading platforms and the Wallet, each server a backend with its own credentials and health.
- 8 trading platforms: MetaTrader 4, MetaTrader 5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade and TraderEvolution
- TradeCore Wallet alongside them, for balances that are held rather than traded
- Custom trading backends supported through the open API
- Multiple servers per platform — demo and live are separate backends with their own credentials
- Credential fields declared by the platform adapter, so a new platform brings its own form
- Secrets are write-only: the platform reports that a credential is configured, never what it is
- Per-backend health status an operator can override, and a circuit state
- Per-brand backend opt-in, so each brand offers its own set
TradeCore Trading — Configuration
Six screens — backends, groups, leverages, account types and both rule sets — scoped per brand.
- Six configuration screens: backends, trading groups, leverages, account types, binding rules, availability rules
- Trading groups named per backend, each carrying its currency
- Leverages as labelled values offered on chosen backends, in your own sort order
- A leverage value is immutable — you add the new one and retire the old one, so no provisioned account is silently re-targeted
- Account types you name yourself, bounded by allowed backends, currencies and leverages
- Allowed leverages as an explicit list or a min/max range
- Minimum deposit with its own currency, display order and expiry per account type
- Client-pickable and swap-free switches per account type
- Hedged, netted or spread betting as the platform-technical account type
- Maximum accounts per client, set per backend
- A starting demo credit amount on demo backends
- Draft → Active → Deprecated lifecycle on account types and both rule sets, with reactivation
- Every catalog scoped per brand
TradeCore Trading — Rules
Binding rules that set group and leverage, availability rules that decide what a client may open.
- Binding rules: a condition on the client, a cell of backend plus optional currency and account type, outputting a trading group, a leverage or both
- Priority ordering, with a priority-zero Default that cannot be deleted
- Plain-English warnings on save for same-priority overlap and for a missing Default
- Deactivation impact preview before a group or leverage is retired, and a refusal while an active Default still outputs it
- Rules whose output is deactivated are moved back to Draft automatically
- The rules that produced an account's group and leverage are stamped on the account
- Availability rules: allow or deny account types by country of residence, introducing broker, source campaign or referring client
- Selection mode per rule — client picks, highest priority applies automatically, or operator only
- Permissive or strict as the brand's default posture
- Bulk re-evaluation reports which accounts would resolve differently, and changes none of them
- An operator can open an account the rules would refuse; the bypass records the rules bypassed, the reason and who did it
TradeCore Trading — Account lifecycle
Seven states, an activation trigger per backend, approval with a reason, and fourteen gated operator actions.
- Seven states: created, provisioning, pending approval, active, disabled, error, archived
- Activation held until the client reaches a profile state you name, or immediate on signup completion
- A trigger pointed at a non-existent state works as a deliberate kill switch
- Automation actions to create a trading account and to hold one for approval
- Approve and reject with a reason, resuming or ending provisioning
- Retry and cancel provisioning from the CRM
- Fourteen operator actions, each gated on the account's state and the operator's permission
- Leverage, account type, password and archive changes pushed to the trading platform
- Work waits and is redelivered when a platform's circuit breaker is open
- Client merge re-points trading accounts rather than orphaning them
TradeCore Trading — Trade data
The append-only ledger, the projection folded from it, and every way it heals and checks itself.
- Append-only ingestion ledger, one row per fact, payload kept verbatim
- Trades and positions projected by folding that ledger, so they can be rebuilt from source
- Duplicate facts converge; a re-delivery that changes nothing is a no-op
- Cancelled trades retained with money zeroed — never deleted
- Corrections published as amendments naming the fields that changed
- Outage fill on reconnect, with every healed row logged
- Scheduled anti-entropy sweep per account
- Window count comparison against the platform's own count, where the platform can answer it
- Facts arriving before their account is provisioned are held and projected later
- An alarm on holds that stay unresolved
- Operator re-import of one account's trades over a window
- Trade executed and trade closed published as automation triggers, carrying the symbol and the currency
TradeCore Trading — Money
Tracked transfer legs, the idempotency probe, live withdrawal caps and close-out on the same rails.
- Wallet-to-trading and trading-to-wallet transfers as tracked legs: pending, completed, retry, failed
- An idempotency probe against the platform's own deal history before every balance operation
- Operator override and re-drive, both requiring a reason and both published
- A leg whose wallet side was already reversed refuses re-drive
- Fresh live balance and free margin for withdrawal caps, refusing rather than answering from cache
- Bonus credit onto and off an account through the same legs
- Negative-equity liquidation: read-only plus close-all, deduplicated
- Balance, equity, credit, used margin and free margin per account
TradeCore Trading — Client portal
What a client opens, sees and changes on their own trading accounts, in the broker's white-label portal.
- Client-opened live and demo accounts, choosing platform, currency, leverage and account type
- Separate eligibility for live and demo, resolved from the client's profile state
- Login details delivered to the client as soon as the trading platform provisions the account
- Credential reveal with show, hide and copy
- Client-initiated leverage change, password change, rename and archive
- Direct platform login links, to the platform the client trades on
- Trading history and ledger history across accounts
- Demo balance top-up
- White-label per brand, with pages switchable per brand
TradeCore Trading — Governance
Encrypted credentials, before-and-after on every change, permission-gated actions and a record never deleted.
- Field-level encryption on master passwords
- Only a platform-generated password is revealable; a client-chosen one is never echoed back
- Every credential reveal published with the actor and their capacity, and no plaintext
- Every account change published with the value before and the value after
- Operator free-text reasons kept internal
- Trading group names kept internal; account types are the client-facing product name
- Permission-gated action menu — an action an operator cannot take is not shown
- Data is never deleted: permanent audit trails
How does a broker CRM’s trading layer compare to the platform’s own admin?
Unlike legacy broker CRMs, which connect 2–3 trading platforms and leave each account to its own admin panel, TradeCore governs accounts on 8 trading platforms from one place. The trading platform executes the trades; TradeCore decides who gets an account, on what terms and in which state, and keeps an append-only ledger behind every trade.
| Capability | BrokerIQTradeCore | Legacy broker CRMs | The trading platform's own admin |
|---|---|---|---|
Platforms from one place | 8 trading platforms plus the Wallet, in one account list with the columns you choose | 2-3 trading platforms, each with its own admin panel | One platform — its own, and only its own |
Who sets group and leverage | Priority-ordered binding rules with an undeletable Default, and warnings when a configuration is ambiguous | A hard-coded default per platform | Set by hand, per account, in the platform manager |
Who may open what | Availability rules on country, introducing broker, campaign and referrer, with client-picks, auto or operator-only selection | Not modelled | Not modelled |
Account lifecycle | Seven states with an approval branch, automatic retries, and an activation trigger you set per backend | Create and delete | Create and disable |
Change accountability | Every change published with the value before and the value after, and the person who made it | A partial activity log | Platform-native logs with limited retention |
Trade data integrity | Append-only ledger with a folded projection, outage fill, scheduled sweep and window count comparison | Batch import reconciled monthly | Authoritative, but only for its own book |
Money onto the account | Tracked legs with an idempotency probe against the platform's own deal history before every balance operation | Manual reconciliation between CRM and platform | Manual, in the platform manager |
Client self-service | Clients open accounts, receive and reveal credentials, change leverage, rename and archive from your white-label portal | None — the operator does it | None |
Time to a working environment | Ready as soon as you finish signup | 3-6 months to go live | Not applicable |
Competitor columns describe categories of product, not named vendors. Every TradeCore cell describes the product as it runs today.
Trading platform questions, answered
What operations and back-office teams ask before they connect a trading platform to TradeCore.
Trading platform CRM integration connects a broker's trading servers to the CRM, so client trading accounts are opened, governed and reconciled from the client record. TradeCore does it for 8 trading platforms inside the BrokerIQ CRM core, with every account's group and leverage resolved from rules the broker authors.
Eight: MetaTrader 4, MetaTrader 5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade and TraderEvolution, plus the TradeCore Wallet for balances that are held rather than traded. Each connection is its own backend, so demo and live servers are configured separately with their own credentials, and one brokerage can run several servers of the same platform. Custom trading backends are supported through the open API.
Yes. TradeCore can mirror the clients, trading accounts and closed trades from the trading platform you already run, so IB commission and cashback work on real trade data with nothing migrated. A brokerage keeping its existing CRM can start with any of the six BrokerIQ modules standalone and move onto the CRM core later without rip-and-replace.
No. In mirror mode, TradeCore reads the clients, trading accounts and closed trades from the trading platform you already run, so IB commission and cashback work on real trade data from the first day. You still author the same catalogs and rules as a broker whose accounts TradeCore opens.
Yes. Trading is built into the BrokerIQ CRM core, so TradeCore's free plan runs it with one trading platform, two trading accounts per client — up to 5 through the free plan's shop — and trades syncing every 30–60 minutes. TradeCore's Core plan adds unlimited trading accounts per client and live trade import, and each further platform is €200 a month on either plan.
Still have questions?
Contact our teamRun Trading for free
TradeCore’s free plan switches on the BrokerIQ CRM core and every module, with trading included. No card to sign up — a card the first time you buy an add-on. Your environment is ready as soon as you finish signup.
What TradeCore’s free plan includes · TradeCore plans and add-on prices