Getting started Integration flow

Getting Started

Request access

To try the cidaas ID validator, you need an active cidaas tenant with the product enabled.

Please contact our sales team for environments (test / production) and regulatory options.

---

Configuration & integration

After access to your cidaas instance, open the Admin Dashboard (backoffice). There you will configure:

• ID validator settings (configurations)
• Use-case–specific verification modes
• Webhooks
• Themes

note

Detailed Admin UI steps are in Prerequisites and the following chapters. This page is the high-level orientation.

High-level flow

1

Start process

Your backend creates an ID validation case. The API returns a unique URL.

2

Redirect user

Send the user into the ID validator WebApp via that URL.

3

User completes verification

The WebApp guides the user through the steps required by the selected mode.

4

Webhook delivery

Status updates are sent to your webhook endpoint.

5

Fetch case result

Retrieve the final result and extracted data via API.

---

Understand process steps

Before you create a configuration or pick a mode, know the building blocks of a case:

Step	Required?	Description
Start process	Always	Backend creates a case with a selected configuration
Prevalidation	Optional*	Confirm business-context data (contract ID, employee number, …)
Document scan	Mode-dependent	Authenticity, expiry/age rules, fraud signals; MRZ checksum/match mandatory only for AgeCheckEssential & OnboardingEssential, otherwise only if the document template has MRZ — see Document requirements
Document data matching	Optional*	Your custom_attributes vs. OCR/MRZ text from the document — see how it works
Face analysis & liveness	Mode-dependent	Live capture and liveness detection
Face matching	Mode-dependent	Live face vs. document portrait
Final result	Always	Available via API / webhook

* Availability depends on the mode. Details: Verification Modes.

Modes define the security envelope

Modes are not free-form templates where every step is freely togglable.
They enforce which checks run and how deep they go. Consent, theme, prevalidation, and data matching are configured on top where the mode allows it.

Orchestration properties:

• Consistency — workflow and checks are enforced per mode
• Flexibility — multiple modes and configurations can coexist in one tenant
• Traceability — actions and transitions are logged for support and audits

---

Verification modes

Modes group security expectations for common scenarios (identity, age, onboarding).

Cluster	Examples	Start here
Ident	IdentCard → IdentEidas	KYC / eIDAS
Age Verification	AgeCheckCard → AgeCheckEssential	Age gates
Onboarding	OnboardingLight / Essential	Signup + context

→ Full matrix, decision guide, retries & result reuse: Verification Modes

---

Next steps

1. Verification Modes — choose the right profile
2. Theming · Configuration · Webhooks
3. Integration Guide