Validate verifiable-credential structures against EUDI wallet profiles under eIDAS 2.0. Checks PID, QEAA, and EAA credentials against the ARF (Architecture Reference Framework) requirements — format compliance, mandatory claim set, proof-of-possession, trust-anchor, and selective-disclosure conformance. Returns an acceptance-readiness determination and gap list. Hard deadlines: Nov 2026 member-state wallet rollout · Dec 2027 obliged-entity acceptance. Chains into ART-04.
AP2 ExportChains: ART-04eIDAS 2.0 · Nov 2026Obliged entities: Dec 2027Zero PII · Client-Side
🔒 All credential fields are synthetic. Do not enter real identity data. Validation is performed entirely in your browser — no data is transmitted. Use placeholder or generated values for all PII fields.
⚠ Educational/simulation only. Validation rules are based on the EUDI Wallet Architecture Reference Framework (ARF) v1.4.0 (2024), eIDAS 2.0 Regulation (EU) 2024/1183, and published ETSI/CEN technical standards for verifiable credentials. Acceptance obligations for specific obliged-entity types (credit institutions, payment institutions, telecoms) are subject to member-state implementation acts and Commission delegated acts not yet fully published. All regulatory citations are real and sourced.
Credential parameters
PID is the core identity credential. QEAA requires accredited issuer. EAA/non-qualified EAA are sector-specific.
SD-JWT VC and mdoc are the two EUDI ARF v1.4 mandatory formats. JWT-VC and LDP-VC are optional.
Determines Dec 2027 acceptance obligation scope under eIDAS 2.0 Art. 45f.
Selective disclosure support
Proof of possession
Revocation mechanism
Issuer accreditation (QEAA)
Synthetic credential claims (no real data)
Readiness score & gap analysis
0%
eIDAS 2.0 deadline status
Chain to ART-04 — Agent identity & authorization attestation
→ Open in ART-04Export the artifact below, then carry it into ART-04 to validate KYA-OS agent delegation credentials referencing the same EUDI wallet identity