What is sanctions screening?
Sanctions screening compares a person or organization to official restricted-party lists so you can stop or review activity that may involve a sanctioned party before an account is opened or funds move.
How sanctions screening differs from generic AML screening
Sanctions lists are issued by governments and international bodies. A true sanctions hit usually has a higher urgency than a PEP or adverse-media signal. Teams still need match context: which list, which aliases, and which identifiers supported the result.
Where it sits in a product flow
Most teams screen at customer onboarding and again on payment counterparties. Continuous monitoring matters because lists change. The product should store the screening identifier so operations can reconstruct why a hold or review happened.
How Naiza applies sanctions screening
Naiza’s AML screening API includes sanctions sources alongside other watchlists in one request path. Use the AML product page for source names and the API docs for request and result fields. Do not treat a possible name match as proof that a party is sanctioned.
Frequently asked questions
Short answers written so search and answer engines can cite them.
What is a sanctions screening API?
A sanctions screening API accepts a name or entity and returns structured matches against restricted-party lists so your application can allow, review, or stop a workflow.
Is OFAC screening the same as sanctions screening?
OFAC is one widely used United States sanctions source. Sanctions screening often includes additional lists such as UN and EU sources. Confirm coverage on the product page.
Can sanctions screening run in real time?
Yes. Onboarding and payment flows typically need a synchronous result. Naiza is designed for that request-and-decide pattern, with review routing when the match is uncertain.