Custom integrations for MT5 brokers are the pieces of software that connect a MetaTrader 5 server to everything around it: the CRM, payment providers, KYC and AML vendors, liquidity bridges, market data feeds and the broker’s own systems. FXUP builds them on MetaQuotes’ Web and Manager APIs and on each vendor’s own API and webhooks, with every event logged and applied exactly once.
What custom integrations does an MT5 broker usually need?
Usually five kinds: MT5 account and trade data into the CRM, payments into MT5 balances, verification results into client profiles, prices and orders between MT5 and liquidity, and reporting out to finance or management. A broker that launches on an off-the-shelf stack gets most of these already connected. The custom work starts when you add a payment provider that nobody has integrated yet, use a KYC vendor your regulator prefers, need a report your bank asks for, or want MT5 events to reach a system your team already relies on.
We come to this from a particular angle. Our own branded WebTrader and mobile trading app run on a Go back end that talks to MetaTrader 5 through the Web API all day, for every connected client. The problems that matter in integrations, such as timeouts, duplicate events, server clocks and partial failures, are problems we deal with in our own products first.
Which MetaTrader 5 APIs can an integration use?
MetaQuotes offers five server-side APIs, and the right one depends on what the integration needs to do. Most broker integrations use the Manager API or the Web API; the Gateway and Server APIs are for deeper work on execution and the trade server itself. The table uses MetaQuotes’ own one-line definitions.
| API | MetaQuotes’ definition | Typical broker integration |
|---|---|---|
| Manager API | “allows you to develop custom administration and management utilities, or even your own manager terminal” | CRM account opening, balance operations, back-office tools |
| Web API | “used for platform integration with web resources and other services of the company” | Web services, client portals, trading front ends such as ours |
| Gateway API | “used for MetaTrader 5 integration with other trading systems and creation of custom data feeds” | Connections to liquidity venues and external price sources |
| Server API | “can help you add more functions to MetaTrader 5 Trade Server and MetaTrader 5 History Server” | Server plugins for custom rules and processing |
| Report API | “expands the reports which are produced by the MetaTrader 5 trade servers” | Custom server-side reports |
What does an FXUP integration look like under the bonnet?
Usually a small Go service that sits next to MT5, holds the API connection and does one job well. Our trading front ends use the same design: the Go back end keeps a pool of connections to the MT5 server, queries it in batches for every connected user roughly every 100 milliseconds, and pushes changes to browsers and phones over WebSocket, the protocol the IETF standardised in RFC 6455 for two-way communication between a client and a server. MT5 itself is reached through the Web API, not through WebSocket.
For integrations, that design has three practical consequences. Credentials stay in one place on the server. Load on MT5 does not grow with every extra user or report, because queries are batched. And when the trade server restarts, as it does for MT5 updates, the service reconnects and carries on instead of needing someone to restart it by hand. Updates go to the demo instance first and are checked before live is touched.
How does a payment provider integration work?
The provider tells your system that money has moved, and your system turns that into an MT5 balance operation exactly once. The client starts a deposit in the client area, the CRM creates a payment request and sends the client to the provider, and the provider later sends a notification, usually a webhook, with the result. The integration verifies the notification, matches it to the request, records it, and only then credits MT5.
Two details separate a reliable integration from a fragile one. First, notifications are verified before anything happens; Stripe’s documentation, for example, describes checking a signature on every webhook so that nobody can fake a payment message. Second, the same event can arrive more than once, so the integration must recognise a repeat and ignore it. Stripe puts the second point plainly.
Withdrawals run in reverse and need more care, because money leaves the business. The integration checks KYC status and free margin, waits for staff approval where your rules require it, debits MT5 and then instructs the provider. If any step fails, the record shows exactly where, so finance never has to guess whether a client was paid. The forex CRM is where these approvals live.
“Webhook endpoints might occasionally receive the same event more than once. You can guard against duplicated event receipts by logging the event IDs you’ve processed, and then not processing already-logged events.”
How do KYC and AML vendor integrations work?
The vendor runs the document and identity checks; the integration brings the result back into your CRM and moves the client forward or into a review queue. Most vendors offer a hosted or embedded check and then report the outcome by webhook; Sumsub, for instance, describes its webhooks as a way to “receive automatic notifications about verification events”. The integration maps each status to your own workflow: approved, rejected, more documents needed, or manual review.
What matters most is the record. A compliance officer should be able to open a client and see which check was run, when, with what result and who made the final decision. If you change vendor later, the history from the old one should still be readable. Our KYC and AML glossary entry explains the terms. Which checks you need is set by your regulator and the countries your clients come from; this is not legal advice.
Can you integrate liquidity providers and bridges with MT5?
Yes. Connecting MT5 to liquidity is either done with a bridge, a separate system that routes orders and aggregates prices, or with a gateway that runs as part of the MT5 environment. MetaQuotes now also offers its own aggregation product, Ultency, which it describes as an “ultra-low-latency solution for liquidity aggregation, order matching, and risk management” and which supports routing between A-Book, B-Book and C-Book executions.
Our part in a liquidity project is usually the integration around the bridge: connecting it, checking that the provider’s instruments line up with the symbols your team has set up in MT5, implementing the routing rules your dealing desk decides, and building the reports that show what was hedged and where. The trade-offs between options are covered in our pages on liquidity provider integration, MT5 liquidity bridges and A-book, B-book and hybrid execution.
Can you connect custom data feeds to MetaTrader 5?
Yes, within the limits of what the MT5 licence holder allows. Price data reaches MT5 from liquidity connections or from a separate feed through the Gateway API, which MetaQuotes defines as covering “creation of custom data feeds”. Data can also flow the other way: MT5 prices, deals and account data exported to a risk dashboard, an accounting system or a data warehouse.
The detail people overlook is time. MT5 timestamps bars, ticks and deals in the trade server’s own time, which many brokers run at UTC+2 or UTC+3 depending on the season. An integration that mixes server time with UTC, or applies its own daylight-saving rules, produces candles and reports that are two or three hours out. We convert to real Unix time at the boundary and never guess. Our forex price feed guide covers where prices come from.
Can MT5 events trigger webhooks into my own systems?
Yes. A small service can watch MT5 for the events you care about and push them where your team works. Examples we are asked about: a message to the dealing desk when a single client’s exposure crosses a limit, a notification to the account manager when a VIP client deposits, a nightly export of IB volumes to accounting, or a lead score updated in your sales tool when a demo client places their first trade.
The pattern is the same each time. Read from MT5 through the API, decide what counts as an event, send it with a signature so the receiver can trust it, retry if the receiver is down, and log everything. The receiver should be able to handle the same event twice without doing the work twice.
Risk alerts
Exposure, margin level or large-order thresholds sent to the dealing desk in real time.
Finance exports
Deposits, withdrawals, IB payouts and net funding pushed to accounting on a schedule.
Sales signals
First deposit, first trade or inactivity events sent to your CRM or sales tool.
Support context
Recent orders and errors attached to a client’s support ticket automatically.
How does FXUP scope and deliver an integration?
We start from the other side’s documentation and your business rule, not from code. Most of the time on an integration goes into agreeing what should happen in the unusual cases, and that is best done before anything is built.
- RequirementsYou tell us what should happen, in business terms: “credit MT5 when a card deposit is confirmed, hold anything above our approval limit for review”.
- Documentation and accessWe read the vendor’s API documentation and agree the MT5 API access needed with you or your MT5 provider.
- Written scopeA short document listing events, edge cases, retries, logs and what your staff will see. You approve it.
- Build on demoThe integration runs against your MT5 demo server and the vendor’s sandbox first.
- Testing with real casesYour team runs real scenarios, including failures: duplicate notifications, timeouts, rejected payments.
- Live and monitoredReleased to live after demo has been checked, with alerts if something stops flowing.
What security rules apply to broker integrations?
The same few rules every time, because integrations touch money and personal data. We apply them to our own services and expect them from any vendor we connect to.
- MT5 API credentials and vendor keys live on the server side only, never in a browser or mobile app.
- Every inbound notification is verified, using the vendor’s signature or another agreed method, before it changes anything.
- Every event is logged with an identifier so repeats are recognised and ignored.
- Money-moving operations are never retried blindly after a timeout; the system checks the real state first.
- Connections run over TLS, and access to the MT5 server is limited to the services that need it.
- Error messages shown to clients are readable and contain no internal server details.
Should I use an off-the-shelf plugin or a custom integration?
Use an off-the-shelf connector when one exists and does what you need; build custom when it does not, or when the existing one hides problems you cannot see. Many CRMs advertise long lists of ready integrations, and for mainstream payment and KYC providers that is often the fastest route. Custom work earns its cost when the provider is regional, the rule is specific to your business, or the data needs to reach a system nobody else uses.
| Ready connector | Custom integration | |
|---|---|---|
| Time to start | Short, if it already exists | Depends on vendor documentation and scope |
| Fit to your rules | What the connector supports | Built around your rules |
| Visibility of failures | Varies; ask to see the logs | Logs and alerts designed in from the start |
| Regional or niche vendors | Often missing | Possible if the vendor has an API |
| Maintenance | Vendor’s responsibility | Agreed in the scope; changes when the vendor’s API changes |
What do you need from me to quote an integration?
Three things: the name of the system on the other side (with a link to its API documentation if you have one), a sentence or two on what should happen, and your MT5 setup. If you are on an MT5 grey label, the MT5 provider controls API access: on an FXUP grey label, Manager API and SDK access is provided after payment, and with another provider we need to know who it is and what it allows. On your own server, we will need to agree access with your administrator.
The effort, and therefore the quote, depends on the quality of the vendor’s documentation, the number of edge cases (refunds, partial payments, expired sessions, duplicate notifications), whether a sandbox exists, how many environments we deploy to and who maintains the connection when the vendor changes its API. Current prices and conditions for FXUP’s standard products are shown in the solution finder, and a custom integration is scoped in writing once the vendor and the rule are known. If you are comparing quotes, check that each one names the same edge cases, testing in the vendor’s sandbox and a maintenance arrangement, because those are the lines most often left out.
The CRM sits in the middle of most integrations. FXUP has its own CRM and also works with partner CRMs; we propose whichever fits your payment providers, KYC vendor and IB structure, and we can equally connect a new vendor to the CRM you already run.
FXUP is an independent technology provider and is not affiliated with MetaQuotes; MetaTrader 5 and its APIs are licensed through your MT5 arrangement. For bigger picture planning, our broker technology stack guide shows where each integration sits. If you are still choosing the MT5 set-up your integrations will run on, open the solution finder: it shows the right FXUP product for your case with current prices and conditions on the same screen, and a reference code to continue with our team, so the integration can be discussed from there.
Questions buyers ask
Which MT5 API do integrations use?
Can you connect a payment provider that my CRM does not support?
Can you integrate my KYC vendor?
Do I need my own MT5 licence for API integrations?
Can MT5 send alerts to Telegram, email or my own systems?
How long does an integration take?
What happens if the other system is down?
Can you work with my existing CRM rather than yours?
Is FXUP affiliated with MetaQuotes?
Not covered here? Open the solution finder and see the setup, prices and conditions that fit your case.
Sources
- MetaQuotes — MetaTrader 5 for brokers (API overview) (accessed October 2026)
- MetaQuotes — Ultency (accessed October 2026)
- Stripe — Receive Stripe events in your webhook endpoint (accessed October 2026)
- Sumsub — Webhooks documentation (accessed October 2026)
- IETF — RFC 6455: The WebSocket Protocol (accessed October 2026)
FXUP is an independent consulting and technology firm and is not affiliated with MetaQuotes Ltd. MetaTrader 4 and MetaTrader 5 are trademarks of MetaQuotes Ltd. This page is general information, not legal, tax or investment advice; regulatory requirements depend on the jurisdiction and change over time. Current FXUP prices and conditions are shown in the solution finder.