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.
Questions 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?
Engineering
- Inputs
- People or entity names and secondary identifiers · Customer names and secondary matching identifiers
- Outputs
- Screening matches, ongoing-screening records, and review audit history · Screening candidates, risk context, and configured case records
- Webhooks
- Not verified in public documentation.
- Decision timing
- No measured latency or contracted response time verified.
- Deployment
- Hosted API · Hosted World-Check One, API integration, or licensed data-file delivery
- Dependencies
- World-Check One API entitlement and API credentials · Use Case Management and Audit mode when retained decisions, rescreening, and batch uploads are required
Verified details 12
- Deployment
Hosted API
Source Checked 2026-09-18 - Dependency
World-Check One API entitlement and API credentials
Source Checked 2026-09-18 - Inputs
People or entity names and secondary identifiers
Source Checked 2026-09-18 - Inputs
Customer names and secondary matching identifiers
Source Checked 2026-09-18 - Outputs
Screening matches, ongoing-screening records, and review audit history
Source Checked 2026-09-18 - Outputs
Screening candidates, risk context, and configured case records
Source Checked 2026-09-18 - Deployment
Hosted World-Check One, API integration, or licensed data-file delivery
Source Checked 2026-09-18 - Connected provider
Dun & Bradstreet
Source Checked 2026-09-18 - Connected provider
IHS Maritime
Source Checked 2026-09-18 - Connected provider
Dun & Bradstreet for ownership verification
Source Checked 2026-09-18 - Connected provider
IHS Maritime for vessel diligence
Source Checked 2026-09-18 - Dependency
Use Case Management and Audit mode when retained decisions, rescreening, and batch uploads are required
Source Checked 2026-09-18
Illustrative contract
An example for your internal adapter. This is not a vendor endpoint, request, or response.
{
"contract": "internal-risk-review/v1",
"vendorId": "lseg-world-check",
"internalCorrelationId": "example-001",
"vendorRecordId": null,
"control": "Risk intelligence",
"evidence": [],
"status": "pending",
"decision": "review",
"requiresHumanReview": true
}Integration limits
- Illustrative internal integration contract. This is not a vendor request, response, endpoint, or SDK example.
- Empty country, deployment, or provider lists mean not verified in this review. A documented country refers to the specific product noted in its source, not universal platform coverage.
- The service uses REST/JSON over HTTPS and publishes a Swagger description. API access is not automatic for non-API customers. The guide recommends v3 for new integrations.
- Dun & Bradstreet is named for UBO verification; IHS Maritime is named for vessel due diligence. These are scoped connections, not proof of included access in every package. Zero Footprint screening turns off persistent features; select it deliberately.
- Zero Footprint screening is a distinct mode with no permanent screening record. Contact locations and source-list geography do not establish product availability.
Sources 3
Source review dates are shown above. Product claims come from public sources. Fit, limits, and evaluation questions are our analysis. This is not a hands-on performance test. Methodology · Changelog