Ongoing AML Monitoring When Watchlists Change
A clean onboarding screen goes stale. Re-screen when lists update, keep the same external id, and send overnight hits to REVIEW.
Read morePractical articles on fraud APIs, AML screening, event monitoring, and launch readiness for regulated products.
A clean onboarding screen goes stale. Re-screen when lists update, keep the same external id, and send overnight hits to REVIEW.
Read moreDenylists fail closed on confirmed-bad identifiers. Allowlists exempt known-good ones. Keep REVIEW in the middle so lists do not become your only policy.
Read moreVPN and proxy detection is a REVIEW signal. Combine it with device history and login velocity instead of declining every privacy-conscious customer.
Read moreMulti-accounting farms bonuses and mule rails. Link one device fingerprint to many customer ids, then REVIEW clusters before you BLOCK a family iPad.
Read moreHow to use device fingerprints, login events, and REVIEW routing to catch ATO without treating every new device as fraud.
Read moreCredential stuffing is leaked passwords at login scale. Count failures per IP and device, pair novelty with velocity, and list confirmed-bad fingerprints.
Read moreWrite velocity rules with an identifier, action, window, and threshold so operations can defend ALLOW, REVIEW, and BLOCK decisions.
Read moreShip fraud policy as three outcomes you can defend. Use scoring to rank the queue, named rules to decide, and REVIEW-first rollouts before you enforce BLOCK.
Read moreOFAC is one sanctions list family. Watchlist screening is the broader control. Build the API workflow for both, and do not treat a possible match as a legal block.
Read moreConnect Naiza webhooks to your case workflow and send investigation feedback back into the API.
Read moreScreen a customer, send AML events, and poll event results using the tenant-scoped externalEventId.
Read moreBuild the event ingest call, include session context, and use the returned decision in your product workflow.
Read moreKYC verifies who the customer is. AML screening checks watchlists. You need both, and an AML API is not a document KYC product.
Read moreAccept the webhook quickly, persist the ids, and make every case update safe to retry so a second delivery does not open a second case.
Read moreWatch screening volume in shadow before you hold activation or payouts. Enforce only after the review queue matches the team you have.
Read moreA practical checklist for shipping fraud decisioning: event coverage, API keys, named rules, webhooks, and the first week of REVIEW.
Read moreHow to structure events, rules, and review decisions so fraud teams can understand why Naiza flagged an action.
Read moreCall sync when the product cannot continue without ALLOW, REVIEW, or BLOCK. Queue the event when operations can look after the fact.
Read moreScreen during onboarding, persist the screening id, and only hold the customer when the result is REVIEW or CONFIRMED.
Read more