ormuz
Home/Integrations/Sumsub/Nodes/Create applicant (Sumsub)
SumsubHelperBeta

Create applicant (Sumsub)

Creates or reuses the Sumsub applicant associated with an Ormuz subject and preserves a durable mapping between both identities.

Vue d’ensemble

This helper prepares the provider identity required by Sumsub journeys without creating a new Ormuz business object. It guarantees that one subject has a reusable applicant mapping within a given configuration.

Exemple

Before a KYB verification, create or find the applicant linked to the company so the same provider identity can be reused for SDK tokens and status reads.

Parameters 6

extension_config_idRequisref(extension_config:sumsub)
Sumsub configuration in which the applicant must be resolved or created.
subjectRequisobject
Ormuz subject to correlate with Sumsub. Depending on the journey, it may represent a company, contact, or another subject explicitly accepted by the node contract.
level_nameRequisstring
Sumsub level associated with the applicant on creation. It defines the provider scenario used by subsequent verification steps.
onboarding_caseOptionnelOnboarding case
Onboarding case used as correlation context when the subject belongs to an onboarding journey.
scopeOptionnelstring
Ormuz business scope written into correlation metadata to distinguish several checks for the same subject.
metadataOptionnelmetadata
Optional integration metadata attached to applicant creation/correlation without changing the Sumsub decision.

Outputs 3

sumsub_applicantSumsub applicant
Normalized Sumsub applicant, created or reread from the existing mapping.
createdboolean
True when this execution created a new Sumsub applicant; false when an existing unique mapping was reused.
extension_object_mappingextension object mapping
Durable mapping between the Sumsub applicant and Ormuz subject, used for later Sumsub operations.

Behavior

Resolve the subject

Ormuz determines the explicit business identity carried by subject and the optional onboarding context.

Reuse when possible

An existing unique applicant mapping is reread from Sumsub instead of creating a duplicate.

Otherwise create and correlate

When no mapping exists, Sumsub creates the applicant and Ormuz records the durable mapping to the subject.

Limits and responsibilities

  • A Sumsub applicant is a provider verification identity, not a canonical Ormuz company, contact, or compliance check.
  • Creating an applicant is neither KYC/KYB verification nor a compliance decision.
  • Several competing mappings for the same subject are ambiguous and must be fixed rather than arbitrarily selected.