Onboarding vs ongoing AML monitoring
Onboarding screening checks the customer before activation. Ongoing AML monitoring combines transaction monitoring, periodic risk reviews, and re-screening when watchlists change.
| Dimension | Onboarding | Ongoing | Where Naiza fits |
|---|---|---|---|
| When to use | Before you activate the customer | When watchlists change after join | Real-time onboarding checks and automatic list-update re-screening |
| Failure mode | Listed after join, never re-checked | List alerts disconnected from payment activity | List re-screening and full transaction monitoring connected to investigation |
| Together | Necessary | Necessary for a live book | Onboarding, ongoing screening, and transaction monitoring on one platform |
Start with onboarding screening
Screen before account activation, then connect re-screening, risk reviews, and transaction monitoring to the same customer record.
Choose ongoing monitoring if
Use ongoing monitoring for an existing customer base. Naiza supports re-screening on watchlist updates so new matches connect to customer records and investigation cases.
How they work together
Combine real-time screening at signup and payout with ongoing re-screening as watchlists update. Add Naiza’s full transaction monitoring for payment activity and connect the results to the same investigator workflow.
Frequently asked questions
Answers about screening, risk signals, and Naiza integration.
How does onboarding screening connect to ongoing monitoring?
Naiza screens customers before activation, then connects watchlist re-screening, risk reviews, and transaction monitoring to the same customer record and investigation workflow.
How does re-screening work alongside transaction monitoring?
Re-screening checks customer identities against updated lists. Transaction monitoring evaluates payment activity. Naiza connects both to the same customer records and investigation cases.
What should we persist?
Customer external id, screening id, and the decision. That join is how an overnight list hit becomes a case instead of an orphan alert.