SumsubRouteurBeta

Screen AML (Sumsub)

Triggers a server-to-server Sumsub AML screening for an Ormuz subject without hosted user experience, then waits for the provider decision.

Business object

Contrôler AML (Sumsub)

Approuvé

Rejeté

Relance

Revue requise

Applicant Sumsub

Aml check Sumsub

Vue d’ensemble

Objectif

This node covers AML-only: no WebSDK, no interactive document verification, only a provider check on a Sumsub applicant.

It creates or reuses the Sumsub applicant linked to the Ormuz subject, marks the check as check_type: aml, then waits for extension.sumsub.applicant_reviewed.

If the applicant is already approved, the node triggers a Sumsub AML recheck. Otherwise it requests an applicant check on the configured AML level.

aml_check is the main business output and drives approved, rejected, retry, and review_required routes. A terminal decision is materialized directly in aml_compliance_check under explicit permission.

Quand l’utiliser

You need to check PEP, sanctions, or watchlist without a user identity journey.
You want to screen a contact or company already known in Ormuz.
You want to rerun an AML check on an already-approved applicant.

Parameters 6

extension_config_idRequisref(extension_config:sumsub)

Active Sumsub provider configuration used to create the applicant and trigger screening.

subjectRequisContact

Ormuz subject to screen. The node accepts a persisted contact or company.

level_nameRequisstring

Name of the Sumsub level configured for AML-only screening.

onboarding_caseOptionnelOnboarding case

Onboarding case to record on the future aml_compliance_check.

scopeOptionnelstring

Business scope of the AML check. Default: aml_screening.

reasonOptionnelstring

Reason sent to Sumsub when the node requests review. Default: aml_screening.

Outputs 6

sumsub_applicantSumsub applicant

Sumsub applicant used for AML screening.

aml_checkSumsub aml check

AML business result. aml_check.decision drives node routes.

selected_routestring

Route selected from aml_check.decision.

screening_statusstring

Ormuz-side request status. requested means screening was requested and the node is waiting for the provider decision.

screening_modestring

applicant_check for an AML-level check, aml_recheck for an already-approved applicant.

aml_compliance_checkOptionnelCompliance check

Persisted AML Compliance Check created or reused on resumption with a terminal decision.

Behavior

Prepare the applicant

The node creates or reuses a Sumsub applicant for the Ormuz subject, with ormuz_check_type: aml in technical metadata.

Trigger screening

When the applicant is already approved, the node calls Sumsub AML recheck. Otherwise it requests an applicant check on the configured AML level.

Wait for the decision

The node waits for extension.sumsub.applicant_reviewed correlated to the applicant. On resume, aml_check routes the process and aml_compliance_check is materialized when the decision is terminal.

Process example