Skip to the operations

Identity verification

Sumsub in a decision flow.

A Connection node calls Sumsub mid-decision with the credentials your own contract issued. Whatever comes back is data the rest of the flow can read, branch on, and keep in the decision's trace.

Category
Identity verification
Type
Integration
Authentication
hmac
Test environment
Production host only

What a flow can call

4 operations, each one a step you can place on the canvas.

  1. POST/resources/applicants

    Create an applicant profile

    Creates the applicant record used by the verification workflow.

  2. POST/resources/accessTokens/sdk

    Generate a WebSDK or MobileSDK token

    Issues a short-lived token for Sumsub's applicant-facing SDK.

  3. GET/resources/applicants/$data.sumsub_applicant_id/status

    Get an applicant review status

    Reads the current verification decision. A transport 200 only means the lookup worked; use reviewStatus and reviewResult.reviewAnswer in the response to decide whether the applicant passed.

  4. GET/resources/applicants/$data.sumsub_applicant_id/one

    Get an applicant profile

    Retrieves the full applicant profile and information obtained during verification.

Where it sits in the decision

A provider call is a node, not a side effect.

The call runs where the policy needs it — after the cheap checks that might make it unnecessary, before the rules that depend on it. Calls that do not depend on each other run together rather than in sequence.

Because it is part of the run, the response is part of the record. When someone asks why an applicant was declined months later, what Sumsub returned at the time is in the trace, not re-fetched from a service whose answer has since changed.

  • 01Add Sumsub as a connection, with your credentials.
  • 02Place a Connection node and choose the operation.
  • 03Read the response in the rules, tables and branches that follow.
  • 04Test the whole path in Sandbox before it carries live traffic.

Ready when you are

Wire Sumsub into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs