KYC, KYB & Identity · Use case

Screen for sanctions, PEP and adverse media

Scope this use caseTalk to us

Short answer

Screening checks customers against sanctions lists, politically exposed persons and negative news, at onboarding and whenever lists or customers change. Quality is measured by catching the real matches while keeping false positives low enough for your team to review.

What this use case is

Screening checks customers against sanctions lists, politically exposed persons and negative news, at onboarding and whenever lists or customers change. Quality is measured by catching the real matches while keeping false positives low enough for your team to review.

Who builds this

Any regulated fintech
Payment providers
Crypto platforms
Lenders

What your customer sees

  1. 1Nothing, usually — screening runs in the background; a match may trigger a request for more information

How KYC, KYB & Identity solves it

1

Customer data sent at onboarding

Customer data sent at onboarding

2

Matched against selected lists with fuzzy matching

Matched against selected lists with fuzzy matching

3

Potential matches scored

Potential matches scored

4

Alerts reviewed by your team

Alerts reviewed by your team

5

Decision recorded with rationale

Decision recorded with rationale

6

Customers re-screened when lists update

Customers re-screened when lists update

7

Changes trigger new alerts

Changes trigger new alerts

Want to have

  1. Coverage of the lists your footprint requires
  2. Configurable matching
  3. Ongoing monitoring
  4. Alert review tooling
  5. Audit trail
  6. API and batch screening

Optional

  1. Adverse-media with source links
  2. Payment screening in real time
  3. Risk scoring

Design decisions

Monitoring

Onboarding only
Continuous

cost versus expectation and risk.

Matching thresholds

Strict
Balanced

fewer misses versus fewer false positives.

What to put in your RFP

Lists

  • sanctions
  • PEP
  • adverse media
  • update frequency

Matching

  • fuzzy logic
  • transliteration
  • thresholds

Workflow

  • alerts
  • review
  • audit

Integration

  • API
  • batch
  • payments

Commercials

  • per screen and per monitored entity
Add these to an RFP

How to evaluate providers for this use case

  1. 1False-positive rate on your data
  2. 2List update speed
  3. 3Review efficiency
  4. 4Audit export

Pitfalls

  • Thresholds so loose the team drowns in alerts
  • No re-screening when lists change
  • Poor transliteration of names

What providers will ask you

  1. Customer volumes
  2. Markets
  3. Current alert volumes
  4. Review team size

Other Finlane categories that cover parts of this

This use case is solved mainly with KYC, KYB & Identity. These categories cover specific parts of it and can be tendered alongside it.

Fraud & AML Monitoring

Transaction monitoring alongside screening

RegTech & Compliance Ops

Case management and regulatory reporting

Frequently asked questions

Other KYC, KYB & Identity use cases

Onboard consumers with document + selfie

Verify ID documents plus a liveness selfie, with automated decisioning and manual review fallback.

Verify businesses and UBOs

Pull company registry data, map the ownership tree, and screen directors/UBOs against sanctions and PEP lists.

Orchestrate multiple identity vendors

Route each user through the best-fit vendor by geography, risk score or document type — from one integration.

Scope screen for sanctions, PEP and adverse media with KYC, KYB & Identity providers

Scope this use case