Knowledge Base

Knowledge BaseeIDAS / QWAC Certificates

eIDAS Citizen Certificate Validation: What to Expect During Validation

Updated on May 29, 2026

Overview

This article explains how Citizen eIDAS Certificate Validation works, what information is verified, and what applicants can expect during the validation process.

Common Questions This Article Answers

What is eIDAS Citizen Certificate Validation?

What information is validated for an eIDAS Citizen Certificate?

Why is video-based identity verification required?

What actions are required from me during validation?

What should I expect if additional verification is needed?

What Is eIDAS Citizen Certificate Validation?

It is a structured verification process designed to confirm the identity and legitimacy of an individual requesting a certificate under the eIDAS Regulation.

How eIDAS Citizen Certificate Validation Works

The process uses multiple assurance levels including contact verification, request authentication, video-based identity verification, and document integrity review.

What Information Is Verified During Validation

Contact Information (verified email or phone)

Certificate Request Authentication

Identity Verification using video-based verification (Driver licenses are not accepted)

Additional Email Verification

Document Integrity Review

What to Expect During Validation

Sign and return the Subscriber Agreement

Complete additional email verification if requested

Complete video-based identity verification

Respond to validation calls or emails

Track progress in the Validation Manager

Additional Notes

Certain eIDAS certificates require a Qualified Signature Creation Device (QSCD).

For the Sectigo Citizen Qualified Certificate QSCD the private signing key is generated and stored on a secure hardware device (token) rather than in software. This additional protection is required to help prevent unauthorized use of the certificate and to meet platform and industry security requirements.

The secure device ensures that:

The private key cannot be copied, exported, or extracted

Only authorized use of the certificate is possible

Signed software can be trusted as coming from the verified organization

Once validation is complete, the private key is provisioned onto the secure token and shipped to the customer. Once received the customer collects the email certificate via the collection email and imports it into the token. https://www.sectigo.com/knowledge-base/detail/Sectigo-eIDAS-Qualified-Certificate-Installation-on-SafeNet-eToken

This secure storage model helps protect users from malicious software and strengthens trust in signed applications.

Use Cases