Inside MetaTraderCRM's separate MT4 and MT5 brokerage editions

MT4 and MT5 follow separate deployment paths

The details in this profile are attributed to TGS's published product documentation, checked on 19 October 2026. They describe the advertised product scope rather than the results of an independent installation or execution test.

TGS's MT4 page, which dates its connector scope to 16 October 2026, describes an MT4-specific REST gateway. It retains client records, staff roles, trader portals, KYC document review, support and team tasks. Account import depends on verified access to the exact account group and a complete gateway response. MetaTraderCRM — MT4 CRM; connector scope dated 16 October 2026 ↗

The same page explicitly blocks live Copy Trading and MAM execution in the current MT4 release. PAMM settlements and transfers are also blocked. MT4 and MT5 use separate installations and storage; cross-platform MT4-to-MT5 copying is outside the stated MT4 scope. These boundaries are important when a brokerage compares visible modules with operations it can actually activate. MetaTraderCRM — MT4 CRM; connector scope dated 16 October 2026 ↗

For MT5, the integration documentation describes HTTPS access through MT5 Web API and up to 50 isolated broker connections. Manager permissions and account-group access determine which server actions are available. An API method appearing in a catalogue does not establish that a particular manager can execute it. MetaTraderCRM — MT5 integration and Web API documentation ↗

Client funding has distinct operational milestones

The finance documentation lists 18 payment adapters and requires each broker to configure its own merchant credentials and permitted callbacks. Provider confirmation and explicit MT5 account crediting are separate stages. Nuvei is described as reconciliation-only in this release. MetaTraderCRM — deposits, withdrawals and reconciliation ↗

Withdrawals likewise separate review, the trading-account debit and external payment. TGS says an authorised operator carries out the external transfer separately and records its reference; the CRM does not itself send the bank transfer. This structure can help a team track which stage has evidence and which still requires action. MetaTraderCRM — deposits, withdrawals and reconciliation ↗

An illustrative deposit investigation would therefore ask three questions: what the provider confirmed, what the MT5 account recorded and what the CRM linked to that operation. A successful checkout redirect would answer none of those questions on its own.

Copy Trading and pooled investment use different models

The MT5 Copy Trading documentation describes hedging market positions, explicit symbol routes, subscriber controls, client consent and administrator approval. It requires a persistent worker. The worker observes snapshots, which means a source position opened and closed between reads can be missed. MetaTraderCRM — cross-broker Copy Trading for MT5 ↗

PAMM instead tracks investor shares around a dedicated MT5 manager account. The published model uses one broker and one currency per fund, individual high-water-mark performance fees and confirmed settlement stages. Funding and withdrawals require stopped trading with no open positions or pending orders. MetaTraderCRM — MT5 PAMM software and investor portal ↗

For a brokerage evaluating the software, these documented differences provide a useful acceptance agenda: select the edition, verify account reads, test the required permissions, reconcile money movements and demonstrate the intended investment workflow in a controlled environment. TGS's current product pages at MetaTraderCRM.com are the direct reference for discussing that deployment scope.