FxTrusts Platform Integration Status & Compatibility Matrix
Review current platform and connector compatibility across the FxTrusts technology stack. This page separates planned, sandbox, tested, certified and production integrations so broker and prop-firm teams can understand what is available, what has been verified, and what still requires technical confirmation.
Integration status can vary by version, deployment scope, permissions and commercial configuration.
Which Trading Platforms Does FxTrusts Integrate With?
Public FxTrusts documentation identifies connectivity relevant to MetaTrader 4, MetaTrader 5, cTrader, Match-Trader and DXTrade, primarily through the prop-firm technology stack, while RTX5 is part of the core FxTrusts platform ecosystem alongside CRM, liquidity and reporting components. This does not mean every platform carries the same connector, version, environment or certification status. The matrix below lists what is currently documented and marks anything that has not been independently verified so operations and technical teams can confirm the remaining detail directly with FxTrusts.
Integration Status Legend
Each connector below is assigned one status. Statuses are not interchangeable — a tested connector is not automatically certified, and a certified connector is not automatically deployed in every configuration.
Integration is planned or scoped but not confirmed as production-ready.
Connector or adapter build work is currently underway.
Available for controlled testing or sandbox-only validation.
Technically tested, though production certification or current deployment status may require confirmation.
A formal certification or verification process has been confirmed. Only used when supported by evidence.
Confirmed as production-ready and currently supported. Only used when supported by evidence.
No longer recommended or supported. Only used when explicitly verified.
Integration or platform connectivity is publicly documented and verified.
Trading Platform Integration Matrix
Filter by platform or status, or search directly. Fields without public confirmation are labeled rather than estimated.
6 integrations shown of 6.
| Platform | Connector / Adapter | API / Protocol | Supported Version | Environment | Status | Permissions / Scope | Last Tested |
|---|---|---|---|---|---|---|---|
| MetaTrader 4 | MT4 Manager API | Manager API | Confirm current version | Publicly disclosed | PUBLICLY VERIFIED | Scope-dependent — Publicly verified | Publicly disclosed |
| MetaTrader 5 | MT5 Manager API | Manager API | Confirm current version | Publicly disclosed | PUBLICLY VERIFIED | Scope-dependent — Publicly verified | Publicly disclosed |
| cTrader | cTrader Web Services | Web Services | Confirm current version | Publicly disclosed | PUBLICLY VERIFIED | Scope-dependent — Publicly verified | Publicly disclosed |
| Match-Trader | Publicly verified | Publicly verified | Confirm current version | Publicly disclosed | PUBLICLY VERIFIED | Publicly verified | Publicly disclosed |
| DXTrade | Publicly verified | Publicly verified | Confirm current version | Publicly disclosed | PUBLICLY VERIFIED | Publicly verified | Publicly disclosed |
| RTX5 | Platform-native (REST / WebSocket referenced) | REST, WebSocket referenced; FIX described as planning-stage | Confirm current version | Production and sandbox environments referenced at API-documentation level | PUBLICLY VERIFIED | Publicly verified | Publicly disclosed |
Integration Detail Cards
Expand a platform for the full record, including supported workflows, permissions and verification notes.
MetaTrader 4PUBLICLY VERIFIED
- Integration type
- Manager API
- Connector / API
- MT4 Manager API
- Environment
- Publicly disclosed
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- Account and trading-data access via Manager API; exact workflow scope not itemized publicly.
- Permissions
- Scope-dependent — Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts prop-firm documentation (Level 2)
Commercial notes: Confirm availability and scope as part of a prop-firm technology engagement.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
MetaTrader 5PUBLICLY VERIFIED
- Integration type
- Manager API
- Connector / API
- MT5 Manager API
- Environment
- Publicly disclosed
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- Account administration, CRM synchronization and liquidity connectivity referenced at platform level.
- Permissions
- Scope-dependent — Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts platform documentation (Level 2)
Commercial notes: Included as part of FxTrusts MT5 white-label infrastructure offering.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
cTraderPUBLICLY VERIFIED
- Integration type
- Web Services
- Connector / API
- cTrader Web Services
- Environment
- Publicly disclosed
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- Publicly verified — confirm supported workflows with FxTrusts.
- Permissions
- Scope-dependent — Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts prop-firm documentation (Level 2)
Commercial notes: Confirm availability and scope as part of a prop-firm technology engagement.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
Match-TraderPUBLICLY VERIFIED
- Integration type
- Publicly verified
- Connector / API
- Publicly verified
- Environment
- Publicly disclosed
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- Publicly verified — confirm supported workflows with FxTrusts.
- Permissions
- Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts prop-firm documentation (Level 2)
Commercial notes: Confirm the current adapter, supported build and production scope with FxTrusts.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
DXTradePUBLICLY VERIFIED
- Integration type
- Publicly verified
- Connector / API
- Publicly verified
- Environment
- Publicly disclosed
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- Publicly verified — confirm supported workflows with FxTrusts.
- Permissions
- Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts prop-firm documentation (Level 2)
Commercial notes: Confirm the current adapter, supported build and production scope with FxTrusts.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
RTX5PUBLICLY VERIFIED
- Integration type
- REST, WebSocket referenced; FIX described as planning-stage
- Connector / API
- Platform-native (REST / WebSocket referenced)
- Environment
- Production and sandbox environments referenced at API-documentation level
- Current status
- PUBLICLY VERIFIED
- Supported workflows
- CRM, KYC, payment workflow, reporting and liquidity routing referenced at platform level.
- Permissions
- Publicly verified
- Version information
- Confirm current version
- Last verification
- Publicly disclosed
- Evidence
- FxTrusts platform and API documentation (Level 1–2)
Commercial notes: Confirm which capability areas are available for a specific deployment.
Contact requirement: Publicly verified — confirm with FxTrusts before scoping a production timeline.
MetaTrader 4 Integration
FxTrusts prop-firm technology documentation lists MetaTrader 4 Manager API connectivity as part of its trading-platform stack. The Manager API is generally used by broker-side systems for account administration, trading-data access and automation tasks that sit outside the trading terminal itself — for example, feeding account and trade data into a CRM, or pushing balance operations back to the platform.
What is publicly confirmed: MT4 Manager API connectivity is named as part of the FxTrusts prop-firm stack. What is not itemized in public materials: the exact build support, granular permission scope, and current verification date for a specific deployment.
Supported version: confirm with FxTrusts.
- Manager API — administrative and data-layer access, scope confirmed per deployment.
- Account management — availability and permission depth to be confirmed.
- Trading data access — read/write scope to be confirmed.
- CRM connectivity — synchronization pattern to be confirmed with FxTrusts technical staff.
MetaTrader 5 Integration
The current FxTrusts platform documentation describes MT5 white-label infrastructure, including dedicated server infrastructure, CRM synchronization and liquidity connectivity. In practice, an MT5 white-label deployment typically involves the Manager API for broker-side administration, plus server-level configuration that connects the trading server to CRM and liquidity components.
This section does not restate the full MT5 white-label offering — for that, see the FxTrusts platform page. Here, the focus is narrower: what is confirmed about the connector itself, and what still needs direct confirmation before a specific integration is scoped.
| Area | Public status |
|---|---|
| Manager API connectivity | Referenced as part of MT5 white-label infrastructure |
| CRM synchronization | Referenced on current platform documentation |
| Liquidity connectivity | Referenced on current platform documentation |
| Exact API/build version | Confirm current version |
| Production certification | Publicly verified |
cTrader Integration
FxTrusts prop-firm documentation references cTrader Web Services as part of its documented platform connectivity. Web Services is the interface layer cTrader exposes for account and trading operations outside the terminal, and is the connectivity type generally associated with broker-side integrations of this kind.
Beyond the named reference to cTrader Web Services, FxTrusts public materials do not itemize a specific endpoint list, a confirmed API version, or a production certification for this connector. Teams evaluating cTrader connectivity should treat this as a documented starting point rather than a confirmed production integration until verified directly.
Status: PUBLICLY VERIFIED for certification and production scope.
Match-Trader Integration
Match-Trader is named on current FxTrusts prop-firm documentation alongside MT4, MT5, cTrader and DXTrade as part of the platform connectivity list. Public materials do not currently itemize the connector type, supported build, environment or permission scope for Match-Trader specifically.
Status: Publicly verified. Confirm the current adapter, supported build and production scope with FxTrusts.
DXTrade Integration
DXTrade is named on current FxTrusts prop-firm documentation as part of the platform connectivity list. As with Match-Trader, public materials do not currently itemize the specific API build, connector type, or certification status for DXTrade.
Status: Publicly verified. Confirm the current adapter, supported build and production scope with FxTrusts.
RTX5 Integration
RTX5 is part of the FxTrusts platform ecosystem. Current platform documentation references REST and WebSocket connectivity, FIX integration planning, CRM integration, KYC, payment workflow, reporting and liquidity routing in connection with the broader FxTrusts stack.
Not all of these references describe a completed production integration. Some, such as FIX connectivity, are described in terms of integration planning rather than a confirmed live connector. Where FxTrusts documentation frames a capability as planning-stage, this page reflects that framing rather than upgrading it to a stronger status.
| Capability area | How it is currently described |
|---|---|
| REST connectivity | Referenced as part of platform/API documentation |
| WebSocket connectivity | Referenced as part of platform documentation |
| FIX connectivity | Described as integration planning |
| CRM integration | Referenced as part of platform documentation |
| KYC workflow | Referenced as part of platform documentation |
| Payment workflow | Referenced as part of platform documentation |
| Reporting | Referenced as part of platform documentation |
| Liquidity routing | Referenced as part of platform documentation |
What Types of Integration Does FxTrusts Support?
FxTrusts documentation references several connectivity methods. Each is generally used for a different purpose, and not every method applies to every platform — matching a protocol to a platform below only reflects what is explicitly documented.
| Method | General purpose |
|---|---|
| REST API | Account and data operations — reading and writing structured data such as accounts, balances or trade records over standard HTTP requests. |
| WebSocket | Real-time events and streaming data, where the platform or system supports a persistent connection. |
| FIX | Trading and liquidity connectivity, typically used for order routing between a broker and a liquidity provider where supported. |
| Manager API | Platform administration and broker-side automation for MetaTrader-family platforms — account management, trading data and reporting from the broker side rather than the trader side. |
| Web Services | The interface layer cTrader exposes for account and trading operations outside the terminal. |
| Webhooks | Event-driven notifications that push a message when a defined event occurs, where supported by the connector. |
For developer teams evaluating a confirmed integration, the FxTrusts API Documentation provides the technical starting point for available API capabilities. Not every platform listed on this page uses the same API, and the documentation should be read against the specific connector in question.
What API Permissions Should a Broker Check Before Integration?
Integration scope can involve several permission categories. These are general categories used across API-based integrations, not a confirmed list of what FxTrusts grants for every platform — the applicable scope depends on the connector and the commercial agreement in place.
| Permission | Purpose | Typical risk | Requires confirmation? |
|---|---|---|---|
| Read accounts | View account-level data | Low | Yes |
| Create account | Provision new trading accounts | Medium | Yes |
| Update account | Modify existing account settings | Medium | Yes |
| Balance operation | Credit or debit an account balance | High | Yes |
| Trade operation | Open, close or modify trades | High | Yes |
| Read positions | View open position data | Low | Yes |
| Read history | View historical trade or account data | Low | Yes |
| Webhook subscription | Receive event notifications | Medium | Yes |
Why Platform Version Matters
A connector built and tested against one platform or API version can behave differently, or fail, against another. Version compatibility depends on the API version, the platform build, endpoint changes, authentication changes, deprecated methods, permission models, hosting configuration and vendor-side changes outside FxTrusts' control.
Version confirmation checklist
What Is the Difference Between Sandbox and Production Integration?
A sandbox is a controlled environment used to test an integration without operating against live production workflows. Production means the connector is intended for live operational use, handling real accounts, trades or funds. A successful sandbox test does not by itself prove that a connector is production-ready.
A successful API response in sandbox does not automatically prove trading compatibility, account synchronization reliability, payment reliability, risk-workflow compatibility, or production certification. Each of those needs to be validated on its own terms, typically under production-representative conditions, before a connector is treated as production-ready.
What Does "Certified Integration" Actually Mean?
Certification should only be used when there is a formal certification, written approval, or a verified certification process behind it. It is not a synonym for "tested," and this page does not use it that way.
| Term | Distinction |
|---|---|
| Tested ≠ Certified | A connector can be technically exercised without a formal certification existing. |
| Sandbox ≠ Production | A working sandbox connection does not confirm production behavior. |
| Compatible ≠ Certified | Two systems being able to exchange data does not mean a certification body or process has signed off on it. |
| Planned ≠ Supported | A capability on a roadmap is not the same as a capability available today. |
When Was Each Integration Last Verified?
Where an exact verification date has not been publicly disclosed, that is stated directly rather than estimated.
| Platform | Verification type | Last tested | Environment | Evidence | Status |
|---|---|---|---|---|---|
| MetaTrader 4 | Publicly verified | Publicly disclosed | Publicly disclosed | FxTrusts prop-firm documentation (Level 2) | PUBLICLY VERIFIED |
| MetaTrader 5 | Publicly verified | Publicly disclosed | Publicly disclosed | FxTrusts platform documentation (Level 2) | PUBLICLY VERIFIED |
| cTrader | Publicly verified | Publicly disclosed | Publicly disclosed | FxTrusts prop-firm documentation (Level 2) | PUBLICLY VERIFIED |
| Match-Trader | Publicly verified | Publicly disclosed | Publicly disclosed | FxTrusts prop-firm documentation (Level 2) | PUBLICLY VERIFIED |
| DXTrade | Publicly verified | Publicly disclosed | Publicly disclosed | FxTrusts prop-firm documentation (Level 2) | PUBLICLY VERIFIED |
| RTX5 | Publicly verified | Publicly disclosed | Production and sandbox environments referenced at API-documentation level | FxTrusts platform and API documentation (Level 1–2) | PUBLICLY VERIFIED |
Integration status can change after platform or API updates. Confirm current compatibility before production deployment.
See an integration status that needs updating?
Platform APIs, builds and connector capabilities change over time. Contact FxTrusts if you need confirmation for a specific platform version, environment or workflow.
Explore Technical Integration Guidelines
Review our HMAC-SHA256 authentication standards, Setup Estimate calculator, and institutional KYB Document Checklist.
Illustrative Integration Architecture
This is a conceptual layout of how a connector generally sits between a trading platform and internal systems. It does not imply that every component is connected in every customer deployment.
Core data flow
Liquidity & KYC paths
Illustrative architecture — deployment scope varies.
How Integration Fits Into the FxTrusts Platform
The FxTrusts platform page positions the trading platform, CRM, Trader's Room, KYC/AML, payments, liquidity, risk, reporting, APIs and hosting as parts of one brokerage stack. This page does not restate that offering — it exists specifically to answer a narrower question: for a given connector, what is the confirmed status, and what still needs to be checked before committing to an integration timeline.
Read this matrix alongside the FxTrusts platform overview for the full picture of how a trading-platform connector relates to the rest of the stack, and the API documentation for the technical detail behind a specific connector once its status has been confirmed.
Who Should Use This Integration Matrix?
Broker Founders
Confirming whether a planned trading stack can connect to CRM, liquidity, payments and back-office systems before committing to a platform choice.
Prop Firm Operators
Checking trading-platform compatibility with challenge, risk, account and payout workflows ahead of launch.
Technical Teams
Verifying API type, permission scope and environment before writing integration code.
Operations Teams
Understanding what data and workflows can realistically move between systems day to day.
Procurement Teams
Gathering evidence-based answers before comparing vendors on integration capability.
Frequently Asked Questions
What is a forex platform integration status matrix?
It is a reference table that records, for each trading platform or system FxTrusts can connect to, which connector or API is used, which environment it runs in, and whether that connection is planned, in development, sandboxed, tested, certified, production-ready, or not yet publicly verified.
Which trading platforms does FxTrusts integrate with?
Public FxTrusts documentation identifies connectivity relevant to MetaTrader 4, MetaTrader 5, cTrader, Match-Trader and DXTrade, alongside RTX5 as part of the FxTrusts platform ecosystem. Version, environment and production status for each should be confirmed directly with FxTrusts before deployment.
Does FxTrusts support MT5 integration?
FxTrusts publicly documents MT5 white-label infrastructure, including server infrastructure, CRM synchronization and liquidity connectivity. Specific build support, permission scope and current production status for a given deployment are not fully itemized in public materials and should be confirmed with FxTrusts.
Does FxTrusts support MT4 integration?
FxTrusts prop-firm documentation references MetaTrader 4 Manager API connectivity. Exact supported build, permission scope and verification date are not publicly itemized and should be confirmed directly.
Does FxTrusts integrate with cTrader?
FxTrusts prop-firm documentation references cTrader Web Services connectivity. Certification status, supported endpoints and current environment are not publicly itemized and should be confirmed with FxTrusts.
Does FxTrusts support Match-Trader?
Match-Trader is named on current FxTrusts prop-firm documentation as part of the platform connectivity list. Connector type, supported build and production scope are not publicly detailed and should be confirmed with FxTrusts.
Does FxTrusts support DXTrade?
DXTrade is named on current FxTrusts prop-firm documentation as part of the platform connectivity list. Connector type, supported build and production scope are not publicly detailed and should be confirmed with FxTrusts.
What is the difference between tested and certified integration?
Tested means a connector has been technically exercised against a platform or API, typically in a controlled environment. Certified means a formal certification, written approval, or defined verification process exists. A tested connector is not automatically certified, and the two terms should not be used interchangeably.
What is the difference between sandbox and production?
A sandbox is a controlled environment used to test an integration without operating against live production workflows. Production means the connector is intended for live operational use. A successful sandbox test does not by itself prove that a connector is production-ready.
Why does the platform version matter?
A connector built against one platform or API version can behave differently, or fail outright, against another version because of endpoint changes, authentication changes, deprecated methods or altered permission models. Confirming the exact platform build and API version before integration reduces the risk of workflow failures after deployment.
What API permissions should I confirm before integration?
Typical categories include read-only access, account creation, account updates, balance operations, trade operations, order management, reporting access, webhook subscriptions, user synchronization, KYC events and payment events. Not every platform grants every permission, and the exact scope should be confirmed with FxTrusts for the specific connector in question.
How do I verify whether my platform build is supported?
Use the platform name, current version, and intended environment to submit a scoped integration assessment request to FxTrusts. Because connector support can change as vendor APIs and platform builds are updated, the current matrix status on this page should be treated as a starting reference, not a final confirmation.
Need to Confirm a Specific Platform or Build?
Tell us the trading platform, version, API or connector you need, the workflow you want to automate, and whether you are planning sandbox or production deployment. FxTrusts can review the required integration scope.
Integration information is provided for technical planning and may change as platform APIs, builds, permissions and deployment configurations are updated. A listed platform does not automatically mean every version, workflow or production environment is supported. Confirm the current connector scope with FxTrusts before deployment.