LSEG World-Check
Screening intelligence and workflow
World-Check is LSEG’s structured risk intelligence dataset. World-Check One combines that content with screening and review software. Data feeds and APIs can also supply another platform. The core job is risk screening. World-Check One also lists connected identity and UBO checks; confirm each provider and package.
Our assessment
Strong screening-data and workflow scope, with connected identity verification. Add transaction monitoring and underwriting separately.
Best fit and limitations
A core data and screening candidate for sanctions, PEP, and adverse-risk due diligence. It can be used directly by analysts or as a source within another workflow platform.
- World-Check and World-Check One are different buying choices.
- Risk profiles and connected verification checks produce different evidence. Confirm the provider and scope of each UBO or identity check.
- No reviewed evidence establishes a full AML behavioral monitoring, card fraud, or merchant underwriting system.
Tools 5
World-Check dataRisk intelligence+
- Structured profiles for individuals and entities
- Sanctions, political exposure, and related risk context
World-Check OneScreening and review+
- Customer and third-party screening workflows
- Manage matches and ongoing screening
World-Check One APIEmbedded screening+
- REST/JSON screening integration
- Configurable settings and ongoing monitoring
Connected verification and due diligenceAdditional evidence+
- UBO checks use Dun & Bradstreet data
- Integrated identity checks and EDD reports need separate scope confirmation
Data deliveryBring your own engine+
- Data can support external screening systems
- Confirm format, update schedule, and permitted use
AI capabilities
Screening and matching intelligence
LSEG combines researched risk data with screening technology. Do not equate a match score with a probability that a person is sanctioned.
What to validate
Validate aliases, transliteration, missing birth dates, entity types, and repeat-match suppression using a labelled test set.
Implementation
Integration checklist
- Choose the direct UI/API or a data-feed route into another engine.
- Preserve profile IDs, sources, list versions, and analyst decisions.
- Test update propagation, re-screening triggers, and whether earlier clearances must reopen.
Commercial scope
Quote required. Separate data rights, API volume, monitored population, analyst seats, and delivery options.
Estimate total costQuestions for the demo
- Which datasets, entity types, and jurisdictions are in our subscription?
- How are source changes and corrections delivered?
- What evidence and licensed content may we export to our case system?
Sources 3
Reviewed September 17, 2026. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology