Skip to main content

Predefined Workflows

The platform ships with ready-made workflows covering the most common verification needs. A Company can use them as-is, or fork one as the starting point for a custom flow. Each maps to a business scenario described under Use Cases.

The catalog​

WorkflowCapturesEvaluatesProduces
idv_onboarding_v1 — Identity VerificationDocument + selfie + livenessAuthenticity, OCR, face match, liveness, anti-fraud, optional duplicity checkNew / merged / updated Customer, or reject / block
doc_update_v1 — Personal Data UpdateDocument + selfie + livenessSame as idv, matched 1:1 against a known CustomerUpdated Customer
biom_authentication_v1 — Biometric AuthenticationSelfie + liveness1:1 face match against a known CustomerAuthenticated / rejected
age_check_v1 — Age VerificationSelfie, then document if neededAge estimate from the selfie; age from the document's date of birth as fallbackAge verified / rejected
identification — Biometric IdentificationSelfie + liveness1:N face search against the Customer watchlistIdentified / not found / rejected
document_enrollment — Document EnrolmentDocument onlyAuthenticity, OCRDocument enrolled / rejected

Tenants with palm verification enabled can add the palm steps to a forked onboarding workflow (both-palms enrolment) or build a palm authentication workflow from single_palm_capture and palm_matching.

Choosing a workflow​

  • Unknown person, full identity proof → idv_onboarding_v1.
  • Known Customer, confirm it's them → biom_authentication_v1.
  • Unknown person, recognize by face → identification.
  • Known Customer, refresh their data → doc_update_v1.
  • Just an age gate → age_check_v1.
  • Document data now, identity later → document_enrollment.

Tier awareness​

The same workflow definition works on any data tier — the platform applies only the actions the tier supports at runtime. For example, duplicity check and watchlist actions are skipped when 1:N is not enabled, without changing the workflow.

See also​