⬡ OpenChainGraph · Wave B · eudi-wallet · linear · §4 artifact (ART-13)
OpenChainGraph · eIDAS 2.0 · EUDI Wallet · 5 Steps

EUDI Wallet Acceptance Chain

Regulation (EU) 2024/1183 (eIDAS 2.0) requires all EU member states to offer an EUDI Wallet to every citizen by 31 December 2026 (Article 5a) and mandates that regulated financial institutions performing Strong Customer Authentication must accept EUDI Wallet credentials by approximately December 2027 (Article 5f). This chain covers the full acceptance workflow: attribute attestation mapping (PID + QEAAs) → KYC flow redesign for wallet-based onboarding → RP registration obligations → ART-13 credential-acceptance readiness check (§4) → overall EUDI readiness scoring and gap analysis.

eIDAS 2.0 · Regulation (EU) 2024/1183 ART-13 · OpenChainGraph §4 Artifact Art. 5a: Wallet available Dec 2026 Art. 5f: SCA acceptance ~Dec 2027 Client-side · Zero PII Wave B
⚠ Key deadlines

Art. 5a — EUDI Wallet availability: All EU member states must offer an EUDI Wallet to citizens and residents by 31 December 2026. Art. 5b — Acceptance by public authorities: Member state public bodies must accept EUDI Wallet credentials by early 2027. Art. 5f — Regulated FI SCA acceptance: Banks, payment institutions, and other regulated entities performing SCA must accept EUDI Wallet credentials by approximately December 2027. Relying Party registration: RP registration processes are being established by member states — start the registration runway now to avoid last-minute compliance risk.

01
T489 · Original Tool
EUDI Attribute Attestation Mapper
Map the attributes your service needs (name, date of birth, address, tax ID, account number, professional credentials) against the EUDI Wallet's available attestation types — Person Identification Data (PID), Qualified Electronic Attestations of Attributes (QEAAs), and non-qualified Electronic Attestations of Attributes (EAAs). Identify which attributes can be requested from the EUDI Wallet vs. which still require legacy identity verification channels. The attribute mapping is the foundation for all subsequent KYC flow and RP registration decisions.
Pre-Dec 2026 T489 PID · QEAA · EAA Feeds: KYC flow design
Open T489 ↗
02
T490 · Original Tool
EUDI KYC Flow Designer
Design your wallet-based customer onboarding flow — how a user presents their EUDI Wallet credential to complete KYC, SCA, and consent. Covers the OpenID4VP (OpenID for Verifiable Presentations) presentation request flow, selective disclosure of attributes, proximity and remote presentation flows, and the PSD3/SCA integration path where the EUDI Wallet replaces the current factor-combination requirement. Produces a KYC flow diagram and a credential-request specification for your RP integration.
T490 Consumes: T489 attribute map OpenID4VP · selective disclosure · SCA · PSD3
Open T490 ↗
03
T491 · Original Tool
EUDI Relying Party Registration Checker
Check your RP registration obligations: member state-specific registration requirements, the EU Trusted List for Relying Parties, the wallet-unit attestation verification obligation, and the notice-of-intent timeline for your operating jurisdiction(s). Identifies which registration steps are already complete, which have dependencies (e.g., qualified certificates), and your estimated registration runway. The RP registration output feeds directly into the ART-13 credential readiness assessment.
T491 Consumes: T490 KYC flow spec EU Trusted List · RP registration · wallet-unit attestation
Open T491 ↗
ART-13 · OpenChainGraph Promoted · chain_depth: 1
EUDI Wallet Credential-Acceptance Readiness Checker
Deep credential-acceptance readiness check: validates that your technical integration can correctly request, receive, verify, and process EUDI Wallet credentials end-to-end. Checks OpenID4VP presentation request construction, mdoc/SD-JWT-VC credential format support, certificate-chain validation against the EUDIW Trusted Infrastructure, selective disclosure parsing, and the revocation-status check flow (OCSP/CRL). Exports a §4 hash-anchored readiness report that maps each technical requirement to your current implementation status — the chain's key compliance evidence artifact.
⬡ OpenChainGraph compliance_mandate §4 execution_hash chain_depth: 1 Consumes: T491 RP registration OpenID4VP · mdoc · SD-JWT-VC
⬡ Open ART-13 →
05
T348 · Terminal · EUDI Readiness Scoring
eIDAS 2.0 EUDI Wallet Relying Party Readiness Scorer
Overall EUDI Wallet acceptance readiness grade and gap analysis. Aggregates your attribute mapping coverage (T489), KYC flow design completeness (T490), RP registration status (T491), and ART-13 technical integration readiness into a composite readiness score across five dimensions: Legal/Regulatory, Technical Integration, KYC/SCA Compliance, RP Registration, and Operational Readiness. Identifies your highest-risk gaps and generates a prioritised remediation roadmap for the Dec 2027 Art. 5f deadline. The terminal deliverable of this chain — your EUDI Wallet acceptance readiness pack.
Dec 2027 · Art. 5f T348 Terminal node Consumes: ART-13 §4 credential readiness Composite readiness grade · gap analysis
Open T348 ↗
✓ What you have at the end of this chain
A complete EUDI Wallet acceptance readiness pack — attribute map, KYC flow spec, RP registration status, §4 credential integration check, composite readiness grade

After this chain: a PID/QEAA/EAA attribute mapping (T489), a wallet-based KYC and SCA flow specification with OpenID4VP credential request structure (T490), an RP registration obligation checklist with runway estimate (T491), an ART-13 §4 hash-anchored credential-acceptance technical readiness report covering OpenID4VP, mdoc/SD-JWT-VC, and certificate chain verification, and a composite EUDI readiness grade with a prioritised gap-remediation roadmap (T348). The ART-13 §4 artifact is your machine-verifiable evidence of technical integration readiness — attach it to your Art. 5f compliance file.

§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.