eIDAS 2.0
Five scenarios spanning public sector, financial onboarding, cross-border verification, and EUDI pilots.
Five scenarios spanning public-sector services, regulated finance, cross-border verification, workforce integration, and member-state pilot programmes.
Customer: A government service (permit office, tax authority, benefits portal) accepting EUDIW PID as the authentication source.
Outcome: Citizen presents their EUDIW PID; verifier checks trust chain + selective disclosure; service receives verified identity claims. Replaces paper-ID submission and DigiD-LoA-High for suitable services.
Customer: A bank or regulated financial institution onboarding customers under eIDAS 2.0.
Outcome: Customer presents PID + qualified attestations (proof of address, tax number). Verifier returns a normalised claim bundle; the bank records verified onboarding evidence for regulatory audit.
Customer: An age-restricted online service (alcohol, nicotine, gambling) with customers across EU member states.
Outcome: Customer presents the derived age_over_18 claim from any member-state's EUDIW wallet. Verifier accepts all conformant member-state issuers. Zero PII collected; regulator-satisfying proof of verification.
Customer: An enterprise using EUDIW PID as the authentication source for workforce applications (alongside traditional SSO).
Outcome: Verifier is wired behind Hub. Users can log in via EUDIW wallet; claims flow through as OIDC attributes. Works alongside Okta/Azure AD federation; policy decides which users authenticate via which path.
Customer: A member-state pilot programme testing wallet issuance + relying-party acceptance end-to-end.
Outcome: Pilot issuers publish via Credential Issuer; the verifier accepts their credentials; the programme measures presentation success rates, latency, and conformance-test outcomes with production-ready tooling.
Request access to connect the eIDAS Verifier to your relying party.