eIDAS-Compliant Identity Verification

SEON's Identity Verification solution supports eIDAS-compliant identity proofing workflows. You can use SEON to satisfy regulatory identity verification requirements under EU eIDAS legislation and related national frameworks for use cases including regulated financial services, qualified trust service providers (QTSPs), digital wallet issuance and age verification.

SEON is certified under ETSI TS 119 461 v2.1.1 (Extended Level of Identity Proofing) and ETSI EN 319 401 V3.1.1 (trust service provider operations), following a conformity assessment by QSCert Slovakia. This certification is valid across all EU member states.

Prerequisites

Before starting your integration:

• SDK integration is required: eIDAS workflows must use SEON's native mobile or web SDK with live camera capture. File upload is not supported.
• SEON configures your compliance settings: eIDAS-specific configuration including LoIP evaluation, injection attack detection, deepfake detection and human-in-the-loop document review is enabled and maintained by SEON's implementation team during onboarding. You do not set these parameters directly.

Tip: Notify SEON after workflow changes: If you add new workflows or modify an existing eIDAS workflow after go-live, contact your SEON implementation team to validate the updated configuration.

eIDAS - Regulation (EU) No 910/2014, as amended by Regulation (EU) 2024/1183 (the European Digital Identity framework) - is the EU framework governing electronic identification and trust services. It defines three Levels of Assurance (LoA) for electronic identification means - low, substantial, and high (Art. 8; criteria in Implementing Regulation (EU) 2015/1502).
LoA applies to an electronic identification means/scheme across its full lifecycle (enrollment, credential management, authentication). Identity proofing is one component of that lifecycle. SEON is certified as an identity-proofing trust service component under ETSI TS 119 461 and reports a Level of Identity Proofing (LoIP). Where a session uses a third-party eID scheme (Path 3), the LoA is returned by that scheme as an input; SEON maps it, binds it biometrically, and writes a LoIP result.
 

You likely need eIDAS-compliant verification if you are:

• A Qualified Trust Service Provider (QTSP) issuing electronic signatures, seals, or attribute attestations
• A regulated financial institution onboarding customers under the EU AML framework at high-risk tiers
• Issuing or relying on European Digital Identity Wallets under eIDAS 2.0
• Operating in regulated gaming or age-restricted markets in Germany (SEON holds a positive KJM assessment for age verification)
• Responding to government or public sector RFPs that require ETSI/eIDAS certification as a technical prerequisite
   

SEON supports three eIDAS-compliant verification approaches. You choose the path that fits your use case and user population; all three can coexist within your SEON integration by setting up the corresponding custom workflows in the Workflow Editor.

Path 1: Document Verification, Selfie & Liveness Detection (Optical)

The user captures their identity document via camera. SEON performs optical document analysis (data extraction, authenticity checks, expiry verification) followed by a liveness selfie with biometric face matching.
Achieves: Extended LoIP
Best for: Standard KYC onboarding, any document type including those without NFC chips, broadest device support.

Learn more about document verification ?
Learn more about selfie and liveness detection ?

Path 2: NFC-Enhanced Document Verification,  Selfie & Liveness Detection

Same as Path 1, with NFC chip reading enabled. When the user's device and document support it, SEON cryptographically verifies the chip and uses the chip-embedded photo for biometric matching, providing stronger document authenticity assurance than optical analysis alone. Devices or documents without NFC support fall back silently to optical-only.
Achieves: Extended LoIP
Best for: High-assurance use cases, banking, government, RFPs requiring chip verification.
Requires: Mobile SDK (iOS 14+ or Android 5.0+ with NFC hardware)

Learn more about NFC verification ?

Path 3: eID-Based Verification,  Selfie & Liveness Detection

Instead of capturing a physical document, the user authenticates through an accredited government-backed eID provider (such as a national digital identity scheme). SEON receives an identity assertion and Level of Assurance from the eID provider, then completes a biometric selfie step for binding.
Achieves: LoA “Substantial”; LoA “High"
Best for: Markets with high eID adoption (Nordics, Baltics, Germany, Netherlands).
Note: Available eID schemes vary by market. Contact your SEON implementation team to confirm availability for your target geography.

Note: Available eID schemes vary by market. Contact your SEON implementation team to confirm availability for your target geography.

For a session to receive a positive eIDAS compliance attestation, all of the following must apply. SEON's implementation team will configure these requirements for your account during onboarding and this section helps you understand what is expected.

Note: File upload is not permitted in eIDAS workflows. Both the camera-capture requirement and injection attack detection are incompatible with file upload. Your workflow must use SEON's SDK with live camera capture enabled.

After every session completes, SEON automatically evaluates whether all required conditions were met and writes a Level of Identity Proofing (LoIP) result to the session record. This result is your machine-readable compliance attestation.

Result values

Key behaviours

The LoIP result is automatic. It runs on every session with no action required from you.

It is immutable so it is written once when the session reaches a terminal status. It does not change if you later update the session outcome manually.

It runs on all terminal statuses, including DECLINED. A declined session will still carry a loip result (typically none), which can be useful for diagnostics.

A session can be APPROVED and still receive loip.result: none if the workflow was not correctly configured (for example, if session video recording was not active). Approval and eIDAS compliance are independent signals.
 

The LoIP result is delivered as a loip object in your existing workflow_execution_finished webhook payload. No changes to existing fields — this is a new top-level addition.

Compliant session example

{
  "event": "workflow_execution_finished",
  "executionId": "exe_abc123",
  "status": "APPROVED",
  "loip": {
    "result": "extended",
    "evaluatedAt": "2026-06-22T10:15:00Z",
    "unmetConditions": []
  }
}

Non-compliant session example

{
  "event": "workflow_execution_finished",
  "executionId": "exe_def456",
  "status": "APPROVED",
  "loip": {
    "result": "none",
    "evaluatedAt": "2026-06-22T10:16:00Z",
    "unmetConditions": [
      {
        "condition": "VIDEO_RECORDING_MISSING",
        "reason": "Session video recording was not enabled or failed to upload"
      }
    ]
  }
}

Possible unmetConditions values

Using the LoIP result for compliance reporting

To generate a compliance report or fulfill an audit requirement, filter your webhook data to sessions where loip.result equals extended (for eIDAS High) or baseline (for eIDAS Substantial). These sessions represent completed identity proofing events that meet the relevant assurance standard.

SDK integration is required

eIDAS workflows must use SEON's native mobile or web SDK with live camera capture. Injection attack detection requires the SDK's Capture Library, which cannot run on file upload flows. This applies to all three paths.

SEON configures the compliance requirements

All eIDAS-specific configuration including the LoIP evaluation, injection attack detection, deepfake detection and human-in-the-loop document review is enabled and maintained by SEON's implementation team. You do not configure these directly. During onboarding, SEON will verify that your workflow meets all requirements before go-live. If you add new workflows or modify an existing eIDAS workflow after onboarding, notify your SEON implementation contact so they can validate the updated configuration.

Learn more: Questions about your eIDAS configuration? Contact your SEON implementation team or speak with an expert.