Updated version of EBW definition, version 1.1 - #281
Conversation
stavamichal
commented
Jul 30, 2026
- Based on issue Scope and Context: Regulatory Alignment (EC Proposal & EP Amendments) update #236
- Added information based on last known proposed Regulation of European Council on EBW from 9th June, 2026
- Added challanges and open topics we do know so far
- Added References to mentioned facts
| This document draws on the EUDI Wallet regulations, EWC deliverables<sup><sup>[\[1\]](#footnote-0)</sup></sup>, and relevant industry and consortium publications, and incorporates the draft Implementing Act on Business Wallet. | ||
| This document draws on the EUDI Wallet regulations, EWC deliverables [\[6\]](#references), and relevant industry and consortium publications. Its main legal reference is the text of the proposed Regulation on the establishment of European Business Wallets as agreed in the Council’s general approach of 9 June 2026, published as Council document 10346/26 [\[2\]](#references), read together with the original Commission proposal COM(2025) 838 [\[1\]](#references) and the European Parliament ITRE rapporteur’s draft report [\[3\]](#references). | ||
|
|
||
| ### Legislative status |
There was a problem hiding this comment.
Suggest addition to section 2.2 in the Blueprint instead.
There was a problem hiding this comment.
As requested, I have moved the legislative status to 2.2 in commit 44e1785
|
|
||
| Where this document cites Articles, Recitals or the Annex without further qualification, it refers to the Council general approach text. | ||
|
|
||
| ## Purpose of the European Business Wallet |
There was a problem hiding this comment.
Suggest this to be merged into either chapter 1.1 "Background" or 2.2 "EBW framework"
There was a problem hiding this comment.
I was looking into chapters 1, 2 and 3 and I didn't find any right place where the description of EBW purpose would fit better. To be honest, IMHO believe that this particular text should stay in Business Wallet Definition. I have shorten it in f9050b3 If you insist that this is not a good place for it, I would rather remove it instead of moving it somewhere else.
| 1. Authorisations in the wallet are **technical**. They do not create, limit or otherwise affect any power of attorney or legal mandate under national or Union law (Article 5(1)(j), Recital 18). | ||
| 2. The authorisation system should remain compatible with the EU digital power of attorney established by Directive (EU) 2025/25 (Recital 18). | ||
|
|
||
| ### Relationship with the EUDI Wallet |
There was a problem hiding this comment.
I would suggest streamlining this text a bit, Passages discussing Recital 4 precedence (where the EBW Regulation takes precedence over ARF in case of inconsistency) or the ITRE draft report's non-operative architectural directions are better placed in the main body.
The high-level framing of how the EBW "builds on and complements" the eIDAS framework is already (partially at least) covered in Section 2.2 of the main Blueprint.
The functional interaction patterns fits nicely here though;
- Distinction: Natural persons (EUDI) vs. Legal persons (EBW).
- Authentication: How the EUDI Wallet is used to "unlock" or operate the EBW.
- Hybrid Roles: How sole traders bridge the two worlds.
| class EBW businessWallet | ||
| ``` | ||
|
|
||
| ### Key terminology |
| | Provider of EBW-OID | A qualified trust service provider, a public sector body responsible for an authentic source, or the Commission (for Union entities). | | ||
| | Critical assets | Assets within or in relation to a wallet unit whose compromise would have a very serious, debilitating effect on the ability to rely on that unit (Article 3(27)). | | ||
|
|
||
| ## Legal effect: the principle of equivalence |
There was a problem hiding this comment.
Should also be moved, to section 2.2 on "The EBW Framework".
This principle is a cornerstone of the Regulation's legal mandate and provides the necessary context for why public sector bodies must accept EBW-based actions and belong in the main document. Moving it keeps Appendix D focused on being a lean, functional reference for our development teams.
There was a problem hiding this comment.
As requested, the principle of equivalence has been moved to section 2.2 via bd1ece7
|
Thank you @stavamichal for the suggested update and all the work you have put into this! While the updated content provides important clarity, I have some concerns regarding the formatting and placement of this text within Appendix D and would like to suggest some updates:
Proposal for the Section:
The purpose of moving the regulatory 'weight' to the main body is to ensure Appendix D remains a lean, practical reference for our capability and use case teams. |
|
@Saramandus Thanks for all the comments, we will process them as soon as possible. |
- Based on issue webuild-consortium#236 - Added information based on last known proposed Regulation of European Council on EBW from 9th June, 2026 - Added challanges and open topics we do know so far - Added References to mentioned facts
897ecfc to
e425120
Compare
|
I have removed unnecessary citations in 9d4a986 |
|
@Saramandus I have made few changes as you suggested. Please, let me know if this is more suitable as Annex document of EBW for D4.1. Thank you! |
Saramandus
left a comment
There was a problem hiding this comment.
I think this is a good update to both the vocabulary and the Regulatory and foundational alignment chapter.