Standalone Sanctions & PEP Checks
Baselayer offers dedicated endpoints for running sanctions and PEP screening independently from Business Search. These are useful when you need to check individual names, run batch screening, or build custom compliance workflows outside of the standard business verification flow. Sanction lists are updated daily. For watchlist screening as part of Business Search, see the Watchlists & Sanctions: Business Search guide. For a deeper understanding of sanctions compliance concepts, see the Watchlists, Sanctions & Compliance Screening guide.When to Use Standalone Checks
Standalone sanctions and PEP endpoints are designed for workflows where you need screening outside of a full Business Search:- Individual KYC — Screening a person’s name (e.g., a beneficial owner or authorized signer) without running a full business verification
- Batch processing — Screening many names at once by uploading a CSV file, such as during periodic rescreening of an existing customer base
- Re-screening existing customers — Running updated checks against current sanctions lists for customers already onboarded
- Custom compliance workflows — Integrating sanctions checks at specific points in your application flow (e.g., before disbursing funds, during periodic reviews)
- Pre-screening — Quick name checks before initiating a full Business Search
Available Endpoints
OFAC Sanctions Check
POST /ofac/searches
Checks a name against OFAC sanctions lists (SDN, SSI, and other OFAC-administered lists).
PEP Check
POST /pep/searches
Checks a name against Politically Exposed Persons databases to identify individuals holding or having held prominent public positions.
The Similarity Threshold
Both standalone endpoints accept asimilarity_threshold parameter that controls how closely a name must match a watchlist entry to be flagged. They also accept limit, the most matches to return (default 1, max 50).
How It Works
The threshold is a value between0.0 and 1.0 (0% to 100% similarity). A name must meet or exceed the threshold to be returned as a match.
- 0.9 (90%) — High precision. Our recommended starting point to limit false positives, while maximizing coverage.
- 0.85 (85%) — Balanced. Catches more name variations and cases with additional words.
- 0.7–0.8 (70–80%) — High recall. Catches more name variations (transliterations, abbreviations, typos) but generates more false positives requiring manual review.
Choosing a Threshold
The default for standalone checks is 0.9 (90%) if nosimilarity_threshold is specified. This provides high precision with fewer false positives. Adjust based on your results:
- If you’re seeing too many false positives (common names flagging unrelated watchlist entries), raise the threshold toward 0.95.
- If you’re in a highly regulated industry and want maximum coverage, lower it toward 0.7 — but expect more manual review.
Reading the Response
Standalone check responses return match results directly.Key Fields
total_matches— Number of matches found. A value of 0 means no matches.matches: Array of individual match records, each containing name, addresses, alternative names, and similarity score.
Identifying Matches
Any response wheretotal_matches > 0 indicates a positive match requiring review. Examine the matches array to understand what matched and assess whether it’s a true positive or false positive.
Implementation Examples
OFAC Sanctions Check
PEP Check
Batch OFAC Screening
For screening many names at once — such as periodic rescreening of an existing customer base — Baselayer provides a dedicated batch endpoint that accepts a CSV file.POST /ofac/searches/batches
Submit a CSV file (max 5MB) with two columns: entity_name and reference_id. The reference_id is your internal identifier for each entity, allowing you to match results back to your records.
Sample CSV: here
similarity_threshold parameter defaults to 0.9 and can be adjusted per batch via query parameter.
Poll GET /ofac/searches/batches/{batch_id} until the state is COMPLETED, then download the results from GET /ofac/searches/batches/{batch_id}/download.
Best Practices
Use standalone checks for individual screening. If you’re verifying a person (not a business), standalone endpoints are the right tool. Don’t run a full Business Search just to check a name. Match your threshold to your risk tolerance. Start at 0.9 and adjust. Highly regulated industries may want 0.7. Always review match details. A positive match doesn’t always mean a true hit. Examine names, addresses, and sanctions programs to distinguish true positives from false positives caused by common names. Log everything. Record the name checked, threshold used, timestamp, and full response. Regulators may require proof of screening. Combine with Business Search. Standalone checks are complementary to — not a replacement for — Business Search watchlist screening. Use standalone checks for individual names and edge cases; use Business Search for full business verification workflows. Set up ongoing monitoring. Standalone checks are point-in-time. For continuous screening, use Portfolio Monitoring to automatically rescreen your customer base when watchlists are updated.Next Steps
- Learn the fundamentals: Read Watchlists, Sanctions & Compliance Screening for compliance concepts
- Business Search screening: See Watchlists & Sanctions: Business Search for integrated screening
- Set up monitoring: Use Portfolio Monitoring to continuously screen your customer base
- API reference: POST /ofac/searches | POST /ofac/searches/batches | POST /pep/searches