ormuz
Home/Integrations/Sumsub/Nodes/Sync AML result (Sumsub)
SumsubConnecteurBeta

Sync AML result (Sumsub)

Synchronizes the latest active Sumsub AML case for an applicant and materializes the corresponding AML Compliance Check.

Vue d’ensemble

Objectif

This node reads AML details from Sumsub using the applicant already created by a KYC journey or another Sumsub node.

It starts no hosted experience: it rereads provider evidence and materializes the canonical check under its write permission.

aml_check is the main business output for the decision; aml_compliance_check is the canonical object created or reused when the result is terminal.

Quand l’utiliser

  • You already have a sumsub_applicant from sumsub.verify_identity and want detailed AML data.
  • You want to explicitly reread the latest AML case after an extension.sumsub.applicant_reviewed webhook.
  • You want to route a process on a detailed AML result without creating a risk_score.

Parameters 5

extension_config_idRequisref(extension_config:sumsub)
Active Sumsub provider configuration used to call the AML API.
sumsub_applicantOptionnelSumsub applicant
Sumsub applicant to reread. Recommended input after sumsub.verify_identity.
subjectOptionnelContact
Ormuz subject already mapped to a Sumsub applicant. Used when the process does not directly carry sumsub_applicant.
onboarding_caseOptionnelOnboarding case
Onboarding case to attach to the materialized compliance_check.
scopeOptionnelstring
Business scope of the AML check. Default: aml_screening.

Outputs 4

sumsub_applicantSumsub applicant
Sumsub applicant used for the AML read.
aml_caseobject
Raw response of the latest active Sumsub AML case.
aml_checkSumsub aml check
Current AML business result with decision, result, risk labels, hits, and raw response.
aml_compliance_checkOptionnelCompliance check
Persisted AML Compliance Check created or reused when the applicant is mapped to a persisted Ormuz subject and the result is terminal.

Behavior

Resolve the applicant

The node prioritizes sumsub_applicant. Otherwise it searches the provider mapping from subject. applicant_id exists only as an advanced reconciliation parameter.

Read the latest AML case

The node calls the Sumsub AML Case API to retrieve the latest structured data available for the applicant.

Materialize the AML check

The result is translated into aml_check for the business decision, then materialized as a canonical compliance_check with check_type: aml when terminal.

Process example

Applicant Sumsub + contexte métier
Synchroniser le résultat AML (Sumsub)

The node rereads the AML result and materializes the canonical check under explicit permission.