FinTech & Trading
CRM and Client Portal for a Forex or CFD Broker: Buy a Forex CRM, Use What Your Platform Includes, or Build Your Own
What a broker's back office does, from KYC and the client portal to IB commissions, which integrations take the most work, what EU rules expect from the records, and when to buy a forex CRM, use what your platform includes or build your own.
By amBrain10 min read
In this article
A forex or CFD broker's back office is the software behind the trading platform. It checks new clients, opens their trading accounts, moves their money and pays the partners who brought them in. Clients see one part of it, the client portal. Staff work in the other, the CRM (customer relationship management system). You can buy a forex CRM, use what your trading platform or white-label package includes, or build your own, often next to a CRM you buy. The choice depends mostly on how many platforms you run and how unusual your partner deals are. Your duties to clients and regulators stay with your firm on every route.
The short answer: if most clients trade on one platform and your partner deals are simple, start with what your platform or white-label package includes. Buy a forex CRM when you run several platforms or will soon need to connect many payment and identity-check providers. Build, often next to a CRM you buy, when your partner deals or onboarding flow are part of what you sell. On every route, have the contract give you a full export of client records, identity-check files and transaction history.
What does a broker's back office do?
It does seven jobs. Some products cover all of them, some only one or two:
- Onboarding and KYC (know your customer): checking identity documents and proof of address, and screening clients against watchlists, usually through a specialist provider
- The client portal, also called a traders' room, where clients register, upload documents, open accounts, deposit, withdraw and download statements
- Trading accounts: creating each account on the platform's server, setting its group, meaning the trading conditions it gets, and changing its balance. This runs through the platform's APIs, the interfaces a platform maker offers to other software
- Payments: deposits and withdrawals through payment service providers (PSPs), the companies that process card, bank and e-wallet payments
- IB commissions: an introducing broker (IB) brings in clients for a commission. The back office tracks who came from which IB, often across several levels of sub-partners. It then calculates what each one earns, for example per lot, the platform's standard trade size
- The sales and retention CRM: leads, calls, tasks and notes, so staff can turn sign-ups into funded accounts and reach clients who stopped trading
- Reports for management, finance, compliance and partners
MetaQuotes, the maker of MetaTrader 5, says a brokerage CRM “typically includes features such as lead management, client onboarding, customer segmentation and marketing automation.”
Which integrations take the most work?
Most of a back office is connections. Three of them take most of the effort: the trading platform, the PSPs and the KYC provider. Each one updates its own records, such as a balance, a payment status or a check result. Your back office has to keep its copy in step.
On MetaTrader 5, MetaQuotes says the “Manager API allows you to develop custom administration and management utilities, or even your own manager terminal”. The manager terminal is the program a broker's staff use to run client accounts. MetaQuotes also says the “Web API is used for platform integration with web resources and other services of the company.”
Spotware, the maker of cTrader, offers a WebServices API to “Integrate CRMs, traders' rooms and registration forms with the cTrader backend”. It says brokers can “Create trading accounts and register users with a single API call” and “Assign traders to partners for accurate reporting and commission tracking.” Spotware also offers a Manager's API, which it says “enables you to perform nearly all major operations on server entities”. It comes with a warning about cServer, the cTrader server: “using it improperly may have a detrimental effect on your cServer instances, potentially impacting the performance or even causing an outage.”
Match-Trade Technologies, the maker of Match-Trader, publishes a CRM API. Its integration guide walks through creating a user and a trading account, then handling deposits and withdrawals. It notes that “Payment gateways are pre-configured by Match-Trade or the client”.
A payment passes through several statuses before it is final. Spotware says “cTrader itself is not a payment processor”. Match-Trade calls the Praxis cashier “a PSP aggregator”, meaning one connection to many PSPs. Praxis documents a deposit status called “pending”: “Waiting for updates from the payment service provider (PSP).” A withdrawal request stays “awaiting merchant approval” until your staff approve it. Your back office must credit an account once, and only after the money is confirmed.
KYC results also come in from the provider's side. MetaQuotes calls Sumsub, a KYC provider, “readily integrated with MetaTrader 5”. Sumsub sends webhooks, messages one system sends to another when something changes, and says each one is “retried automatically on failure”. So the same message can arrive twice. The back office has to spot repeats in KYC and payment messages, or a deposit gets booked twice.
What comes with our trading platform or white-label package?
A white label is a copy of a trading platform that runs under your brand on another company's licence. What comes with it differs by platform.
MetaTrader 5. MetaQuotes says “CRM functionality is already embedded in MetaTrader 5 Manager Terminal, but we recommend extending this to a complete solution for both working with your clients and managing your company's internal operations.” It calls its built-in payments “a free solution which does not require developing resources or additional settings.” Its licence types, Entry, Standard and Enterprise, “contain different numbers of real accounts and sets of system components”.
cTrader. Spotware says it “provides platform-as-a-service”, so it runs the platform for you. Its documentation defines the broker's client area as “a CRM system belonging to a broker”, and its integrations page lists third-party CRMs. Spotware's full integration links your CRM to cTrader, so clients use one login for the portal and the platform (single sign-on) and can deposit inside the platform. Spotware says it “is a paid add-on and is not provided by default as part of the onboarding package.”
Match-Trader. Match-Trade's white-label page lists the “apps and extensions” it offers white-label brokers. Among them are a “Client Office / CRM application to easily onboard, verify and manage your client” and a “Multi-Level IB module to build automatically up to 50 level IB structures”.
This route has the fewest parts to run. It fits when most clients trade on one platform and your IB deals fit the product's settings. What you give up: the client record lives in the platform maker's or the provider's system, in their format, and leaves with you only as an export. MetaQuotes tells brokers who run MetaTrader 5 that “we have no access to your servers, accounts, or your clients' trading history”. On a white label, ask the provider who can open your clients' records.
When should a broker buy a ready forex CRM?
Forex CRM vendors sell the portal, the CRM, the IB module and the platform and PSP connections as one product. Kenmore Design, one vendor, says a forex CRM “integrates with the Forex Client Portal and Trading Platform, enables onboarding, KYC, deposits, trading data, IB structures, and PSP integrations”. These are vendor claims, so test them in a demo with your own platform and PSPs.
Buying fits when your needs look like those of the vendor's other clients:
- You run more than one platform, or plan to, and want one client record across them
- You need many PSP and KYC connections soon, and the vendor already runs them for other brokers
- Your IB plans and reports fit what the product supports
What you give up is control of the system of record, the place where the official version of each client's data lives. Kenmore Design, for example, says “By default, our Forex CRM is SaaS-based”, meaning the vendor runs it and you rent access. It adds that “source-code licensing for self-hosted environments is possible in certain cases.” A commission rule the product lacks waits for the vendor's plans or a paid change.
When is building our own back office worth it?
Building rarely means writing every part. More often it is your own client portal or IB commission engine next to a bought CRM. Or it is your own client database, kept as the system of record and fed by the other systems. A full build fits mainly when you run a trading platform of your own and want the back office built around it.
At least one of these should be true:
- Your partner deals or onboarding flow are part of what you sell, and the products you tested cannot apply them as written
- Fees that grow with your accounts or revenue now cost more than a team running your own system
- You want every client record, KYC file and payment in a database you control
The price is time at the start and a team after launch. Every platform update and PSP change becomes your job. If nobody on your side can own that, buy first and build the parts that set you apart later.
What does each route cost?
This article gives no prices of its own. Each route charges in a different way:
- Platform bundle: the licence or white-label fee plus paid add-ons. MetaQuotes ties its licence types to the number of real accounts
- Bought CRM: a monthly fee by package, module or number of clients, often with setup fees. Kenmore Design lists an “Initial Setup Fee”, a “Final Setup Fee” and a “Monthly Service Fee”. Some vendors offer a lower fee plus a share of your revenue. On 6 November 2026, BrokerTech's pricing page read “CRM from $3,000/month”, with the option of “a lower base plus 5% of net revenue”
- Own build: the team that builds it, the servers, and the staff who run and change it
- Every route: PSP and KYC provider fees, and your staff's time on integrations
Ask each vendor for a written quote at the number of clients you expect in one year and in three. Then add the cost of leaving, which is mostly the work of moving your data to the next system.
What should we own, and what can we take with us if we leave?
Whatever the route, name these in the contract, with the format of each export and when you can ask for it:
- The client database: every client, lead, account, note and status change, as a full export at any time and after the contract ends
- KYC files: documents, check results and dates. EU rules make you keep them for years after a client leaves, so they must outlive the vendor contract
- Transaction history: every deposit, withdrawal, transfer and adjustment, with the PSP's reference
- IB structures and commission rules: who introduced whom, at which level, under which rule, and every payout
- Domain and brand: the portal's domain, email domains and app store accounts, registered to your company
- Code: yours only on a build, under a contract that transfers the rights. On a bought product, ask for source code escrow. A third party holds the vendor's code and releases it to you if agreed events happen, such as the vendor closing. The code usually stays the vendor's, and you get a licence to use and maintain it
- Exit terms: notice and transition periods, export costs, and deletion of your data at the vendor afterwards
What do EU rules expect from these records?
This section quotes EU law only. Other countries have their own rules.
MiFID II, Directive 2014/65/EU, is the EU's main law for investment firms. Its Article 16(6) requires a firm to “arrange for records to be kept of all services, activities and transactions undertaken by it”. Article 72(1) of Commission Delegated Regulation (EU) 2017/565 adds that these records must be kept so that “any corrections or other amendments, and the contents of the records prior to such corrections or amendments” are easy to find. They must also be kept so that “it is not possible for the records otherwise to be manipulated or altered”. Where a CRM holds records these rules cover, one way to meet this is a change history that keeps earlier values and that staff cannot erase.
Article 16(7) of MiFID II covers recordings of “telephone conversations or electronic communications” about client orders and dealing on own account (the firm trading for itself), including those “intended to result in transactions”. They are kept for “a period of five years and, where requested by the competent authority, for a period of up to seven years.” If sales or retention staff call or message clients from the CRM, ask your lawyer which conversations this covers.
Directive (EU) 2015/849, the EU's anti-money-laundering directive, calls KYC checks customer due diligence. Under its Article 40, firms keep copies of the documents “for a period of five years after the end of the business relationship with their customer”. After that, they “delete personal data, unless otherwise provided for by national law”. Directive (EU) 2024/1640 repeals it with effect from 10 July 2027, when Regulation (EU) 2024/1624 starts to apply. The Regulation's Article 77 also counts the five years from “the date of refusal to enter into a business relationship”, so the rule covers files on rejected applicants too.
The GDPR is the EU's data protection law. Under it, a vendor that hosts your client data is usually a processor, which “processes personal data on behalf of the controller”, here your firm. Article 28 requires a contract saying the processor, “at the choice of the controller, deletes or returns all the personal data to the controller after the end of the provision of services”. The processor also needs your written authorisation before it brings in another processor. Ask each vendor which other processors it uses, such as its hosting company.
Article 24(9) of MiFID II covers fees and commissions that a firm pays to, or receives from, anyone other than the client or someone acting for the client, in connection with an investment or ancillary service. It allows them only where they are designed to enhance the quality of the service to the client and do not impair the firm's duty to act in the client's best interests. It says “The existence, nature and amount” of such a payment “must be clearly disclosed to the client”, before the service is provided. Ask your lawyer whether this covers your IB commissions.
All sources in this article were opened on 6 November 2026. EU law was read in the consolidated texts of the EU Publications Office.
What should we ask a firm that would build or connect our back office?
- Which platform APIs will you use for account creation, balance changes and reports, and which of them have you worked with before?
- How does the system credit a deposit exactly once, even when the PSP sends the same message twice or late?
- What happens when a client deposits or withdraws while the trading platform is unreachable?
- How are IB commission rules stored and changed, and can our finance staff recalculate a past month and get the same result?
- How is every change to a client record logged, and who can read or delete that log?
- Where are KYC files stored, how long are they kept, and how are they deleted when the retention period ends?
- What do we receive at handover: the source code, build instructions, the database layout and admin access to every server and outside service?
- Can you show this working in a system that runs today?
Where does amBrain fit?
amBrain publishes this blog. It describes one part of its trading work in one line: “amBrain builds algorithmic trading infrastructure: order execution, market data and pre-trade risk controls.” Another line on amBrain's website reads: “Trading terminal development, order management systems, and FIX protocol exchange integration.” Neither line names a CRM or a client portal.
amBrain has been building software since 2019. On how it works with clients, it says: “Three formats: full delivery, a dedicated team, or engineers embedded in your team.” Its line on ownership is “The client keeps full ownership of the product and the code, except our reusable components.” Ask for the list of those components by name before you sign.
This article is not a case study and describes no client work. It does not say that amBrain has built, bought or integrated a forex CRM, a client portal or an IB system for any client. It quotes the published pages of MetaQuotes, Spotware, Match-Trade Technologies, Kenmore Design, BrokerTech, Praxis and Sumsub. It claims no relationship between amBrain and any of these companies, recommends none of their products and gives no amBrain prices or timelines.
It is not legal advice either. Check the rules that apply to your firm with a lawyer in your market. If amBrain is on your shortlist, ask it the same questions as any other firm.
Topics
- Forex CRM
- Brokerage
- Client Portal
- Build or Buy