What is list management?
List management is the operational control of blocklists and allowlists: adding an identifier with a reason, applying it on later events, and removing it when the case is closed.
What belongs on a list
Confirmed-abusive device fingerprints, IPs, emails, or customer ids after investigation. Not entire countries. Not every REVIEW. Product copy includes blocklist management and whitelist override.
How Naiza applies it
Events can hit listed identifiers and return BLOCK (or an allowlist override). Keep a reason trail. Confirm the current list APIs in docs. Pair lists with scoring so unknown traffic still has a path.
Governance
Allowlists expire. Denylists need an owner. An allowlisted stolen session is worse than a false REVIEW. See allowlist vs denylist.
Frequently asked questions
Short answers written so search and answer engines can cite them.
What is a fraud list management API?
It lets you create and apply allowlists and denylists of identifiers so decisions stay consistent across login, payment, and payout events.
Should analysts add every chargeback to a denylist?
No. One dispute can be legitimate. List after confirmation, or use a customer-level REVIEW rule first.
Is a watchlist the same as a fraud denylist?
No. Watchlists are sanctions/PEP/media sources in AML. Fraud lists are your own abusive identifiers. Both can route to REVIEW or BLOCK, with different legal meaning.