SumsubHelperBeta

Fetch applicant status (Sumsub)

Rereads the current review status of a Sumsub applicant without creating a new decision or Ormuz compliance check.

Applicant Sumsub

Récupérer le statut applicant (Sumsub)

Applicant status

Vue d’ensemble

This helper is a low-level provider read. It is useful for diagnosing or refreshing an applicant, but standard journeys should prefer Sumsub business nodes that directly wait for and interpret the review decision.

Exemple

An operator wants to understand why an applicant remains pending: reread its Sumsub status without restarting verification.

Parameters 3

extension_config_idRequisref(extension_config:sumsub)

Sumsub configuration from which status must be reread.

sumsub_applicantOptionnelSumsub applicant

Sumsub applicant whose status must be read. Its identifier takes priority when supplied.

applicant_idOptionnelstring

Direct applicant identifier to use when the sumsub_applicant object is unavailable.

Outputs 1

applicant_statusobject

Current normalized Sumsub review-status payload for the requested applicant.

Behavior

The node chooses the identifier from sumsub_applicant when supplied, otherwise applicant_id, then queries Sumsub and exposes the normalized current review status.

Limits and responsibilities

The applicant's raw status is not an Ormuz business route and must not be turned into implicit approval.
This node does not persist a compliance_check; use dedicated Sumsub nodes when you need to materialize a compliance result.
Provide either sumsub_applicant or applicant_id; the applicant object is preferred when already available in the process.