How to Integrate an AML Screening API Without Slowing Onboarding

AML screening works best when the product treats it as a decision service, not a separate back-office task. Send the minimum reliable customer identity fields at onboarding, store the screening id, and route only REVIEW or CONFIRMED outcomes to operations.

Integration Flow

• Collect a legal name and your own stable externalId before calling the API.
• Add date of birth, nationality, aliases, and document identifiers when available.
• Persist the returned screening id so support and compliance teams can reconcile the decision.
• Avoid blindly retrying POST calls after upstream timeouts; reconcile the outcome first.

POST /api/v1/aml/screen
x-api-key: naiza_api_sk_live_...

{
  "inputName": "John Michael Smith",
  "externalId": "cust_123456",
  "entityType": "INDIVIDUAL",
  "inputDob": "1985-04-12"
}

Handle Results

Treat AUTO_CLEAR as the low-friction path. REVIEW means the match needs investigation. CONFIRMED means your workflow should stop or hold the action until the compliance outcome is recorded.

Read the AML API reference or talk to Naiza when you are mapping onboarding holds.