guide

Verify a trading-platform claim without confusing software and authorisation

Build a reproducible platform evidence record that distinguishes the software vendor, broker connection, legal entity and available account products.

By Betsafe Reviews Editorial Team ·

Updated Oct 5, 2026

A claim needs a matching document
  1. Claim
  2. Primary document
  3. What it establishes
A reading framework, not a finding about any specific company.
In this article

A familiar platform logo is a starting point for checking a claim, not proof of the broker's identity or permission. Software can connect to multiple providers, and a financial group can offer different products through different companies. A useful verification record must establish which connection is offered to which account. It should also distinguish a documented feature from something the reviewer has actually tested.

State the claim narrowly enough to check

Compare 'the brand offers MT4' with 'the UK provider's product page states that eligible live and demo CFD accounts can connect to MT4'. The second statement identifies geography, product and account mode. Capital.com's UK MT4 page contains that kind of eligibility detail. It is stronger documentary evidence than a logo in a global footer, while still remaining a provider disclosure rather than an independently tested connection.

State the claim narrowly enough to check
Record fieldQuestion to answer
Contracting entityWhich company would serve this account?
Product and accountCFD, investment account, demo or another branch?
Platform routeNative app, web interface or external connection?
Availability boundaryCountry, device, account status or instrument restrictions?
Evidence typeDocumented, observed in a demo, or tested in a live account?

Trace a connection rather than assuming feature parity

An integration page may explain that the broker account connects inside another charting product. That does not mean every feature of either product is available through the connection. Capital.com's TradingView page explicitly asks users to check executable prices, account status, instrument availability and regional access. A charting subscription, a broker login and a live trading account are separate parts of the arrangement. Do not treat a software vendor's general feature list as the broker's account specification.

Product differences also matter within a proprietary platform family. Saxo's UK overview distinguishes a trading platform from an investment-focused interface. A shared brand name does not establish that both expose the same FX instruments. If the evidence only documents stocks and funds for one interface, record that limit rather than filling in the missing Forex availability from another product page.

Handle mismatches as evidence gaps

When a navigation item names a platform but the linked document concerns another region, keep both observations. Record the starting URL, destination, page title, entity and check date. Do not silently change the research scope to whichever destination is easiest to read. Equally, a redirect or an unavailable page alone does not prove wrongdoing. The unresolved question is whether the claimed service is documented for the account being assessed.

Keep testing claims honest

Reading download instructions is not installation testing. Opening a demo is not evidence of live order execution or withdrawals. A screenshot can show an interface at one time without proving reliability, security or every supported device. If testing occurs later, its account mode, device, version and observations need their own record. Until then, label functionality as provider-disclosed and leave performance unknown.

Platform familiarity should never replace legal-entity verification or an understanding of leveraged-product risk. Keep the connection evidence beside the licence and contract record, with separate conclusions for each. Inspect the Saxo UK platform distinctions

Article sources