Website information and service scope

Using the service catalogue

The pages describe technology components and project requirements. Reading the catalogue or using its terminal does not open a trading account, purchase a platform licence or approve an integration. A production deployment requires a separately confirmed scope and the permissions of the relevant parties.

Written project terms

Before commissioning work, confirm the contracting entity, deliverables, exclusions, payment schedule, recurring costs, acceptance checks and support responsibilities. Pricing, deployment dates and service levels should be stated in the applicable written proposal or agreement. Diagrams and example interfaces do not establish an availability commitment.

External dependencies

Trading platforms, liquidity counterparties, payment providers, verification services and infrastructure suppliers have their own access and commercial requirements. Confirm the actual components and approvals needed for your project. The presence of a technology name in the catalogue does not demonstrate an endorsement or a partnership.

Changes and questions

Use the current service pages and contact channels to clarify a requirement before relying on it in a project plan. Any agreed change to a production scope should identify its impact on cost, timing, access and acceptance. These website notes explain the catalogue; they are not a substitute for the project contract.