Risk screening

PEP and Sanctions Screening

Screen customers, entities, and counterparties against global sanctions, PEP, watchlist, and enforcement data, with configurable matching and ongoing monitoring.

Last updated

What this covers

  • Global sanctions lists (OFAC, UN, EU, HMT)
  • Politically exposed persons (PEP)
  • Adverse media & enforcement
  • Real-time & batch screening
  • Ongoing monitoring
Neoclassical stone columns on the facade of a civic government building

Screening in production for

  • CSC
  • EFICA
  • EML
  • Groupama
  • MEO
  • Riskified
  • Securiport
  • Tanzania Commercial Bank
  • Tradeview Markets
  • Zappit
  • AMP
  • BancABC
  • BMG
  • BTC
  • CMC Markets
  • Coop
How it works

From a thousand sources to one decision.

  1. Your teamConfigureBefore any checkThresholds, fuzzy logic and secondary identifiers, set to your risk appetite.
  2. AutomatedScreenWhole bookEvery customer against 1,000+ sanctions, PEP and watchlist sources.
  3. AutomatedCandidate matchesName hitsEvery name that touched a list, before any scoring is applied.
  4. AutomatedScored and filteredAbove thresholdWeak coincidental matches drop out below your threshold.
  5. Your teamReview and decideAnalyst queueEvidence, assignee and a decision history a regulator can inspect.
2 your team3 automated
A thousand sources do not mean a thousand alerts. The shares are illustrative, but the shape is not: the value of the middle stages is how much they remove from the last one, which is the only stage that costs analyst time.
The real problem

False positives are the cost, not the coverage.

Screening against more sources is the easy part. The work is what arrives afterwards, and an analyst hour spent clearing a coincidental name match is the real price of a screening programme. Matching is yours to tune, so weak matches drop out before they reach a queue rather than after someone has already read them.

How to reduce false positives without missing genuine risk
  • Set match thresholds per customer segment, not one setting for the whole book
  • Fuzzy matching for transliteration, phonetic variants and non-Latin scripts
  • Secondary identifiers such as date of birth and country narrow a name-only hit
  • Every cleared match keeps its evidence, so a tuning decision is defensible later
Capabilities

What you get.

Configurable matching

Thresholds, fuzzy logic and secondary identifiers are yours to set, not ours.

Real-time and batch

Screen a single customer at onboarding through the API, or run your entire book in batch. Both paths use the same lists and matching logic.

Ongoing monitoring

Re-screen customers automatically as sanctions and PEP lists change, so a cleared customer is reviewed again the moment a new listing affects them.

Case management & audit trail

Every match carries its evidence, its assignee and the decision that closed it.

API integration

Embed screening directly into onboarding and core systems through the MemberCheck API, so checks run inside your product.

Scope

What you can screen.

  • Individuals and sole traders
  • Entities and organisations
  • Beneficial owners and directors
  • Counterparties and third parties
  • Your existing customer base
1,000+
Global watchlists screened
<1s
Average screening response
24h
Watchlist refresh cycle
195
Countries covered
Assurance

What your security review will ask for.

99.98%
System uptime
<24h
Average integration time
24–48h
Signed to production account
<1s
Average screening response
  • ISO/IEC 27001:2022 certifiedISO/IEC 27001:2022Information security management, independently audited.
  • ISO/IEC 27701:2019 certifiedISO/IEC 27701:2019Privacy information management, extending ISO 27001.
  • GDPR — EU General Data Protection RegulationGDPRPersonal data handled to EU standards, wherever you operate.
  • DORA — EU Digital Operational Resilience ActDORAOperational resilience for EU financial entities and their vendors.
Questions

Common questions.

Can I tune matching to cut false positives?

Yes. You set matching thresholds, fuzzy-matching sensitivity, and secondary identifiers such as date of birth or country to your own risk appetite, so weak coincidental matches are filtered out while genuine hits still surface. Match rules are yours to set, not fixed.

Can screening run in real time via API, or in batch?

Both. Screen a single customer at onboarding through the API for a sub-second response, or run your entire book in batch. Both paths use the same lists and the same matching logic.

Does MemberCheck re-screen customers after onboarding?

Yes. Ongoing monitoring re-screens your customer base automatically as sanctions and PEP lists change, so a previously cleared customer is reviewed again the moment a new listing affects them.

How many sources do you screen against, and how often are they updated?

MemberCheck screens against over 1,000 sanctions, PEP, and watchlist sources, refreshed on a 24-hour cycle, covering 195 countries.

What counts as a politically exposed person?

FATF Recommendation 12 splits PEPs three ways: foreign PEPs, who hold a prominent public function in another country; domestic PEPs, who hold one at home; and people entrusted with a prominent function by an international organisation. Relatives and close associates are treated alongside them. Jurisdictions apply the categories differently, so a customer in scope in one country may not be in another.

Do you screen relatives and close associates as well as the PEP?

Yes. A PEP's family members and known close associates carry related risk, because they are the obvious route for holding assets at one remove. They are screened as part of the same check rather than as a separate exercise.

Which sanctions regimes are covered?

Screening covers the major consolidated regimes including OFAC in the United States, the United Nations Security Council list, the European Union consolidated list and HM Treasury in the United Kingdom, alongside national lists and watchlists. Coverage by country is set out on the country coverage pages.

How do you handle non-Latin names and transliteration?

Names transliterated from Arabic, Cyrillic, Chinese or Japanese scripts rarely match character for character, which is where a name-only check fails. Fuzzy matching handles spelling variants, phonetic similarity and alternative transliterations, and secondary identifiers narrow what remains.

What should an audit trail contain for an inspection?

A regulator asks what was screened, what matched, what the analyst concluded and on what evidence. Each match keeps its source list, its score, the identifiers used, the assignee and the decision that closed it, so the record answers the question without reconstruction.

Can different customer segments have different thresholds?

Yes. A single threshold across the whole book either buries analysts in low-risk noise or sets the bar too high for higher-risk segments. Matching is configured per segment so the setting follows the risk rather than the average.

See MemberCheck in action.

A short walkthrough of screening, verification and ongoing monitoring in one platform, set to the thresholds and jurisdictions your programme actually uses.