AML platform in Saudi Arabia

AML screening, events, and cases in Saudi Arabia

Screen names against watchlists, send AML events for money movement, and work alerts as cases in the dashboard — including a SAR record your team can file and download. Hosted in KSA. A match is a review signal, not a legal block.

5
Watchlist sources
2
Screen and events APIs
Cases
Dashboard workflow

Screen every name against every list

A single API call submits the name and returns a classified result after comparing it against all five watchlist sources simultaneously. No daisy-chaining, no per-source billing.

  • OFAC SDN US Treasury Specially Designated Nationals
  • UN Consolidated List Security Council sanctions & asset freezes
  • EU Financial Sanctions European financial sanctions database (FSD)
  • Dow Jones PFA2 PEPs, watchlists & adverse media coverage
  • OpenSanctions Aggregated official watchlists and PEP registries
POST /api/v1/aml/screenREVIEW
{
  "id": "scr_abc123",
  "externalId": "cust_123456",
  "decision": "REVIEW",
  "listsHit": ["OFAC_SDN"],
  "matches": [
    {
      "watchlistEntityId": "we_987",
      "score": 92,
      "classification": "STRONG",
      "matchedName": "John Michael Smith",
      "source": "OFAC_SDN"
    }
  ]
}

REVIEW is a possible match for your workflow, not a legal determination.

The full AML loop in one product

Screening is the start. Events use the AML API. Cases and SAR records are dashboard work for your investigators.

  1. API

    Screen names

    POST /api/v1/aml/screen returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context from the five watchlists.

  2. API

    Monitor AML events

    POST /api/v1/aml/events for payments and counterparty changes. Statuses stay CLEAR or ALERTED — separate from screening classes.

  3. Dashboard

    Work cases

    Alerts and possible matches open cases in the Naiza dashboard. Assign an investigator, review the timeline, and resolve or escalate.

  4. Dashboard

    File a SAR record

    From a case, file a SAR with a reference number, an audit log, and a downloadable document. This is not SAFIU e-filing.

Built for every workflow

From onboarding screens to event alerts, cases, and SAR records

Customer Onboarding Screening

Screen new customers at the point of onboarding before account creation or KYC approval. Get an instant classification so your team acts only on genuine matches.

Transaction Counterparty Checks

Screen counterparties on every payment or wire transfer in real-time. Automatically flag transactions where the beneficiary or originator appears on a watchlist.

Ongoing list monitoring

Re-screen your existing customer base as watchlists are updated. Receive alerts when a previously cleared customer appears on a newly published sanctions list.

AML event monitoring

Send payments, instrument changes, and counterparty updates to POST /api/v1/aml/events. Matching rules return ALERTED; the API does not pause fulfillment.

Case management

Open cases from alerts or screenings in the Naiza dashboard. Group the customer timeline, assign an owner, and record the outcome.

SAR records

File a SAR from a case when policy requires it. Naiza stores the reference, audit entry, and downloadable document. Regulator e-filing stays in your process.

How it works

How name screening works — four steps from submit to classification

01

Submit Name

Send a name (individual or entity) via the API. Optionally include date of birth, nationality, or identifier fields to improve match accuracy.

02

Normalize & Match

Names are transliterated, normalized, and matched using fuzzy logic to handle spelling variations, aliases, and transliteration differences across scripts.

03

Score Against Watchlists

Each candidate match is scored against all five data sources simultaneously. Match confidence, source weight, and entity type are factored into the final score.

04

Get Classified Result

The API returns a classification—AUTO_CLEAR, REVIEW, or CONFIRMED—along with the matched entity details, source, and confidence score for your compliance workflow.

Possible classifications returned by the API

AUTO_CLEARNo match found
REVIEWPossible match — investigate
CONFIRMEDConfirmed watchlist hit

Five authoritative data sources

All screened simultaneously in a single API call — no per-source fees

OFAC SDN

US Treasury
Sanctions

The US Office of Foreign Assets Control Specially Designated Nationals list. Covers individuals, companies, and vessels subject to US financial sanctions.

UN Consolidated

United Nations
Sanctions

The UN Security Council Consolidated List of individuals and entities subject to measures such as asset freezes, travel bans, and arms embargoes.

EU Financial Sanctions

European Union
Sanctions

The EU Financial Sanctions Database (FSD) maintained by the European Commission, covering EU restrictive measures and autonomous sanctions.

Dow Jones PFA2

Dow Jones
PEP & media

Politically Exposed Persons, relatives and close associates, watchlist subjects, and adverse-media entries from the licensed Dow Jones Risk & Compliance feed.

OpenSanctions

Open Source
Aggregated

An aggregated dataset of official sanctions lists, PEP registries, and related watchlists. Coverage follows the OpenSanctions collections Naiza syncs.

5
Watchlist sources in one API call
Updated as sources publish new data

AML platform explained

Build screening, events, and case work into the customer journey

Naiza gives an API-first path for screening names and sending AML events, plus dashboard cases for investigators. A possible match is still a review signal, not a final compliance decision.

Sanctions and watchlist screening

Screen people and organizations, keep the returned match context, and send uncertain results to a documented review process.

AML event monitoring

Send payments and counterparty changes to the AML events API. Preserve identifiers for audit and investigation.

Case management

Open cases from alerts or screenings in the Naiza dashboard. Assign an owner and record the outcome against the customer timeline.

SAR records

File a SAR from a case with a reference number, audit log, and downloadable document. This is not SAFIU e-filing or a typology TM suite.

Example AML screening request

Send a name you already collected. The API returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context for your review workflow.

POST /api/v1/aml/screen
curl -X POST https://api.naiza.ai/api/v1/aml/screen \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "inputName": "John Michael Smith",
    "externalId": "cust_123456",
    "entityType": "INDIVIDUAL",
    "inputDob": "1985-04-12",
    "inputNationality": "GB"
  }'
ResponseREVIEW
{
  "id": "scr_abc123",
  "externalId": "cust_123456",
  "decision": "REVIEW",
  "listsHit": ["OFAC_SDN"],
  "matches": [
    {
      "watchlistEntityId": "we_987",
      "score": 92,
      "classification": "STRONG",
      "matchedName": "John Michael Smith",
      "source": "OFAC_SDN"
    }
  ]
}

Example AML event request

Send a payment or counterparty change. The API returns CLEAR or ALERTED. Cases and SAR records are dashboard work, not this endpoint.

POST /api/v1/aml/events
curl -X POST https://api.naiza.ai/api/v1/aml/events \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "eventName": "payment.completed",
    "eventCategory": "TRANSACTION",
    "externalEventId": "aml_evt_ext_123",
    "customer": {
      "externalId": "user_123456",
      "email": "user@example.com"
    },
    "sourceReportedAt": 1672520400,
    "metadata": {
      "amount": 99.99,
      "currency": "USD"
    },
    "custom_fields": {
      "counterparty_country": "US"
    }
  }'
ResponseALERTED
{
  "status": "ALERTED",
  "alerts": [
    {
      "id": "aml_alert_123",
      "severity": "HIGH",
      "summary": "Counterparty matched a sanctions rule"
    }
  ]
}

AML screening, events, and cases FAQ

Clear answers for product, engineering, risk, and compliance teams evaluating Naiza AML.

What is AML screening?

AML screening checks customers, businesses, counterparties, and transactions against sanctions, politically exposed person, and other risk data so compliance teams can identify potential matches for review.

What can the Naiza AML API do?

The API screens individuals and entities and accepts AML events for customers and counterparties. Screening returns AUTO_CLEAR, REVIEW, or CONFIRMED. Events return CLEAR or ALERTED.

Does an AML match always mean a customer should be blocked?

No. A possible name or watchlist match is a risk signal, not a final legal conclusion. Teams should apply their own compliance policy, review the supporting match data, and document the final decision.

How is AML screening integrated?

A server sends an authenticated request to the Naiza AML screening endpoint, stores the screening identifier, and routes the returned status into an automatic-clear, manual-review, or escalation workflow.

What are AML events?

AML events are activity you send to POST /api/v1/aml/events, such as a payment or counterparty change. Poll GET /api/v1/aml/events/:externalEventId for CLEAR or ALERTED. ALERTED means a rule matched; pause fulfillment only if your own policy says so.

Does Naiza include case management?

Yes, in the Naiza dashboard. Alerts and possible matches can become cases so investigators can assign work, review the customer timeline, and record an outcome. Cases are not a public API endpoint.

Can I file a SAR in Naiza?

You can file a SAR record from a dashboard case. Naiza stores a reference number, writes an audit entry, and lets you download the document. It does not e-file to SAFIU or replace a dedicated transaction-monitoring typology suite.

What this AML product does not do

  • It is not document KYC, selfie verification, or OCR identity proofing. Screen the name you already collected.
  • A possible match is a review signal, not a legal conclusion that the person is the listed party.
  • It is not a full transaction-monitoring typology suite and not a SAFIU e-filing channel. Cases and SAR records live in the Naiza dashboard for your investigators.
  • List names we screen are on this page. We do not publish entity counts or latency SLAs here.

Ready to add AML screening and monitoring to your compliance stack?

Request access and we will walk through screening, AML events, dashboard cases, and how SAR records fit your process.