TL;DR: The practical issue is not the certificate itself, but what assurance thresholds now mean for identity verification, compliance, and fraud controls across customer and business onboarding, according to SumSub, whose person and business verification modules have reconfirmed eIDAS 2.0 High Level of Confidence certification, covering Auto Identification, Video Identification, e-ID Verification, KYB Verification and a Fully Automated eMRTD module for regulated onboarding in Europe.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should regulated businesses use eIDAS-certified identity verification in onboarding?
A: Use eIDAS-certified verification as a scoped assurance control for specific onboarding journeys, not as a blanket statement that all identity risk is solved.
Q: Why does high-assurance identity verification matter for compliance teams?
A: Because regulated onboarding decisions must stand up to scrutiny, especially where fraud, AML, and digital trust are linked.
Q: What should security teams check before trusting an automated verification module?
A: Check whether the automation is certified for the exact journey, what documents or signals it reads, how failures are escalated, and whether human review is still required for exceptions.
Practitioner guidance
- Map certification to specific journeys List every onboarding, KYB, and signature path that depends on eIDAS assurance, then verify which ones are covered by the certified modules and which rely on separate controls.
- Separate automation from exception governance Document where Fully Automated verification is acceptable, where manual review remains required, and what evidence is captured when a case fails automated checks.
- Align identity evidence with audit and AML needs Retain the identity artefacts, verification outcomes, and business proof used in regulated onboarding so they can support later audit, AML review, or dispute handling.
What's in the full announcement
SumSub's full article covers the operational detail this post intentionally leaves for the source:
- The exact scope of the eIDAS 2.0 High Level of Confidence certification across Auto Identification, Video Identification, e-ID Verification, and KYB Verification.
- The Fully Automated module details, including how eMRTD reading works without manual agent review in the certified workflow.
- The compliance framing around eIDAS and AML onboarding journeys for regulated businesses operating in Europe.
- The quoted vendor rationale for why this certification matters to regulated customer verification and qualified signature flows.
👉 Read SumSub's certification update on eIDAS 2.0 high confidence verification →
eIDAS 2.0 high confidence certification: what it means for IAM teams?
Explore further
High-assurance verification is now an identity governance requirement, not a UX differentiator. eIDAS 2.0 certification signals that regulated onboarding is being judged against auditable assurance thresholds, not just conversion performance. For IAM and fraud teams, that means verification design has to satisfy compliance, traceability, and risk acceptance at the same time. The practitioner conclusion is that onboarding assurance must be treated as governance infrastructure.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, according to The State of Non-Human Identity Security.
A question worth separating out:
Q: Who should own business verification when KYB supports regulated access decisions?
A: Ownership should sit across identity, compliance, and the business function that relies on the decision, because KYB affects account creation, contractual trust, and downstream risk. If no one owns the evidence chain, the organisation can pass onboarding without being able to defend it later.
👉 Read our full editorial: eIDAS 2.0 high confidence certification raises the bar for IAM