Getting Started

Request access

To get a hands on experience on this significant technology, you need to sign up with us.

Please contact our sales team to prepare for the initial setup. The team will support you with preparing environments (test, production) and discussing any regulatory options.

Configuration & Integration

After gaining access to your cidaas instance, the next step is to become familiar with the cidaas Admin Dashboard (our backoffice).
Here you will later configure:

• ID validator settings
• Use-case–specific ID validator modes
• Webhooks
• Themes
• …and more

Note: All configuration steps are thoroughly described in the following chapters.

Once you understand the basic components of the Admin Dashboard, you can begin integrating the ID validator into your own systems and workflows.

A typical high-level integration flow looks as follows:

1. Start Process
   Your backend creates a new ID validation case.
   → The API returns a unique URL.

2. Redirect User
   Redirect the user into the ID validator WebApp via this URL.

3. User Completes the Verification Flow
   The WebApp guides the user through all required verification steps.

4. Webhook Delivery
   The finished status is sent to your webhook endpoint.

5. Fetch Case Result
   Retrieve case result and data.

Note: The detailed configuration and step-by-step integration process are covered in the subsequent chapters. This section provides only a high-level orientation.

Understand Process Flows

Before configuring your ID validator Settings or selecting a verification mode, it is important to understand the individual process steps of the cidaas ID Validator.
Each identity verification consists of several process tasks, some of which can be activated, deactivated, or configured according to your needs.

Core Process Steps

1. Start Process
   Your backend creates a new ID Case using a selected ID validator setting.
   → The API returns a unique URL for the user.

2. Prevalidation (Optional)
   Collection or confirmation of business-context data (e.g., contract number, customer reference).
   These values can be compared with your internal data. Serves as an additional security gate.

3. Document Scan
   The ID validator performs authenticity checks, including:

   • security features
   • MRZ and checksum validation
   • expiry and age rules
   • fraud detection and anomaly analysis

4. Document Data Matching (Optional)
   Compare customer-provided reference values with extracted ID document data.

5. Face Analysis & Liveness
   Capture of a live biometric sample and liveness detection.

6. Face Matching
   Compare the live capture with the portrait extracted from the document.

7. Final Result
   Retrievable via our APIs.

Key properties of the orchestration:

• Consistency: Workflow and checks are centrally enforced per mode.
• Flexibility: Multiple modes and settings can coexist within a tenant.
• Traceability: Every action and transition is logged for support and audits.

What you need to know

• Each step is configurable — you decide which steps are active.
• Verification modes do not enforce process steps technically, but define:
  • typical combinations of security checks
  • a recommended security level
  • alignment with industry standards and legal requirements
• You may operate multiple modes in parallel to fit different business use cases.
• We support you during integration in selecting the most suitable configuration.

ID validator Modes Overview

ID validator modes group common configurations into meaningful bundles.
They define the recommended security level and reflect best practices based on:

• industry standards
• regulatory requirements
• risk considerations
• expected user experience

All process steps remain configurable — except where a mode technically requires a step
(e.g., QES can only be executed in the IdentEidas mode).

Below is an overview of all modes and their classification of process steps.

Mode Cluster	Mode	Pre-Val	Doc Scan	Data Match	Face Scan	Liveness	Face Match	QES	Suggested For
Ident	IdentCard	◯	✔	⭐	❌	❌	❌	❌	Basic document validation
Ident	IdentLight	◯	✔	◯	✔	✔	✔	❌	Non-regulated KYC, fraud prevention
Ident	IdentEidas	⭐	✔	⭐	✔	✔	✔	⭐	eIDAS flows, high assurance, QES
Age Verification	AgeCheckCard	◯	✔	⭐	❌	❌	❌	❌	Simple age checks
Age Verification	AgeCheckLight	◯	✔	◯	✔	✔	✔	❌	Entertainment, gaming, moderate age checks
Age Verification	AgeCheckEssential	◯	✔	⭐	✔	✔	✔	❌	Strict age-controlled scenarios
Onboarding	OnboardingLight	◯	✔	◯	✔	✔	✔	❌	Fintech, marketplaces, conversion-first flows
Onboarding	OnboardingEssential	⭐	✔	⭐	✔	✔	✔	❌	HR, banking, verified communities

Legend

• ✔ Required — technically required for this mode
• ⭐ Recommended — suggested according to standards & best practices
• ◯ Optional — configurable by the customer
• ❌ Not included — not supported for this mode

Notes

• Verification modes reflect security expectations for common business scenarios.
• QES is only available in IdentEidas, therefore marked as Required there and Not included in all other modes.
• We support you during integration to help select the most suitable mode and configuration.