Connect your integrations yourself. Watch them run.
Integrations is the connection layer inside TradeCore's BrokerIQ CRM core for FX/CFD brokers: 8 trading platforms, 100+ payment providers and 5 KYC providers, connected on the broker's own vendor accounts and watched for failure.
100+ brokerages run on TradeCore, including MultiBank Group, AvaTrade, IC Markets, FP Markets and Trade Nation.
Providers you can connect, and the credentials each one asks for
- SumSub (Verification) — App token, Secret key, Webhook secret, from the provider's developer settings. Created against sandbox or production.
- Cellbunq (Verification) — API key, Webhook secret, from the provider's API credentials page. Created against sandbox or production.
- MT5 (Trading platform) — Server, Manager login, Manager password, from your platform server administrator. Registered as a demo or a live connection.
- Praxis (Payments) — Merchant credentials, from your gateway account manager. Created against sandbox or production.
Settings — Integrations
Add a connection
Available
What does a broker integration platform actually connect?
BrokerIQ is TradeCore's modular CRM and back-office product line for FX/CFD brokers. The integration layer is part of the CRM core: 200+ integrations across trading platforms, payment providers, verification providers, message channels and your own systems, all landing on one client record. Every BrokerIQ module also runs standalone on the CRM you already operate.
The data core
BrokerIQ CRM — clients, trades, transactions, KYC, payments
Five rails out, one record back
- On the BrokerIQ CRM core — Every rail lands on the BrokerIQ client record: Trading platforms, payment providers, verification providers and message channels write to one client record. Every BrokerIQ module shares one data layer with the CRM core, so nothing is copied between systems. Credentials, connection health, the exchange record and faults are run from one back office.
- Standalone on your CRM — A BrokerIQ module runs on the CRM you already operate: The module reads and writes your CRM both ways, over APIs and webhooks. Salesforce, HubSpot and Pipedrive are live today, and in-house CRMs are supported. Standalone Compliance sends outbound webhooks to your systems at compliance stages instead. Consolidate onto the BrokerIQ CRM core later, without rip-and-replace.
Do you need a developer to connect a provider?
No. An operator picks the provider from a catalogue in settings, pastes your credentials into the fields that provider asks for, and copies the callback URL TradeCore derives into the provider’s own dashboard.
- Step 01:
Pick the provider
A provider appears in the catalogue only once TradeCore has a working connection for it, so you can never configure one that will fail the first time a client uses it.
- Step 02:
Paste your credentials
The form asks for that provider's own fields and names where to find them in the provider's product. Choose sandbox or production when you create the connection.
- Step 03:
Copy the callback URL back
TradeCore derives the callback URL for that connection. You copy it into the provider's own dashboard, and their results start arriving on it.
And once it exists
Sandbox or production
A connection is created against one or the other, so a test integration can never quietly become the live one.
Deactivated, never deleted
Switching a provider off leaves every verification, payment and document it ever produced resolvable. Data is never deleted.
New platforms need no new form
The credential inputs are built from what each platform declares it needs, so a platform added to TradeCore appears in your settings with the right fields already on it.
Which provider verifies which client is a rule, not a rewire. SumSub, Onfido, Cellbunq, GBG and ComplyAdvantage connect the same way, and TradeCore’s conditional KYC routing picks the provider for each client by jurisdiction.
Your accounts, your rates, your keys
TradeCore stores the broker’s own credentials and does the wiring — nothing is resold, proxied or marked up. A secret goes in write-only, encrypted field by field, and never comes back out.
Write-only, encrypted field by field
A secret goes in and never comes back out: reading a connection tells you a credential is configured, and credentials, provider payloads and message bodies are encrypted at the field level.
- never returned on a read
- field-level encryption
- never written to a log
Rotation is all or nothing
Rotating a connection's keys means re-entering every key together, so a half-finished paste can never silently drop the rest.
- every key re-entered
- no partial rotation
Your account, your rates
TradeCore stores your credentials and does the wiring. Your contract with each provider stays yours, and every provider callback URL is signed and resolves its brand before any client data is read.
- not resold
- not proxied
- not marked up
- signed callbacks
Per brand, on your own accounts
- The same payment provider runs under different brands with different credentials, currencies, countries and limits.
- Each verification provider is scoped to the jurisdictions it serves, and each capability you enable on it carries its own auto-approval setting.
- Email sends from your own SendGrid account, with a separate From and Reply-To identity per brand.
- SMS sends from your own Twilio account, per brand, using your own published sender number.
The same protection covers what the connections write. Field-level PII encryption, row-level visibility scoping and an audit log on every mutating action govern the BrokerIQ client records every provider writes into.
What happens when a trading platform goes down?
The connection cuts out rather than piling more calls onto a dead platform, and waits longer after each further failure. When the wait elapses, exactly one worker makes a single probe call — so a platform that comes back is picked up without anyone asking.
Connection health
One trading connection, through a bad afternoon
- Closed
Calls go through
The connection is healthy. Every request reaches the trading platform and every failure is counted.
- Open
Calls stop instead of piling up
After a run of consecutive failures the connection cuts out, so a dead trading platform is not hammered by every worker at once. Each further failure lengthens the wait before the next try.
- Half-open
Exactly one call goes to look
When the wait elapses, one worker — and only one — is elected to make the probe call. Nothing else is spent finding out.
- Closed
Recovered, without anyone asking
If the probe succeeds the connection closes and normal traffic resumes. If it fails, the connection cuts out again for longer.
What the connection records
- Every trading connection carries a health state — healthy, degraded or unavailable — and an operator can set it by hand when they know something the trading platform has not reported yet.
- Every trading connection records how many failures ran consecutively, when it last cut out, how many times it has cut out, and the kind of error that did it.
The connection that carries every account. The same trading connections open client accounts on 8 platforms and bring closed trades into the CRM — live on TradeCore’s Core plan, every 30–60 minutes on TradeCore’s free plan.
What did we send them, and what did they say?
A deposit that reported success and never moved the balance. TradeCore writes every exchange with a trading platform or a payment provider to a durable record — the operation, the direction, the outcome and the scrubbed bodies — so an operator answers that question on screen instead of escalating it.
Provider exchanges
Every call, and every answer
| Time | Provider | Operation | Direction | Outcome | About |
|---|---|---|---|---|---|
| MT5 | Outbound | Succeeded | Trading account | ||
| Praxis | Inbound notification | Succeeded | Transaction | ||
| Praxis | Client return | Succeeded | Transaction | ||
| MT5 | Outbound | Provider rejected | Trading account | ||
| SumSub | Outbound | Not reached | Verification |
A client came back from the payment provider's page, and no notification from the provider has arrived for that deposit — so an operator chases the provider, not the client.
One exchange, opened
Credentials are stripped as the exchange is captured, so the record is safe to read.
Three directions
Outbound
TradeCore asked the provider to do something.
Inbound notification
The provider told TradeCore what happened.
Client return
The client came back from the provider's page. Recorded separately, so a deposit where the client returned and the provider's notification never arrived is visible as exactly that.
Four outcomes
Succeeded
The provider did what was asked.
Provider rejected
They answered and refused. Theirs to explain.
Timed out
We reached them and they never finished. Ours.
Not reached
We never got to them at all. Also ours, and a different fix.
Scrubbed before it is stored
Passwords, tokens, signatures and card numbers are stripped out of the request and the response as they are captured, then what remains is encrypted. A value the scrubber could not read is stored as unreadable rather than stored raw.
In the database, not in container logs
One durable row per exchange, attached to what it was about: a trading account, a transaction, a withdrawal, a trade-sync run or the connection itself.
Only calls that were about something
Polling, exchange-rate refreshes and keep-alive probes are deliberately not recorded, so the record stays readable. It holds the calls made about a client, an account, a payment or a withdrawal.
The deposit on the other end of the call. TradeCore Payments runs deposits and withdrawals through 100+ PSPs on two linked ledgers — gateway transactions on one, internal wallet movements on the other.
How do you find out an integration has broken?
TradeCore files an operational fault — a row in the CRM with a severity and a written remediation, not a log line. A payment callback failing its authenticity check is the only critical entry in the catalogue, because every settlement on that gateway is blocked while it holds.
Operations — faults
Open faults, most severe first
- CriticalPayments
A provider callback failed its authenticity check
The gateway's webhook secret is wrong. Every settlement on that gateway is blocked while it holds — which is why it is the only critical entry in the catalogue.
- HighPayments
A provider refused the gateway's credentials
No client can start a payment on that gateway. Filed separately from a provider that could not be reached at all, because the repair is a different one.
- HighPayments
A settlement reported less money than the transaction asks for
The payment is left un-settled rather than over-credited, and an operator is asked to reconcile it.
- MediumPayments
A provider reported a status that maps to nothing
Filed once per unrecognised status, because each one is its own mapping job.
- MediumPayments
A callback named a payment the gateway has no record of
Reconcile it against the provider's own dashboard. Filed separately from a callback whose body could not be decoded at all.
- HighTrading
The trading connection is unavailable
Raised alongside the connection cutting out, so the operator sees the cause and not only the symptom.
- MediumTrading
A platform group's rights are wrong, or its clock has drifted
Two separate entries, because a rights problem and a timezone problem are fixed in different places on the platform server.
- MediumVerification
Provider evidence arrived and could not be filed
Split in two: the document type was not mapped, or the mapping resolved and the upload was refused. Different gaps, different jobs.
- HighMessaging
A brand can no longer send on one channel
Grouped per brand and per channel, never per journey — one dead provider breaks every journey that brand runs, and twenty rows for one outage helps nobody.
- HighYour systems
An endpoint used up its retries without ever being accepted
Filed once per endpoint, so hours of failure are one row with a rising count. Something your system needed to know did not land.
One row per problem
Occurrences group, so a fault that fires a thousand times is one row with a count on it — not a thousand rows to read past.
A written remediation, not a stack trace
Every entry in the catalogue carries the sentence that says what to do about it, plus its most recent occurrences and links to what was involved.
Resolve it, and mean it
An operator closes a fault when it is fixed. If the same problem happens again the row reopens itself, so a premature close cannot hide it.
A dead email or SMS channel never stops a journey silently. Failing-send detection in Automations & AI names the broken channel per brand, and every journey routes the send outcome it hit — provider failed included — down its own exit.
How do you connect a system TradeCore has never heard of?
With a signed outbound webhook, the REST API or Zapier — the first two on TradeCore’s Core plan. TradeCore gives a broker’s own endpoint what it demands of its providers: a signature, a retry ladder, a dead letter, and a log that keeps the receiver’s own reply.
Your endpoint
Deliveries, and what came back
Re-drive refused: this delivery was already accepted, so resending it would be a real duplicate.
Every delivery carries
X-Webhook-Signature:
The second signature appears only while a signing secret is being rotated, so your receiver switches over on its own schedule.
Signed, and the secret is yours once
Every delivery carries an HMAC signature over the payload and a timestamp. The signing secret is shown once when it is minted; afterwards only a short fingerprint is readable.
- HMAC over payload + timestamp
- secret shown once
- seven-day dual signature on rotation
Nothing sends that did not happen
A delivery is scheduled only once the change that caused it has committed, and an operator re-drive refuses a delivery already accepted or still in flight.
- sent after commit
- rollbacks send nothing
- re-drive never duplicates
The receiver's own words are kept
The delivery log records the status, the HTTP code, the time taken and the attempts — and the receiver's own reply, which is where it says why it refused.
- status and HTTP code
- receiver's reply
- your own custom headers
- endpoint checked at delivery
Any of 200+ event triggers can call your system. On TradeCore’s Core plan, sending a webhook is an ordinary Automations & AI action, so a trigger in any of 17 areas of the brokerage can notify an endpoint you own.
Integrations on every plan
TradeCore's free plan runs the whole connection layer on one trading platform and one payment provider taking deposits; its shop adds payment providers up to 3 at €100 a month each, and further platforms are €200 a month each. TradeCore's Core plan adds the REST API, outbound webhooks and a connected KYC provider, and every further platform, payment provider and KYC provider stacks with no ceiling.
TradeCore's free plan
€0The whole layer, on your own accounts
- The whole connection layerThe provider catalogue, write-only credentials, connection health, the exchange record and the fault catalogue.
- One trading platform and one payment providerAny one of the 8 trading platforms, and one of 100+ payment providers taking deposits.
- Add connections as you growPayment providers up to 3 through the free plan's shop, at €100 a month each, bought one at a time — and further trading platforms at €200 a month each, with no ceiling.
- KYC reviewed by your own teamEvery client verified in the CRM's full manual review flow, with each decision on the audit trail.
- Message channels on your own accountsEmail on your own SendGrid account and SMS on your own Twilio account, with WhatsApp, Telegram, push, Slack and the in-app inbox beside them.
Core
€2,500 a month, flatOpen to your own systems
- The whole connection layerEverything on the free plan's lane.
- One trading platform, two payment providers and a KYC providerPayouts sent automatically through the connected payment provider, and one of the five KYC providers verifying clients.
- Add connections with no ceilingEach further trading platform is €200 a month, each payment provider €100 a month and each KYC provider €100 a month — all stackable.
- The REST API and integration keysDocumented as OpenAPI schemas, so your own systems read and write TradeCore data.
- Signed outbound webhooksAny of 200+ event triggers can call an endpoint you own, with HMAC signing, a delivery log and operator re-drive.
Every add-on priced side by side. Further trading platforms, payment providers and KYC providers sit with every other TradeCore add-on on the pricing page. No per-trader fees, no per-trade fees, no setup fees.
Every connection, and everything you can set on it
Every part of TradeCore Integrations, by area — the trading platforms, payment providers, verification providers and message channels, how credentials are held, what happens when a provider breaks, and your own systems.
Trading platforms
8 platforms, each a named connection you register yourself, with its own mode, rules and health.
- MT4, MT5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade, TraderEvolution
- Live or demo mode, fixed when the connection is created
- A demo connection states the opening credit every demo account is funded with
- Credential fields come from the platform itself, so a newly supported platform arrives with the right form
- Maximum trading accounts per client, set per connection
- Whether the platform requires a group and whether it requires a leverage
- An optional client-state code that provisions a trading account the moment a client reaches that state
- Health state — healthy, degraded, unavailable — settable by an operator
- A circuit breaker per connection, with the failure count, the last cut-out and the error kind that caused it
- Custom trading backends supported through the open API
TradeCore Integrations — Trading platforms
8 platforms, each a named connection you register yourself, with its own mode, rules and health.
- MT4, MT5, cTrader, DXtrade, MatchTrader, TradeLocker, ScaleTrade, TraderEvolution
- Live or demo mode, fixed when the connection is created
- A demo connection states the opening credit every demo account is funded with
- Credential fields come from the platform itself, so a newly supported platform arrives with the right form
- Maximum trading accounts per client, set per connection
- Whether the platform requires a group and whether it requires a leverage
- An optional client-state code that provisions a trading account the moment a client reaches that state
- Health state — healthy, degraded, unavailable — settable by an operator
- A circuit breaker per connection, with the failure count, the last cut-out and the error kind that caused it
- Custom trading backends supported through the open API
TradeCore Integrations — Payment providers
100+ providers and 300+ payment methods, each gateway configured per brand, method by method.
- Named gateways include Stripe, Skrill, Neteller, PayPal, Praxis, CoinsBuy, Bridger Pay and FasaPay
- A gateway belongs to one brand and carries that brand's own credentials
- Per gateway: deposits, payouts, refunds and card tokenization, each switched independently
- Whether clients see the gateway or only your staff, and its position in the client's cashier
- How the cashier opens: modal, new tab, iframe, direct, or on-screen instructions
- Per method: minimum and maximum amount, currency list and country list — leave a list empty and it means all
- A method open for deposits, for withdrawals, or both — and a gateway that cannot pay out cannot carry a withdrawal method
- Manual bank transfer as a gateway with no credentials at all: you write your own labelled instruction rows per currency
- Custom payment methods mapped to any gateway
TradeCore Integrations — Verification providers
5 providers, scoped by jurisdiction, with the capabilities you enable on your own account.
- SumSub, Onfido, Cellbunq, GBG, ComplyAdvantage
- Seven capabilities you enable on your own provider account: identity verification, document verification, liveness, face match, address verification, AML screening, PEP screening
- Only the capabilities a given provider supports can be switched on for it
- Each enabled capability carries its own auto-approval setting
- Jurisdiction scoping per connection — the mechanism behind conditional KYC routing
- Sandbox or production, chosen when the connection is created
- Deactivate, never delete, so historical verification events stay resolvable
- The callback URL for the connection, derived by TradeCore and copied into the provider's dashboard
TradeCore Integrations — Message channels
8 channels, with email and SMS sent on your own provider accounts.
- Email, SMS, WhatsApp, Telegram, Push, Webhook, Slack, in-app inbox
- Email on your own SendGrid account, with a separate From and Reply-To identity per brand
- SMS on your own Twilio account, per brand, with your own published sender number
- Per-language templates on email and SMS
- Delivery status written back from the provider on both email and SMS
- A failing channel is reported per brand and per channel, not per journey
TradeCore Integrations — Credentials
How every connection's secrets are held, rotated and kept out of reach.
- Credentials are write-only — a read says a credential is configured and never returns it
- Credentials, provider payloads and message bodies encrypted at the field level
- Rotation is all or nothing — every key is re-entered together
- Signed provider callback URLs that resolve the brand and the connection before any client data is read
- Credentials handed to a connection per call, never held by it and never written to a log
- SMS bodies never written to a log, because they may carry a live one-time code
- Your own provider contracts — nothing resold, proxied or marked up
TradeCore Integrations — Health, record and faults
What the layer does when a provider breaks, and the record it keeps of every call that mattered.
- A circuit breaker on every trading connection: closed, open, half-open
- Calls stop instead of piling onto a dead platform, with a longer wait after each further failure
- Exactly one worker elected to probe a platform that may have recovered
- A durable record of every exchange with a trading platform or payment provider, held in the database
- Three directions — outbound, inbound notification, client return
- Four outcomes — succeeded, provider rejected, timed out, not reached
- Request and response bodies scrubbed of credentials at capture, then encrypted
- Housekeeping traffic — polling, rate refreshes, keep-alive probes — deliberately not recorded
- Every inbound KYC and payment-provider delivery logged with what was done with it
- Operational faults with a severity and a written remediation
- One row per problem, with an occurrence count and its most recent samples
- Faults filtered by status, severity, type and brand
- A resolved fault reopens itself if the same problem recurs
TradeCore Integrations — Your own systems
Webhooks, the REST API, two-way CRM sync and the business tools around them.
- Outbound webhook endpoints on TradeCore's Core plan, each with a name, a URL, your own custom headers and an optional signing secret
- HMAC signature over the payload and a timestamp, with a seven-day dual-signature rotation window
- A signature header you supply is discarded, so only TradeCore signs a delivery
- Endpoint URLs checked at registration and again at delivery, so an endpoint cannot be aimed at an internal address
- A delivery is scheduled only once the change behind it commits — a rolled-back action sends nothing
- A delivery log with status, HTTP code, elapsed time, attempts, and the receiver's own reply
- Operator re-drive, refused for a delivery already accepted or still in flight
- The REST API and integration keys on TradeCore's Core plan, documented as OpenAPI schemas
- Two-way sync with the CRM you already run: Salesforce, HubSpot and Pipedrive live today, in-house CRMs supported
- Zapier, Segment and Intercom for the rest of your stack
- Data migration from Salesforce, HubSpot, legacy broker platforms and custom-built systems, with zero data loss
What makes a broker integration platform different from a connector?
Unlike legacy broker CRMs, which ship 10–20 PSPs, 2–3 trading platforms and one basic KYC provider, TradeCore connects 100+ PSPs, 8 trading platforms and 5 KYC providers on the brokerage's own accounts — and files integration failures as named faults with a written fix.
| Capability | BrokerIQTradeCore | Legacy broker CRMs | Point-to-point connectors or a general iPaaS |
|---|---|---|---|
Providers you can connect | 100+ PSPs with 300+ payment methods, 8 trading platforms and 5 KYC providers | 10–20 PSPs, 2–3 trading platforms and 1 basic KYC provider | Whatever connectors your team builds and maintains |
Who adds an integration | Your ops team, from a catalogue in settings, per brand — the provider is offered only if a working connection exists for it | A developer ticket and a release for each new provider | A developer builds and maintains each connector |
Whose provider account is used | Yours. TradeCore stores your credentials and does the wiring; nothing is resold, proxied or marked up | Often the vendor's account, with the vendor's rates | Yours, and yours to maintain |
How credentials are held | Write-only and encrypted field by field; a read says a credential is configured and never returns it; rotation is all or nothing | Stored per installation, often readable by staff | Whatever your team built |
Per-brand configuration | Independent credentials, currencies, countries, limits and jurisdictions per brand on the same provider | One configuration shared across brands | Possible, and yours to build twice |
What happens when a provider goes down | The connection cuts out instead of piling on, waits longer after each failure, then sends exactly one call to check whether it is back | Retries continue against a dead endpoint | Whatever your team built, per connector |
Is there a record of the call | One durable row per exchange — the operation, the direction, the outcome and the scrubbed bodies | Container logs, until the process restarts | Whatever your team logged |
Does a failure have a name | A named catalogue entry with a severity and a written remediation, grouped one row per problem and reopened if it recurs | A support ticket and a log search | An alert, if somebody wrote one |
Outbound webhook security | On TradeCore's Core plan: an HMAC signature over payload and timestamp, a secret shown once, a seven-day dual-signature rotation and the endpoint address checked at delivery | A shared static token, or nothing | Yours to design |
Competitor columns describe categories of product, not named vendors. Every TradeCore cell describes the product as it runs today.
Integration questions, answered
What operations and technology teams ask before they connect their providers to TradeCore.
A broker integration platform is the layer that connects a brokerage's trading platforms, payment providers, verification providers and message channels to one client record. TradeCore's sits inside the BrokerIQ CRM core and connects 8 trading platforms, 100+ payment providers with 300+ payment methods, 5 KYC providers and 8 message channels — 200+ integrations in total.
The whole connection layer — the provider catalogue, write-only credentials, connection health, the exchange record and the fault catalogue — on one trading platform and one payment provider taking deposits. The free plan's shop adds payment providers up to 3 at €100 a month each, and further trading platforms are €200 a month each. TradeCore's Core plan adds the REST API, outbound webhooks and a connected KYC provider.
Yes. TradeCore's Core plan includes the REST API and integration keys, documented as OpenAPI schemas, plus signed outbound webhooks that any of 200+ event triggers can fire. Zapier, Segment and Intercom cover the rest of a brokerage's stack.
Yes. Every BrokerIQ module runs natively on the BrokerIQ CRM core or standalone on the CRM your brokerage already operates, syncing both ways over APIs and webhooks — standalone Compliance sends outbound webhooks at compliance stages instead. Salesforce, HubSpot and Pipedrive are live today, in-house CRMs are supported, and a brokerage can consolidate onto the BrokerIQ core later without rip-and-replace. Standalone deployment is quoted separately, and it is not part of TradeCore's free plan.
Yes, in several ways. Custom trading backends connect through the open API, custom payment methods can be mapped to any gateway, and Zapier, Segment and Intercom cover the rest of a brokerage's stack. Custom integrations are part of a TradeCore Enterprise agreement.
Still have questions?
Contact our teamRun Integrations for free
TradeCore’s free plan switches on the BrokerIQ CRM core and every module, with the connection layer 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