Skip to content
XBaseTech
Available

XBase AML Screening

Sanctions, PEP and adverse media screening

Screening against sanctions lists, PEPs, watchlists and adverse media, with risk scoring, continuous monitoring and case management.

Request DemoTalk to an Engineer
AML ScreeningLIVE
  1. 01List managerDownload, parse, version and diff lists from their sources.
  2. 02Matching engineName normalisation, phonetic and fuzzy matching, secondary field verification.
  3. 03Scoring and policyConfigurable thresholds and rules by customer segment.
  4. 04Case managementReview queue, decision, rationale, four-eyes principle.
  5. 05Integration layerREST API, webhooks and batch screening interfaces.

Product Overview

AML Screening

What it is

XBase AML Screening screens individuals and legal entities against sanctions lists, politically exposed person (PEP) lists, internal watchlists and adverse media sources; it turns matches into a risk score and presents them to the compliance team as cases.

The problem it solves

Two mistakes are costly in sanctions screening: missing a true match and turning every similar name into an alert. The engine evaluates transliteration and fuzzy name matching together with secondary fields such as date of birth, country and identifiers; the result is a score whose rationale is visible.

Who it is for

Built for banks, payment institutions, crypto asset platforms subject to MASAK and international sanctions regimes, and for RegTech providers delivering compliance services.

Core Features

Core Features

  • Sanctions Lists

    UN, EU, OFAC, HMT and national lists; automatic updates and version tracking.

  • PEP

    Categorised screening of politically exposed persons, relatives and close associates.

  • Watchlists

    The institution's own black and grey lists; import and management UI.

  • Adverse Media

    Screening news sources for crime, fraud and sanctions-related content.

  • Risk Scoring

    Configurable scoring by match strength, list type and customer profile.

  • Continuous Monitoring

    The existing customer base is re-screened automatically on list updates.

  • Case Management

    Review, decision, rationale and four-eyes approval for the compliance team.

  • Alert Management

    Alert prioritisation, assignment and SLA tracking.

  • Audit Logs

    Every screening, match and decision is recorded immutably.

  • API Integration

    Connects to onboarding and transaction flows through REST API and webhooks.

Modules

  • Sanctions
  • PEP
  • Watchlists
  • Adverse Media
  • Risk Scoring
  • Continuous Monitoring
  • Case Management
  • Alert Management
  • Audit Logs
  • API Integration

How It Works

How It Works

  1. 01

    Screening request

    Person or entity data is sent via API before onboarding or a transaction.

  2. 02

    Matching

    Name normalisation, transliteration and fuzzy matching; verification against secondary fields.

  3. 03

    Scoring

    Candidate matches become a risk score; those under the threshold close automatically.

  4. 04

    Case

    Matches above the threshold reach the compliance team as cases; decision and rationale are recorded.

  5. 05

    Continuous monitoring

    Affected customers are re-screened on list changes; new matches raise alerts.

Architecture

Architecture

The system separates list management, the matching engine and case management into distinct services. List versions and screening results are stored together, so any historical screening result can be reproduced along with the list version it was based on.

AML ScreeningLIVE
  1. 01List managerDownload, parse, version and diff lists from their sources.
  2. 02Matching engineName normalisation, phonetic and fuzzy matching, secondary field verification.
  3. 03Scoring and policyConfigurable thresholds and rules by customer segment.
  4. 04Case managementReview queue, decision, rationale, four-eyes principle.
  5. 05Integration layerREST API, webhooks and batch screening interfaces.
  • 01

    List manager

    Download, parse, version and diff lists from their sources.

  • 02

    Matching engine

    Name normalisation, phonetic and fuzzy matching, secondary field verification.

  • 03

    Scoring and policy

    Configurable thresholds and rules by customer segment.

  • 04

    Case management

    Review queue, decision, rationale, four-eyes principle.

  • 05

    Integration layer

    REST API, webhooks and batch screening interfaces.

Technologies

  • Node.js
  • TypeScript
  • PostgreSQL
  • Redis
  • Kafka
  • Docker
  • Kubernetes

Integration

Integration

  • REST API

    Versioned, documented endpoints.

  • Webhook

    Event-based, signed notifications.

  • SDK

    Server and client libraries.

Security

Security

  • Encryption

    Personal data encrypted in transit and at rest.

  • Access control

    Role-based access; four-eyes principle on case decisions.

  • Audit logging

    Screening, match, decision and list version are recorded together.

  • Monitoring

    Dashboards for list freshness, screening latency and case SLAs.

  • Data protection

    Retention periods and access requests aligned with KVKK/GDPR.

Use Cases

Use Cases

  • Onboarding screening

    Sanctions and PEP checks at account opening.

  • Ongoing customer monitoring

    Automatic re-screening of the customer base against list changes.

  • Counterparty screening

    Screening the counterparty before a transfer.

Deployment

Deployment

  • Cloud
  • Private Cloud
  • On-Premise
  • Hybrid

Let's talk about AML Screening

For a demo, technical depth or pricing, talk directly to our engineering team.

Request DemoContact Sales