Checklist · Platform Procurement
Platform Entitlement: A Supplier Evidence Worksheet
Check the contracting entity, named licence holder, permitted service and administrator rights before treating platform access as a verified entitlement.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
Quick answer
Platform entitlement review establishes which entity has which contractual right to use or supply a platform service. Identify the publisher, licence holder, contracting supplier, customer entity and permitted use, then connect each claim to current evidence. Working credentials demonstrate access; they do not by themselves establish ownership or transferable rights.

Map the entities and the purchased right
Write the exact legal names before reviewing features. The platform publisher, holder of a software licence, hosted-service supplier and operator facing end clients may be different entities. Ask which agreement connects each party and whether the proposed service is within its permitted scope. Record the territory, environment, customer category and any approval conditions that matter.
MetaQuotes describes direct MetaTrader 5 licensing and deployment on the licensee's own infrastructure on its broker page. That publisher description does not authenticate a third party's proposed hosted arrangement. Request evidence for the specific arrangement rather than assuming that a platform logo or Manager login establishes a direct MetaQuotes licence.
Sources for this section
- MetaQuotes: MetaTrader 5 licensing and broker deploymentwww.metatrader5.com
Inspect evidence at the right level
A useful packet identifies the agreement or entitlement record, issuing party, effective dates, service scope, limitations and a contact authorized to clarify it. Sensitive commercial material may need a controlled review, but a redacted record must still answer the material question. Mark unresolved rights as unresolved; do not convert inability to inspect evidence into a positive verification.
Record administrator privileges separately. Rights to create accounts, edit groups, view reports or export data are operational permissions that can differ by deployment and role. Verify them with an approved demonstration and permission list, then connect them to the contract. A feature shown by a supplier's superuser may not be available to the customer's role.
Keep operating permission separate
Software rights, incorporation and permission to conduct financial activities are different assessments. The FCA's application guidance, for example, treats authorization as permission for specified activities and describes limits confirmed to the firm. That is UK-specific context; it does not decide the legal position of another entity or market.
Assign the legal and compliance review to a qualified owner for the actual business model and jurisdictions. Record a dependency when platform supply or launch is conditional on that review. The entitlement worksheet should support the decision, not make an unsupported claim that a supplier's regulation automatically covers its customer's operations.
Sources for this section
Example: access demonstrated, supply rights still open
A fictional supplier demonstrates account creation using a hosted administration role. The buyer records the test as operational-access evidence, then finds that the proposed order form does not name the platform licence holder. The procurement status remains conditional until the named holder, permitted service and relevant approvals are documented. The demonstration stays useful without being overstated.
| Question | Evidence record |
|---|---|
| Who contracts with the buyer? | Legal entity and signed service scope |
| Who holds the platform rights? | Named holder and inspectable entitlement evidence |
| What can this customer do? | Role permissions and tested operations |
| What remains conditional? | Approval owner, required evidence and decision date |
Implementation checklist
- Identify every entity in the supply relationship.
- Match the proposed use to current entitlement evidence.
- Test the customer's actual role rather than a supplier-only superuser.
- Keep financial-service permissions and launch conditions separately owned.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- MetaQuotes: MetaTrader 5 licensing and broker deploymentwww.metatrader5.com
- FCA: applying for authorisation and confirming permissionswww.fca.org.uk
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.
