Integrate AML Screening and Event Polling

AML integrations usually need two paths: synchronous screening for customer or entity checks, and event ingest for transaction or counterparty monitoring. Use a stable externalEventId when polling write-back results.

Send an AML Event

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

{
  "eventName": "payment.completed",
  "eventCategory": "TRANSACTION",
  "externalEventId": "aml_evt_ext_123",
  "customer": { "externalId": "user_123456", "email": "user@example.com" },
  "metadata": { "amount": 99.99, "currency": "USD" }
}

Poll the Result

GET /api/v1/aml/events/aml_evt_ext_123

• CLEAR means the event did not create an AML alert.
• ALERTED means the event created one or more alerts.
• HELD means the event is waiting for an AML workflow outcome.
• APPROVED and REJECTED are forward-compatible statuses for downstream write-back.

Open the AML product page for a product overview.