EUDI Wallet Reference Implementation
June 22, 2026 Β· View on GitHub
:memo: EUDI Wallet Reference Implementation π§ Functional Scope πΊοΈ Roadmap π Repositories π οΈ Dev Hub π Disclaimer
EUDI Wallet Reference Implementation
Overview
The EUDI Wallet Reference Implementation is built based on the Architecture and Reference Framework (ARF) and aims at showcasing a robust and interoperable platform for digital identification, authentication and electronic signatures based on common standards across the European Union.
The EUDI Wallet Reference Implementation is based on a modular architecture composed of a set of business agnostic, re-usable components which are evolved in incremental steps and can be re-used across multiple projects.
Please check further listed in the following sections for more detailed information on how to get started, contribute, and engage with the EUDI Wallet Reference Implementation.
π Documentation & Resources
The EUDI Wallet documentation is organised across dedicated spaces:
| Topic | Where to find it |
|---|---|
| Wallet design & technical specifications (Architecture and Reference Framework) | eudi.dev |
| Reference Implementation documentation (feature map, components, getting started) | docs.eudi.dev |
| Conformance framework | conformance.eudi.dev |
| Frequently Asked Questions (FAQ) | EUDI Wallet FAQ |
| Official EUDI Wallet website | EU Digital Identity Wallet Home |
Functional Scope
The scope of the EUDI Wallet Reference Implementation is released in an iterative approach focusing on key functionalities which enable the support for a broad set of Use Cases, indicatively:
- Mobile Driving License
- Accessing online public and private services
- Opening a bank account
- SIM registration
- Payment authorisation
- Etc.
π§©For a detailed view of the delivered functionalities, please check the EUDI Wallet Reference Implementation's Feature Map on docs.eudi.dev.
Roadmap
The roadmap of the EUDI Wallet reference implementation provides a transparent view of the features and enhancements that are currently being developed or planned to the future. Its purpose is to promote open communication and collaboration in our community.
π§ You can view further details in EUDI Wallet Reference Implementation Roadmap.
Repositories
The EUDI Wallet Reference Implementation consists of a set of open-source repositories.
π Browse the Reference Implementation repositories on docs.eudi.dev, or the EUDI Wallet GitHub organisation, to find the information you need.
EUDI Wallet Dev Hub
The EUDI Wallet Dev Hub is a key reference point for those building and testing EUDI Wallet solutions, whether for Wallet Providers, Issuers, or Relying Parties.
Explore the EUDI Wallet Dev Hub to find technical guidelines, tools and directions for how to get started defining, designing and building an EUDI Wallet project.
Contributions and Feedback
We encourage you to contribute or provide your feedback/suggestion for the EUDI Wallet Reference Implementation. Depending on the type of feedback you wish to provide, you may utilise one of the following channels:
Code contributions
Comments and contributions on the codebase of the EUDI Wallet Reference Implementation are welcomed through the corresponding repositories in the EUDI Wallet GitHub organisation.Roadmap suggestions
If you have any questions or comments about the features listed on the roadmap or wish to suggest new features, please reach out via the Discussions forum.Other feedback
A designated mailbox CNECT-EUDIW-SUPPORT@ec.europa.eu is available where any queries related to the Wallet Reference Implementation can be addressed.Disclaimer
The released software is an initial development release version:
- The initial development release is an early endeavor reflecting the efforts of a short timeboxed period, and by no means can be considered as the final product.
- The initial development release may be changed substantially over time, might introduce new features but also may change or remove existing ones, potentially breaking compatibility with your existing code.
- The initial development release is limited in functional scope.
- The initial development release may contain errors or design flaws and other problems that could cause system or other failures and data loss.
- The initial development release has reduced security, privacy, availability, and reliability standards relative to future releases. This could make the software slower, less reliable, or more vulnerable to attacks than mature software.
- The initial development release is not yet comprehensively documented.
- Users of the software must perform sufficient engineering and additional testing in order to properly evaluate their application and determine whether any of the open-sourced components is suitable for use in that application.
- We strongly recommend not putting this version of the software into production use.
- Only the latest version of the software will be supported