Checking for screening hits
Checking for hits after screening a customer
You can determine whether a customer has any hits after screening using different approaches, depending on whether the screening was conducted asynchronously or synchronously.
Checking for hits after asynchronous screening
Webhooks (recommended)
- Set up a webhook of type
WORKFLOW_COMPLETEDusing the Create a Webhook API. - Once the screening workflow completes, an update will be sent to the configured webhook URL.
- Refer to the
customer-screening.step_output.screening_resultfield in the webhook payload to determine if any hits were found (HAS_PROFILES).
Polling
- After using the Create and Screen (Asynchronous) API, you’ll receive a
workflow_instance_identifierin the response. - Use this identifier to poll the Get Status and Result of Onboarding API.
- When the customer-screening step is complete, the
customer-screening.step_output.screening_resultfield in the response will indicate whether any hits were found (HAS_PROFILES).
Checking for hits and AML types after synchronous screening
- For Create and Screen (Synchronous) requests, the screening result is included directly in the API response.
- Refer to the
customer-screening.step_output.screening_resultfield to see if any hits were found (HAS_PROFILES). - Refer to the
customer-screening.step_output.aml_typesto see the AML types of the hits. AML types includes:SANCTIONFITNESS-PROBITYWARNINGSPEP_CLASS_1PEP_CLASS_2PEP_CLASS_3PEP_CLASS_4ADVERSE_MEDIAADVERSE-MEDIA-V2-PROPERTYADVERSE-MEDIA-V2-FINANCIAL-AML-CFTADVERSE-MEDIA-V2-FRAUD-LINKEDADVERSE-MEDIA-V2-NARCOTICS-AML-CFTADVERSE-MEDIA-V2-VIOLENCE-AML-CFTADVERSE-MEDIA-V2-TERRORISMADVERSE-MEDIA-V2-CYBERCRIMEADVERSE-MEDIA-V2-GENERAL-AML-CFTADVERSE-MEDIA-V2-REGULATORYADVERSE-MEDIA-V2-FINANCIAL-DIFFICULTYADVERSE-MEDIA-V2-VIOLENCE-NON-AML-CFTADVERSE-MEDIA-V2-OTHER-FINANCIALADVERSE-MEDIA-V2-OTHER-SERIOUSADVERSE-MEDIA-V2-OTHER-MINOR\
Updated 8 days ago