Screen names
POST /api/v1/aml/screen returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context from global sanctions, PEP, and watchlist sources.
Full transaction monitoring and AML screening on one platform. Screen names against 1,100+ global sources, monitor money-movement events, and investigate alerts in the dashboard. Assign cases, record outcomes, and prepare SAR records on one platform hosted in Saudi Arabia.
Submit a person or organization in a single API call. Naiza screens against global sanctions, PEP, and watchlist sources and returns a classified result with match evidence.
{ "id": "scr_abc123", "externalId": "cust_123456", "decision": "REVIEW", "matches": [ { "watchlistEntityId": "we_987", "score": 92, "classification": "STRONG", "matchedName": "John Michael Smith" } ] }
Send a name and customer identifiers to receive a screening classification and supporting match details.
Full transaction monitoring connects AML event rules, counterparty screening, alerts, investigations, cases, and SAR reporting workflows.
POST /api/v1/aml/screen returns AUTO_CLEAR, REVIEW, or CONFIRMED with match context from global sanctions, PEP, and watchlist sources.
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.
Turn a case into a SAR record and keep the full history in one place.
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 so your application can apply its hold or escalation policy.
Open cases from alerts or screenings in the Naiza dashboard. Group the customer timeline, assign an owner, and record the outcome.
Prepare SAR records straight from investigation cases, ready for your reporting workflow.
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 using the matched source, entity type, and match confidence. The result includes evidence for investigation.
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
Limaz delivers fraud and AML technology implementation, connecting Naiza’s screening, transaction monitoring, and investigation workflows to your systems and operations.
Sanctions, political exposure, watchlists, and adverse media in one screening workflow.
Screen customers and counterparties against international sanctions data. Review matches with entity details and source evidence.
Identify politically exposed persons during onboarding and ongoing customer screening. Keep the match context for risk review.
Screen for relatives and close associates of politically exposed persons to assess customer relationships and connected risk.
Review adverse-media matches with source context to support customer risk assessment and investigation.
Check people and organizations against global watchlist records and route matches into your investigation workflow.
AML platform explained
Connect name screening and AML event monitoring to investigator cases. Review match evidence, assign work, track outcomes, and prepare SAR records in the Naiza dashboard.
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.
Prepare SAR records from investigation cases, with the evidence and history attached.
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", "matches": [ { "watchlistEntityId": "we_987", "score": 92, "classification": "STRONG", "matchedName": "John Michael Smith" } ] }
Send a payment or counterparty change. The API returns CLEAR or ALERTED. Investigate the resulting alerts through dashboard cases and SAR records.
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.
REVIEW routes a possible match to investigation. Naiza provides match details and source context so your team can verify the identity, record the outcome, and apply its configured policy.
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. Your application applies the configured hold or escalation policy.
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.
Investigators prepare SAR records directly from dashboard cases, with the alerts, evidence, and decisions already attached.
Request access and we will walk through screening, AML events, dashboard cases, and how SAR records fit your process.