Overview
This guide shows you how to validate individuals (persons) and organizations (companies) against sanctions lists and PEP databases using the KYC API. This is essential for compliance screening, onboarding customers, and monitoring business relationships.Quick Example
Validating Individuals (Persons)
Basic Person Check
For basic screening, provide the person’s full name. Additional information improves accuracy:Person Fields
| Field | Required | Description | Example |
|---|---|---|---|
full_name | Yes* | Full name of the person | ”John Doe” |
document_id | No | Government-issued ID number | ”12345678” |
document_type | No | Type of document | ”Passport”, “CI”, “DNI” |
nationality | No | Two-letter country code (ISO 3166-1) | “US”, “UY” |
birth_date | No | Date of birth (YYYY-MM-DD) | “1985-03-15” |
identifiers or document_id provided
Validating Organizations (Companies)
Organizations are validated using their legal name or tax identification numbers:Checking Multiple Lists
You can check against multiple lists simultaneously for comprehensive screening:Available Lists
| List Name | Description | Supports |
|---|---|---|
ofac | OFAC Sanctions List (US Treasury) | Persons, Organizations |
un | UN Security Council Sanctions | Persons, Organizations |
eu | EU Consolidated Financial Sanctions | Persons, Organizations |
senaclaft_uy | SENACLAFT Uruguay (PEP & Sanctions) | Persons |
Search Types
Choose the matching strategy based on your needs:| Search Type | Description | Use Case |
|---|---|---|
exact | Exact name matching | High precision, strict matching |
fuzzy | Approximate string matching | Handle typos and variations |
token | Word-based matching | Find partial name matches |
composite | Combined strategy (default) | Balanced precision and recall |
llm_enhanced | LLM-filtered matching | Maximum precision with semantic filtering |
Common Use Cases
1. Customer Onboarding
Validate new customers before account creation:2. Batch Validation
Validate multiple entities at once:3. Continuous Monitoring with Watchlists
For ongoing monitoring, create a watchlist instead of one-time checks:Error Handling
Always handle potential errors in your implementation:Best Practices
-
Provide Complete Information: Include
nationality,birth_date, anddocument_idwhen available to improve matching accuracy. -
Use Multiple Lists: Check against multiple sanctions lists (
ofac,un,eu) for comprehensive screening. -
Choose Appropriate Search Type: Use
compositefor balanced results,exactfor strict matching, orllm_enhancedfor maximum precision. - Handle Errors Gracefully: Always implement error handling and timeouts in your integration.
- Consider Watchlists: For entities that need ongoing monitoring, use watchlists instead of repeated API calls.
- Respect Rate Limits: The API has rate limits (1000 requests per 5 minutes per IP). Implement retry logic with exponential backoff if needed.
Related References
- List Check API Reference - Complete API documentation
- Watchlists Overview - Continuous monitoring solution
- Validate Cryptocurrency Wallets - Guide for wallet validation
- Adverse Media Screening - Check for negative news