In-depth technical documentation for EUDI Wallet implementations across EU member states. Architecture models, security standards, open source repositories, and implementation details.
📚 What You\\'ll Find Here
Technical Architecture
- • Architecture models and patterns
- • Security infrastructure
- • Cryptographic approaches
- • Interoperability standards
Implementation Details
- • Open source repositories
- • Technical guidelines
- • Development timelines
- • Partner organizations
Country Technical Deep-Dives
Germany
App: AusweisApp • Architecture: Signed Credential with Cloud Support (C')
Technical Highlights:
France
App: France Identité • Architecture: Cloud-based credential storage
Technical Highlights:
Netherlands
App: NL-wallet • Architecture: Local-first with cloud backup
Technical Highlights:
Belgium
App: MyGov.be • Architecture: Dual authentication (eID/itsme)
Technical Highlights:
Italy
App: IT-Wallet • Architecture: SPID integration
Technical Highlights:
Poland
App: mObywatel 3.0 • Architecture: Evolutionary (2.0 to 3.0)
Technical Highlights:
✅ All 6 Verified Countries Documented
Technical deep-dives now complete for all 6 verified EUDI Wallet implementations representing 74% of EU population. Each country has complete documentation covering architecture, security standards, leadership, and deployment strategy.
Coverage: Germany • France • Netherlands • Belgium • Italy • Poland
Additional countries will be added as official technical specifications become publicly available and verified.
Interoperability Standards and Protocols
OpenID4VC High Assurance Interoperability Profile (HAIP)
OpenID4VC HAIP 1.0 uses OpenID for Verifiable Credential Issuance (OpenID4VCI) and OpenID for Verifiable Presentations (OpenID4VP) as base protocols. Credential formats include IETF SD-JWT VC (Selective Disclosure JSON Web Token Verifiable Credentials) and ISO mdoc (mobile documents).
Protocol Implementation: For remote presentation flows, the Wallet Instance implements the OpenID4VP 1.0 protocol in combination with the W3C Digital Credentials API. For remote issuance, wallets support OpenID4VCI 1.0 specification based on ARF and ISO/IEC 18013-5 (CBOR) standards.
Testing Environment: The EUDI Wallet Launchpad (December 10-12, 2025, Brussels) tested implementations using HAIP 1.0 – draft 04 as the interoperability profile, with 420 successful tests across OpenID4VCI 1.0 (issuance), OpenID4VP 1.0 (remote presentation), and ISO/IEC 18013-5 (proximity presentation).
Credential Formats: W3C VC and ISO 18013-5 mDL
EUDI Wallet supports two internationally recognized credential formats for secure issuance and verification:
W3C Verifiable Credentials Data Model
JSON-LD based credentials supporting selective disclosure, zero-knowledge proofs, and flexible attribute sharing. Used for diplomas, professional qualifications, vaccination certificates, and organizational credentials (QEAA/PuB-EAA).
ISO/IEC 18013-5 Mobile Driving License (mDL) and mDoc
CBOR-encoded mobile documents (mDoc) standard for national ID cards, driver\'s licenses, and health insurance cards. Supports proximity presentation via NFC/Bluetooth and remote presentation via OpenID4VP. Part 7 (ISO/IEC 18013-7) defines add-on functions for extended capabilities.
Interoperability: Both formats ensure cross-border recognition and relying party acceptance throughout the EU. Wallets must support issuance and presentation of credentials in both formats according to ARF 2.7.3 specifications.
Developer Resources and Integration
Official GitHub Organization: The EUDI Wallet open source code is available at github.com/eu-digital-identity-wallet. Explore reference implementations or get started using the EUDI Wallet DevHub.
Key Repositories: Architecture and Reference Framework (ARF), Standards and Technical Specifications (STS), implementation libraries for iOS (Swift), Android (Kotlin), Kotlin Multiplatform, server components (PID issuer, trust validator, web verifier), and testing tools.
Integration Requirements: Developers integrating relying party services must support credential verification using OpenID4VP 1.0 for remote flows and ISO/IEC 18013-5 for proximity flows. Begin technical preparation by integrating EUDI Wallet Connector API software and align with eIDAS 2.0 requirements.
Documentation Access: All technical specifications are published openly on GitHub following a transparent and collaborative drafting process. Stakeholders can comment and contribute via GitHub Issues and Pull Requests to shape the evolving standards.
Understanding EUDI Wallet Technical Standards
EU-Wide Framework
eIDAS 2.0 Regulation (EU 2024/1183)
Legal framework requiring all EU member states to provide at least one EUDI Wallet by December 2026 (for governments) and mandating acceptance by Very Large Online Platforms (VLOPs) by December 2027.
Architecture Reference Framework (ARF)
Technical specification (currently v2.7.3) defining interoperability standards, security requirements, and common technical approaches for EUDI Wallet implementations across all EU member states.
Open Source Requirement
All EUDI Wallet implementations must use open-source licenses for application software components, enabling transparency, security audits, and community participation.
National Standards
Each member state maintains additional national technical standards and security requirements:
- Germany:BSI TR-03127 (eID cards), TR-03128 (service providers), TR-03130 (eID-Server)
- France:ANSSI (National Agency for Security of Information Systems) requirements
- Netherlands:Ministry of Interior and Kingdom Relations (BZK) standards
- More:Technical documentation added as countries publish specifications
For Developers & Technical Teams
Building services that integrate with EUDI Wallets? These technical deep-dives provide the specifications, standards, and implementation details you need.