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

Sync identity result (Sumsub)

Materializes normalized Sumsub identity evidence as a persisted Ormuz Compliance Check.

Vue d’ensemble

Objectif

Use this node when extension.sumsub.identity_check evidence already exists, for example after a process triggered by a Sumsub event.

The node does not allow provider facts to be rewritten: it materializes the evidence as-is under compliance_check:write and reuses the existing mapping on replay.

Quand l’utiliser

  • To import an already-available Sumsub KYC decision without restarting the User Journey.
  • To make an event-driven process explicit: provider event, then authorized canonical synchronization.

Parameters 5

extension_config_idRequisref(extension_config:sumsub)
Sumsub configuration that produced the evidence.
identity_checkRequisSumsub identity check
Normalized Sumsub identity evidence to materialize.
subjectRequisContact
Persisted Ormuz subject to which the check should be attached.
onboarding_caseOptionnelOnboarding case
Onboarding case to attach to the check.
scopeOptionnelstring
Business scope of the check. Default: identity_verification.

Outputs 4

identity_checkSumsub identity check
Synchronized Sumsub evidence.
selected_routestring
Operational decision from identity_check.decision.
selected_valuestring
Decision value identical to the selected route.
compliance_checkOptionnelCompliance check
Persisted Compliance Check created or reused for terminal evidence.

Behavior

Valider l’evidence

The node verifies Sumsub provenance and the persisted subject to which the check must be attached.

Materialize under permission

Terminal evidence creates or reuses the canonical compliance_check under the node grant.

Rester idempotent

Replay of the same provider object resolves the existing mapping instead of creating a second check.

Process example

Identity check Sumsub + Business object
Synchroniser le résultat d’identité (Sumsub)
Identity check Sumsub + Compliance check

The webhook observes; this node explicitly synchronizes the provider fact into the Ormuz model.