The EUDI Wallet enables consent-based data sharing by giving users full control over which personal data they share, with whom, and when. Before any information leaves the wallet, the user must actively approve the request. This applies to every interaction, whether it is opening a bank account, accessing a government service, or proving their age online. The sections below explain exactly how this works in practice.
What data can users actually share through the EUDI Wallet?
Users can share a wide range of verified personal data and digital documents through the EUDI Wallet, including identity attributes such as name, date of birth, and nationality, as well as official credentials like driving licences, diplomas, healthcare cards, and travel documents. The wallet acts as a single secure container for both identity data and document-based credentials.
The types of data stored and shareable through the wallet include:
- Personal identity attributes (name, address, nationality, date of birth)
- Government-issued documents (passport data, driving licence, residence permit)
- Academic and professional credentials (diplomas, certificates)
- Healthcare information (European Health Insurance Cards, prescriptions)
- Financial credentials (for account opening or strong customer authentication)
- Payment means and transport passes
Not all of this data needs to be shared in every situation. The wallet is designed so that users can share only the specific attributes relevant to a given request. This is a fundamental shift from how identity verification works today, where showing a passport often reveals far more than is actually needed.
How does the EUDI Wallet enforce user approval before sharing data?
The EUDI Wallet enforces user approval through an explicit confirmation step that occurs every time a relying party requests access to personal data. No data is transmitted without the user actively confirming the request on their device. This mechanism is built into the wallet’s architecture and cannot be bypassed by the requesting organisation.
When a service provider sends a data request, the wallet displays a clear overview of exactly what information is being asked for and who is asking. The user then decides whether to approve, reject, or limit the request. This process happens in real time and is entirely user-driven.
It is important to distinguish between this in-wallet approval and consent as a legal basis under the GDPR. The user’s approval of a data request in the wallet does not automatically constitute GDPR consent. The relying party receiving the data must have its own lawful basis for processing under the GDPR. For identity verification in a KYC context, that basis is typically a legal obligation. For health data, an additional condition under Article 9(2) GDPR is also required.
This approach gives users considerably more visibility than traditional identity verification methods, where users often have little insight into what data is collected or how it is used. With the EUDI Wallet, approval is granular, informed, and tied to each individual interaction. The wallet also allows users to review which organisations have received which data through a dashboard designed as a tool for the user, giving them ongoing oversight of past data shares.
What is selective disclosure and how does it work in the EUDI Wallet?
Selective disclosure is the ability to share only specific attributes from a credential, rather than the full document or dataset. In the EUDI Wallet, selective disclosure means a user can prove they are over 18 without revealing their exact date of birth, or confirm their nationality without sharing their home address. Only the minimum required information is disclosed.
This works through the use of verifiable credentials in standardised formats such as mdoc and SD-JWT VC, which allow individual data fields within a credential to be shared independently. The wallet uses cryptographic techniques to ensure that a selectively disclosed attribute remains verifiable and trustworthy, even though the rest of the credential stays hidden. Age verification without revealing a date of birth can be achieved through selective disclosure of an attribute such as “age over 18” and does not require zero-knowledge proofs.
A practical example makes this concrete. Imagine booking tickets for an age-restricted event. The wallet presents a single verified statement: “This person is 18 or older.” The event organiser receives a cryptographically signed confirmation, and nothing else. The user’s name, address, and exact date of birth stay private.
Selective disclosure is one of the most privacy-protective features of the EUDI Wallet and is central to the principle of data minimisation embedded in eIDAS 2.0, which amends Regulation (EU) 910/2014. It reduces the amount of personal data that organisations receive, though it does not eliminate all risk of tracking or profiling. Organisations still receive verified attributes, and how those attributes are used depends on the relying party’s own data handling practices and legal obligations.
Who can request data from a user’s EUDI Wallet?
Only registered relying parties can request data from a user’s EUDI Wallet. Under CIR (EU) 2025/848, adopted on 6 May 2025, relying parties must register with the national authority of their Member State of establishment before they can request wallet data. As part of that registration, each relying party specifies the intended uses for which it will request data, and which attributes and attestations it needs for each use. The wallet checks incoming requests against this registered scope.
Relying parties span a broad range of sectors. Public authorities such as tax offices, healthcare providers, and municipal services can request identity data for service access. Private sector organisations including banks, insurers, telecoms providers, and online platforms can also register as relying parties, allowing them to use the wallet for identity verification and onboarding.
When a relying party sends a request, the wallet displays information about who is asking and under what legal basis. Users can see whether the requesting organisation is registered before deciding to share anything. This transparency is a deliberate design choice: users should always know exactly who is on the other side of a data request.
It is worth noting that a relying party does not choose a wallet provider. A registered relying party must be capable of accepting every relevant notified wallet, regardless of which provider issued it or in which Member State. Sector-specific legal obligations continue to apply alongside the eIDAS 2.0 framework.
Organisations working in financial services or government are among the first sectors expected to integrate with the EUDI Wallet ecosystem, given their existing regulatory obligations around identity verification.
How does the EUDI Wallet protect against over-collection of personal data?
The EUDI Wallet protects against over-collection by enforcing data minimisation at the technical level. Relying parties can only request the specific attributes they have registered for each intended use, and users can reject or limit any request that goes beyond what is necessary. The wallet does not allow bulk data transfers or open-ended access to a user’s credential store.
Several mechanisms work together to prevent over-collection:
- Attribute-level requests: Relying parties must specify exactly which data fields they need for each registered intended use, rather than requesting an entire document.
- User approval per interaction: Every data share requires explicit approval, so there is no standing permission that allows repeated or automatic access.
- No central data repository: Data stays on the user’s device and is only transmitted at the moment of sharing. There is no central database that organisations can query.
- Regulatory boundaries: Under eIDAS 2.0, relying parties are legally bound to request only what is proportionate and necessary for their stated purpose.
- User dashboard: Users can review a log of past data shares through the wallet dashboard, giving them visibility and the ability to identify unexpected or excessive requests.
Together, these layers make it structurally difficult for organisations to collect more data than they are entitled to. The wallet shifts the default toward sharing only what is needed for a specific, registered purpose.
What does consent-based sharing mean for organisations accepting EUDI Wallet credentials?
For organisations that accept EUDI Wallet credentials, user-approved sharing means they will receive verified, user-approved data attributes rather than self-declared information or unverified copies of documents. This raises the quality and trustworthiness of the data they receive while also placing clear obligations on how that data may be used.
Organisations need to adapt their processes in several ways. They must define precisely which data attributes they need for each use case, register as a relying party under CIR (EU) 2025/848 with the national authority of their Member State of establishment, and ensure their systems can technically receive and process verifiable credentials in formats such as mdoc and SD-JWT VC. They also need to align their data handling practices with the principle of data minimisation, since they are entitled to use the data only for the purpose stated in their registered intended use. Where organisations operate across borders, they must account for national registration requirements and any sector-specific legislation that continues to apply in each relevant jurisdiction.
The benefits are real. Verified credentials reduce fraud risk, streamline onboarding, and eliminate the need for manual document checks. For sectors like healthcare and financial services, where identity verification is both critical and heavily regulated, the EUDI Wallet offers a more reliable and efficient alternative to current methods. Organisations in healthcare can use it to confirm patient identity securely, while financial institutions can meet know-your-customer requirements with verified, user-approved data. Note that whether verified wallet data can be reused for KYC purposes across institutions depends on AML regulation, not on eIDAS 2.0 itself.
The shift also has implications for customer experience. Users who control their own data and understand what they are sharing are more likely to trust the organisations they interact with. User-approved sharing is both a compliance requirement and a foundation for building lasting digital trust.
How the ID Connector supports consent-based data sharing via the EUDI Wallet
Preparing your organisation for the EUDI Wallet and user-approved data sharing involves a clear understanding of the regulatory framework, a well-defined data strategy, and the right architecture to handle verifiable credentials securely and at scale. Governance of the EUDI Wallet ecosystem is a shared responsibility: the European Commission manages the legal framework and adopts implementing acts, EU Member States provide or mandate wallet solutions and supervise actors within their jurisdiction, and a range of other parties, including wallet providers, issuers of Person Identification Data and attestations, qualified trust service providers, and relying parties, each carry distinct roles and obligations.
The ID Connector is an integration that lets relying parties accept every certified European wallet, whatever Member State issued it, for identification, login and qualified signing. EUDI Wallet acceptance comes first; the same interface also carries other IDs, such as national eIDs, bank IDs and identity documents, inside and outside the EU.
In the context of consent-based data sharing, the ID Connector concretely handles:
- Accepting wallet presentations from any notified wallet, regardless of the issuing Member State
- Verifying issuer signatures against the relevant national trusted lists, which are aggregated in the EU List of Trusted Lists
- Checking revocation status using issuer-provided status information
- Validating wallet unit attestations to confirm that the presenting wallet runs on a certified wallet solution
- Enforcing the registered attribute scope so that only data fields covered by the relying party’s registration under CIR (EU) 2025/848 are requested and processed
- Supporting selective disclosure flows so that users share only the attributes required for each specific interaction
- Connecting to a qualified trust service provider for qualified signing where required
Organisations in financial services, healthcare, pharma, and government can use the ID Connector to meet their identity verification obligations under the EUDI Wallet framework without building and maintaining the underlying trust infrastructure themselves. Get in touch with TrustTech to find out how the ID Connector fits your organisation’s situation.