LSEG: market data, FX workflows, screening and licensing

LSEG supplies several distinct layers of a brokerage’s infrastructure: market data for pricing and analysis, institutional FX trading workflows, and risk-screening tools. Its data business offers real-time streams, historical observations and reference datasets through hosted, on-premises and hybrid arrangements. The useful starting point is the intended job—dealer desktop, application feed, historical research or customer-facing distribution—because each requires a different product and entitlement.[1][10][17]

Streaming feeds: similar names, different delivery

Historical research has its own choice of granularity. Tick History offers instrument-based requests, venue-level bulk delivery, cloud access and packet-capture data. The catalogue reaches back to January 1996, but that is the earliest overall coverage rather than a promise for every instrument. Normalized records and raw packets answer different questions: the former simplify cross-market analysis, while packet data retain details useful for reconstructing feed behaviour. Requested dates, fields, timestamp basis and instrument history therefore belong in the dataset specification.[6]

Machine Readable News supplies structured stories, headlines and metadata from Reuters and other publishers, with streaming and historical routes. Optional analytics include measures such as sentiment, relevance and novelty. Headlines Direct is a separate low-latency news route delivered at the New York trading centre. A text archive, a sentiment dataset and an event feed should not be treated as interchangeable inputs: they differ in what information arrives, when it becomes available and how a historical strategy can reconstruct that moment.[15]

The DataScope Select REST API covers instrument lists, report templates, schedules and extracted files. It can automate an overnight or on-demand data process, including retrieval and processing of the resulting files. LSEG expressly describes API availability as covering most, rather than all, content available through the GUI. An implementation should therefore establish that the chosen report and fields are exposed before replacing a manual process with an API job.[8]

FX execution protocols

Matching’s published controls include credit limits and a prime-broker kill switch. Those controls make credit arrangements part of the operating setup: a visible price and a technically working connection do not establish that a participant can trade with every counterparty. LSEG’s aggregation service similarly combines access routes, while external venue participation and the customer’s trading relationships remain separate elements of the deployment.[11][12]

Trade Notification standardizes trade-event messages from LSEG and third-party venues for downstream processing. It supports a common connection into post-trade systems and includes affirmation/manual-approval workflows. This can reduce the need for a different interface from every execution source. The service described is messaging and workflow infrastructure; settlement movement, reconciliation and the treatment of rejected or amended trades still depend on the systems and counterparties receiving those messages.[13]

Risk screening alongside the trading stack

World-Check One’s API can create screening cases, retrieve potential matches, support remediation and enable ongoing monitoring. The web interface can be used by investigators while the brokerage automates submissions from its own system. This supports a division of work between automatic routing and human decisions: a returned name match is information for assessment, rather than an automatic instruction to accept or reject a customer. The API also provides reporting and audit functions.[17]

World-Check Verify is a different screening architecture. LSEG describes it as a stateless API on AWS that does not retain customer personally identifiable information, with regional hosting options. That distinction matters when a firm wants screening embedded in onboarding or payment flows while retaining its own case records. The claim concerns the Verify service; it should not be extended to all World-Check products or to logs and records kept by the brokerage’s integration.[19]

LSEG has no single price covering this collection of products. DataScope Select describes consumption pricing based on the instruments and fields required; the inspected public page does not supply a numerical enterprise tariff. Data subscriptions, desktop access and execution charges consequently need to be read as separate commercial components.[7]

Taker transaction fees are nil. Ordinary maker spot costs USD10 per million; swaps depend on tenor; forwards add both components. Options cost USD12 per million for Silver/Gold, USD10 for Platinum. Gold applies by default. After the first RFQ trade its monthly minimums are: months 0–6, zero; 6–12, USD1,250; 13–18, USD2,500; 19–24, USD3,750; thereafter, USD5,000. The published month-six overlap requires clarification. Fixings, algos, SEF activity and discounts have separate provisions. These are not complete deployment costs.[21]

World-Check One’s online-package terms give purchased points a 12-month life, with no carry-forward or refund for unused points. Usage above the allocation is charged in the following quarter at the rate in the order form. The dashboard can show consumption and alerts at 50%, 70% and 90%. These conditions describe the online-only packages; they should not be assumed to be the commercial basis of a negotiated enterprise/API arrangement.[20]

World-Check One does not give every web-interface subscriber API access automatically. Its quick-start guide also distinguishes the customer-facing caseId from the internal caseSystemId used by API operations, and tells API clients to retain the mapping. That is a concrete migration and reconciliation requirement: an integration must be able to reconnect an internal customer record, a screening case and the investigator’s view without assuming that both identifiers are interchangeable.[18]

The architecture choices above also determine where a change has to be tested. A feed-field change can affect a pricing engine; a symbology change can break an extract; an altered entitlement can stop a downstream display. For a brokerage deployment, the acceptance scope should join representative instruments and data consumers to the operating team that owns each failure mode. No common implementation duration, recovery objective or migration-export entitlement was established across these separate products.

The group privacy statement distinguishes LSEG acting as a controller from processing carried out on a customer’s instructions, and directs some products to separate information. It is therefore not a substitute for a product-specific data-processing agreement. The contracted service, data categories, processing locations, retention and support access need to be established for the actual deployment, particularly where screening records or user communications are involved.[31]

LSEG’s support structure separates product/content help from account administration and billing. MyAccount includes resources for invoices, payment information, software and service administration, while the Learning Centre offers training. These routes are useful for assigning incidents to the appropriate team: a data-content query is different from a permission problem, an invoice dispute or a brokerage’s own application defect. Product pages for Real-Time – Optimized and Full Tick advertise round-the-clock support, but response, restoration and service-credit commitments require the relevant service agreement.[25][3][4]

The FX complaints summary covers services including FXall, Matching, PriceStream, Order Book, Conversational Dealing and Callouts. It provides a case reference and handler, targets acknowledgment within three business days and a final response within 30 business days of receipt, and describes notification where more time is needed. These are the published complaint-handling targets for that process, rather than a production outage recovery SLA or a universal complaints policy for every group product.[27]

MyAccount also distinguishes a DataScope price challenge from general help. That matters when the issue is the content of an observation rather than its delivery: the appropriate escalation needs the instrument, valuation date or timestamp and the affected field, while an infrastructure incident needs the connection and service details. The existence of a public support route does not establish access to every authenticated tool, which was not tested here.[26]

Spot instruments sit outside the EU and UK MTFs. The selected transaction route determines the applicable venue rules.[21]

The UK MTF rulebook also separates the operator from the counterparties: LSEG is not a party to platform transactions, and payment and settlement remain the participants’ responsibility. It says those transactions are not covered by a compensation scheme and that LSEG does not assume responsibility for a participant’s default. This is a substantive boundary for a broker assessing counterparty exposure; access to a regulated venue does not itself eliminate that exposure.[23]

Internal use, redistribution and derived data

LSEG’s redistribution guidance treats internal use differently from delivering content to customers through trading displays, analytics, dashboards or AI-generated outputs. It also addresses derived data: transforming the original information so that it cannot readily be reconstructed does not automatically remove licensing obligations. A broker publishing prices or calculations to its customers therefore needs explicit rights for that use, as well as the relevant third-party permissions. An API credential demonstrates access, not unrestricted downstream publication rights.[14]

For screening, product access and regulatory accountability are separate. World-Check supplies data and workflow functions; the brokerage sets its risk rules, resolves potential matches and retains the evidence needed for its own decisions. A service’s screening capability should not be described as a certification that every resulting account-opening decision satisfies every jurisdiction’s requirements.

The LSEG website identifies its parent as London Stock Exchange Group plc, registered in England and Wales under company number 05369106, with registered address 10 Paternoster Square, London EC4M 7LS. Product contracts may involve different group operating companies. The parent identity and website address therefore help establish the group, while the service agreement establishes the contracting supplier.[29]

The Workspace Office add-in licence is one example of product-specific contractual layering: it refers to the relevant group services contract and covers that software component. It does not supply universal prices, termination rights or data-export terms for the entire LSEG portfolio. No single public document inspected here establishes those terms across Workspace, feeds, screening and execution services.[30]

Operator

London Stock Exchange Group plc and product-specific group operating companies

Service scope

Broker-relevant market data, research and reference information, institutional FX execution workflows and World-Check screening. Group businesses have distinct products, operators and contracts.

Customer types

Brokerages; Banks; Asset managers; Institutional trading firms; Financial technology businesses

Delivery

Hosted; On premises; API; Managed service; Hybrid

Pricing publication

Public and quoted pricing

Platforms

Workspace; FXall; Spot Matching; Forwards Matching; DataScope Select; World-Check One; World-Check Verify

Integrations

Real-Time APIs; DataScope Select REST API; RTDS; Microsoft applications; Trade Notification; World-Check APIs

Pricing scope

Public FXall RFQ tariffs coexist with product-specific data and workflow quotations and registration-gated screening package prices.

Implementation

Deployment depends on the selected feed, desktop, venue or screening service. API entitlements, connectivity, downstream distribution rights and operating responsibilities are separate requirements.

Support

LSEG product support, MyAccount and training resources; product-specific support terms. A separate published FX complaints process provides acknowledgment and response targets.

Permissions and regulatory scope

Irish FX MTFs appear on the Central Bank of Ireland venue list. The UK MTF operator and oversight are described in LSEG documentation. These findings do not extend financial permissions to every data or screening product.

Provider metadata checked 20 Oct 2026Source 29Source 1Source 2Source 10Source 17Source 21Source 25Source 24Source 22

Benchmarks are a different type of price

WMR publishes closing and intraday FX benchmarks, including spot, forwards and NDFs. Its London closing rates use a 4pm London-time fixing on weekdays, and its data are distributed through LSEG products, feeds and authorized redistributors. A benchmark supports valuation or comparison at a defined time; it is not an executable bid/ask promise to a broker’s customer. Coverage, methodology and permitted use should therefore be matched to the valuation task rather than substituted for a live trading price.[16]

October 2026 historical-data update

On 14 October 2026, LSEG announced work with NVIDIA to accelerate Tick History analysis using cuDF with Polars. The practical change concerns historical-data processing and access in analytical workflows. The announcement’s speed comparisons are vendor benchmarks, not measured performance for this profile or a promise about a broker’s live execution latency. Existing dataset permissions still matter; faster analysis does not expand redistribution rights.[33]

What the public record leaves open

The principal unresolved commercial details are the selected dataset and fields, exchange permissions, redistribution audience, connection and desktop charges, API/package entitlements, and negotiated support, renewal and exit provisions. Some are intentionally customer-specific; World-Check’s online points calculator also requires registration. The public FXall fee schedule provides a useful concrete tariff, but it cannot price the complete deployment. These gaps are local to the relevant commercial arrangement rather than evidence that the published services are unavailable.