Screen names
POST /api/v1/aml/screen returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context from the five watchlists.
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.
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.
{ "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.
Screening is the start. Events use the AML API. Cases and SAR records are dashboard work for your investigators.
POST /api/v1/aml/screen returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context from the five watchlists.
POST /api/v1/aml/events for payments and counterparty changes. Statuses stay CLEAR or ALERTED — separate from screening classes.
Alerts and possible matches open cases in the Naiza dashboard. Assign an investigator, review the timeline, and resolve or escalate.
From a case, file a SAR with a reference number, an audit log, and a downloadable document. This is not SAFIU e-filing.
From onboarding screens to event alerts, cases, and SAR records
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.
Screen counterparties on every payment or wire transfer in real-time. Automatically flag transactions where the beneficiary or originator appears on a watchlist.
Re-screen your existing customer base as watchlists are updated. Receive alerts when a previously cleared customer appears on a newly published sanctions list.
Send payments, instrument changes, and counterparty updates to POST /api/v1/aml/events. Matching rules return ALERTED; the API does not pause fulfillment.
Open cases from alerts or screenings in the Naiza dashboard. Group the customer timeline, assign an owner, and record the outcome.
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 name screening works — four steps from submit to classification
Send a name (individual or entity) via the API. Optionally include date of birth, nationality, or identifier fields to improve match accuracy.
Names are transliterated, normalized, and matched using fuzzy logic to handle spelling variations, aliases, and transliteration differences across scripts.
Each candidate match is scored against all five data sources simultaneously. Match confidence, source weight, and entity type are factored into the final score.
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
All screened simultaneously in a single API call — no per-source fees
The US Office of Foreign Assets Control Specially Designated Nationals list. Covers individuals, companies, and vessels subject to US financial sanctions.
The UN Security Council Consolidated List of individuals and entities subject to measures such as asset freezes, travel bans, and arms embargoes.
The EU Financial Sanctions Database (FSD) maintained by the European Commission, covering EU restrictive measures and autonomous sanctions.
Politically Exposed Persons, relatives and close associates, watchlist subjects, and adverse-media entries from the licensed Dow Jones Risk & Compliance feed.
An aggregated dataset of official sanctions lists, PEP registries, and related watchlists. Coverage follows the OpenSanctions collections Naiza syncs.
AML platform explained
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.
Screen people and organizations, keep the returned match context, and send uncertain results to a documented review process.
Send payments and counterparty changes to the AML events API. Preserve identifiers for audit and investigation.
Open cases from alerts or screenings in the Naiza dashboard. Assign an owner and record the outcome against the customer timeline.
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.
Send a name you already collected. The API returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context for your review workflow.
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" }'
{ "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" } ] }
Send a payment or counterparty change. The API returns CLEAR or ALERTED. Cases and SAR records are dashboard work, not this endpoint.
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" } }'
{ "status": "ALERTED", "alerts": [ { "id": "aml_alert_123", "severity": "HIGH", "summary": "Counterparty matched a sanctions rule" } ] }
Clear answers for product, engineering, risk, and compliance teams evaluating Naiza AML.
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.
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.
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.
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.
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.
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.
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.
Request access and we will walk through screening, AML events, dashboard cases, and how SAR records fit your process.