SumsubHybrid user-action routerBeta

Verify business (Sumsub)

Verifies a company with Sumsub through automatic KYB or a hosted experience, then materializes the compliance decision.

Business object

Vérifier l’entreprise (Sumsub)

Approuvé

Rejeté

Relance

Revue requise

Applicant Sumsub

Business check Sumsub

Vue d’ensemble

Objectif

This node verifies a platform.company as a Sumsub company applicant, with externalUserId equal to the company ID.

In auto mode, the node triggers server-to-server checking and waits for extension.sumsub.applicant_reviewed without creating a hosted screen.

In journey mode, it opens the Sumsub experience for Full KYB journeys requiring documents, questionnaire, or representative participation.

business_check is the main business output: it carries the KYB decision and drives approved, rejected, retry, or review_required routing.

A terminal KYB result is materialized directly in kyb_compliance_check with check_type: kyb. Detected beneficial owners or directors may still be output in associated_companies as contact and contact_role drafts.

Quand l’utiliser

You need to verify a company during onboarding with registry data, company documents, corporate AML, or UBO checks configured in Sumsub.
You want one business node covering automatic KYB and KYB with human interaction without exposing applicant/token/webhook plumbing.
You want the process to decide which UBO drafts to persist after reconciliation.

Parameters 5

extension_config_idRequisref(extension_config:sumsub)

Active Sumsub provider configuration.

subjectRequisCompany

Ormuz company to verify. The node requires a persisted company.

level_nameRequisstring

Sumsub KYB level to apply.

verification_modeOptionnelstring

auto triggers server-to-server KYB; journey opens the Sumsub WebSDK.

onboarding_caseOptionnelOnboarding case

Onboarding case to attach to the compliance check.

Outputs 5

sumsub_applicantSumsub applicant

Sumsub company applicant. Provider correlation remains carried by sumsub_applicant.

business_checkSumsub business check

KYB business result. business_check.decision drives approved, rejected, retry, and review_required routes.

selected_routestring

Route selected from business_check.decision.

kyb_compliance_checkOptionnelCompliance check

Persisted KYB Compliance Check created or reused after a terminal Sumsub decision.

associated_companiesOptionnelobject[]

Contact and role drafts for UBO/director/representative discovered by Sumsub. Persistence remains explicit.

Behavior

Create or reuse the company applicant

The node relies on extension_object_mappings to reuse the Sumsub applicant linked to the company, otherwise creates it with type: company and fixedInfo.companyInfo.

Trigger the check

In auto mode, Ormuz requests Sumsub review through the API. In journey mode, WebSDK is presented to the representative.

Resume on the decision

The process waits for extension.sumsub.applicant_reviewed correlated to sumsub_applicant.id.

Route and materialize the check

The Sumsub decision produces business_check, routes the process from business_check.decision, then materializes kyb_compliance_check; any associated-company drafts remain separate.

Process example