The EUDI Wallet handles cross-border identity verification by allowing citizens to present cryptographically signed identity data from their home country to services and authorities in any other EU Member State. Because every wallet is built on shared European technical standards under eIDAS 2.0, which amends Regulation (EU) 910/2014, the receiving party does not need to know anything about the user’s national identity system to trust what they receive. This article unpacks the most common questions organizations have about how that process works in practice.
Which countries and services accept the EUDI Wallet?
24 December 2026 is the legal deadline by which all EU Member States must make a European Digital Identity Wallet available to their citizens, residents, and businesses, and by which public sector services must accept notified wallets for online interactions that require electronic identification. This deadline is an outer limit, not a predicted launch date, and it does not guarantee that every national wallet will have reached the same level of maturity on that date, or that every possible cross-border use case will be fully operational throughout Europe from that moment. National rollout, certification, notification, and relying party acceptance are each distinct steps, and practical interoperability is likely to develop in phases across Member States.
From 24 December 2027, Article 5f of eIDAS 2.0 requires relying parties in regulated private sectors to accept the wallet where strong user authentication is legally or contractually required. The sectors covered include banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. Micro and small enterprises, defined as organizations with fewer than 50 employees and an annual turnover or balance sheet total of no more than 10 million euros, are exempt. Very large online platforms fall under a separate provision of Article 5f: they must accept the wallet where the platform requires user authentication, on the voluntary request of the user and for the minimum necessary data.
Four large-scale pilot projects involving more than 350 organizations from 26 Member States, Norway, Iceland, and Ukraine tested real-world use cases between April 2023 and 2025. These pilots covered a wide range of scenarios across four consortia. POTENTIAL piloted government services, opening a bank account, SIM registration, mobile driving licence, remote qualified signing, and e-prescriptions. EWC piloted Digital Travel Credentials, payments, and organisational digital identity. NOBID focused on payments. DC4EU covered education and social security. A second wave of pilots started in 2025: WE BUILD focuses on business wallets and payments, and APTITUDE covers travel, ticketing, vehicle registration, and payments.
The scope of acceptance is wide. The wallet is designed to work for both online and in-person interactions, which means organizations in almost every sector will eventually need to be able to receive and verify wallet-based identity data. Organizations should not wait for a single European go-live moment. National readiness will vary, and early preparation is more effective than waiting for uniform market maturity.
How does the EUDI Wallet verify identity across different national systems?
The EUDI Wallet verifies identity across national systems by relying on a shared technical framework. When a user presents their wallet to a service in another Member State, the receiving party performs several distinct checks on a digitally signed attestation, not on the raw national identity record. This means the verification works regardless of how the home country’s identity system is built internally.
Each wallet contains Person Identification Data (PID) attestations. These are issued by the user’s home country, specifically by the authority designated by that Member State as a PID issuer, digitally signed, and stored securely in the wallet unit. When a cross-border service requests identity data, the wallet presents the relevant attestation. Verification involves three separate steps. First, the receiving system checks the issuer’s digital signature against the relevant national trusted list, which is part of the EU List of Trusted Lists (LOTL). This step can be performed fully offline. Second, the relying party checks the revocation status of the attestation using status information provided by the issuer. Third, the relying party validates the wallet unit attestation to confirm that the presenting wallet runs on a certified wallet solution. The second and third steps require a connection to external information and cannot be completed fully offline.
This architecture addresses one of the core limitations of the original eIDAS framework, which required bilateral recognition but left technical details to individual countries. Under eIDAS 2.0, technical standards are harmonized at the European level through implementing acts adopted by the European Commission. The Architecture and Reference Framework (ARF) provides the technical elaboration of those requirements. As a result, a service provider in one Member State can verify a wallet attestation from another Member State using the same logic it would apply domestically. Governance across this system is a shared responsibility: the European Commission manages the legal framework, Member States certify and notify wallet solutions and supervise actors within their jurisdiction, and the European Digital Identity Cooperation Group supports cross-border alignment.
What data does the EUDI Wallet share during a cross-border verification?
During a cross-border verification, the EUDI Wallet shares only the specific attributes the service has requested and the user has approved. This selective disclosure principle is one of the wallet’s defining features. A service that only needs to confirm a user is over 18, for example, receives a verified yes or no response derived from the relevant attribute, without receiving the full date of birth, name, and address.
The data shared depends on the use case. For accessing a government service, this might include name, date of birth, nationality, and a national identifier. For a payment authorization, it might be a verified identity confirmation only. The wallet gives users full visibility over what is being requested before they approve the transaction.
The wallet is designed to avoid unnecessary data sharing. Users can see exactly what a service is requesting before they approve each interaction. Approval in the wallet is a per-transaction decision and is distinct from consent as a legal basis under the GDPR. Relying parties need their own GDPR legal basis for processing the data they receive. Nothing is shared automatically or in the background. This approach aligns with the GDPR’s data minimization principle and gives individuals meaningful control over their digital identity. It is also worth noting that no central European database holds everyone’s identity data: attestations are issued and held at the national level and presented directly by the user.
What is the difference between the EUDI Wallet and existing eIDAS cross-border login?
The original eIDAS framework, Regulation (EU) 910/2014, created a legal obligation for governments to recognize each other’s notified electronic ID schemes, but left the technical implementation fragmented and excluded the private sector entirely. eIDAS 2.0, which amends that regulation through Regulation (EU) 2024/1183, replaces that patchwork with a standardized, interoperable wallet that works for both public and private services across all Member States.
Under the original eIDAS, cross-border login worked through a network of national nodes that translated authentication requests between countries. It was complex to implement, limited to certain assurance levels, and practically unavailable to most private organizations. Coverage was also uneven: not every Member State notified a scheme, and those that did often had limited interoperability in practice.
The EUDI Wallet changes this in several important ways. Every Member State must provide a wallet, with public sector acceptance required by 24 December 2026. Private sector relying parties in regulated sectors are included as mandatory acceptors from 24 December 2027. The wallet supports authentication and the presentation of verifiable attestations, such as diplomas, professional qualifications, and health documents, in standardized credential formats including mdoc and SD-JWT VC. The user experience is standardized, so the same wallet app works consistently across borders using protocols including OID4VP for presentation and OID4VCI for issuance, rather than routing through country-specific infrastructure. Cross-border use does not eliminate national or sector-specific requirements: relying party registration under CIR (EU) 2025/848 remains connected to the applicable national registration framework, and sector legislation such as anti-money laundering rules continues to apply alongside wallet-based verification.
For organizations in financial services or other regulated industries, this shift is significant. Cross-border digital onboarding and identity verification become genuinely scalable, even as sector-specific compliance obligations remain in place.
What happens when a cross-border verification fails or is rejected?
When a cross-border EUDI Wallet verification fails, the most common causes are a mismatch between what the relying party requested and what the wallet can provide, a technical error in the signature validation process, a revoked or expired attestation, or a wallet that has not yet been fully activated or certified. In most cases, the service will receive a clear error response.
From the user’s perspective, a failed verification typically means they need to provide an alternative form of identity proof or contact the issuing authority to resolve a problem with their wallet. Services are generally expected to offer fallback options during the transition period, since national wallets will reach different levels of maturity at different times and not all users will have a fully functional wallet immediately.
From the organization’s side, handling rejections gracefully is an important part of implementation. This means building workflows that can accommodate wallet-based verification alongside traditional identity checks, logging failed attempts in a way that supports audit requirements, and providing users with clear guidance on next steps. Organizations that plan their integration approach carefully will be better positioned to manage edge cases without creating friction for legitimate users.
How should organizations prepare to accept the EUDI Wallet from foreign users?
Organizations should start by mapping which of their digital services require identity verification and assessing which user journeys are most likely to involve cross-border users. From there, preparation involves three practical areas: technical integration, compliance readiness, and user experience design.
- Technical integration: Organizations need to register as a relying party with the national authority of their Member State of establishment under CIR (EU) 2025/848, before requesting any wallet data. Registration is per intended use: the relying party declares which attributes and attestations it will request, and the wallet checks incoming requests against that registered scope. Implementation requires support for the protocols that underpin the wallet architecture, including OID4VP for presentation and OID4VCI for issuance, as well as the relevant credential formats mdoc and SD-JWT VC.
- Compliance readiness: Accepting wallet-based identity data comes with obligations around data handling, audit logging, and purpose limitation. Organizations should review their existing GDPR and eIDAS compliance frameworks to ensure they cover wallet interactions, and should also account for any sector-specific requirements that apply in their industry. A relying party must have its own GDPR legal basis for processing the data it receives. A qualified trust service provider (QTSP) is not automatically required for wallet acceptance, but becomes relevant where the use case involves qualified electronic signatures or qualified electronic attestations of attributes (QEAAs).
- User experience design: A wallet verification flow needs to be clear for users who may be unfamiliar with the technology. Transparent data requests, clear approval screens, and reliable fallback options all contribute to a smooth experience, particularly during the period when wallet adoption is still growing unevenly across Member States.
Organizations in sectors such as government and healthcare face particularly pressing timelines, given the mandatory acceptance requirements that apply to public services from 24 December 2026. Starting preparation now gives organizations time to test integrations, train teams, and refine workflows before cross-border wallet use becomes widespread.
How the ID Connector supports EUDI Wallet cross-border identity verification
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.
For organizations preparing to accept EUDI Wallet credentials from users across Europe, the ID Connector handles the technical and trust management steps that cross-border verification requires:
- Verifying issuer signatures against national trusted lists consolidated in the EU List of Trusted Lists (LOTL), and checking revocation status and wallet unit attestations as part of each verification
- Enforcing the registered attribute scope per relying party, so that only the attributes declared during registration under CIR (EU) 2025/848 are requested from the wallet
- Connecting wallet-based identity verification to qualified electronic signatures via an integrated QTSP, creating a tamper-evident record of each interaction
- Supporting reuse of verified identity data across interactions, reducing repeated verification for returning users without linking records to a wallet identifier
- Covering the sectors where acceptance obligations apply earliest, including financial services, healthcare, pharma, and government
Cross-border digital identity is a present requirement. If your organization wants to be ready to accept the EUDI Wallet from users across Europe, get in touch with TrustTech to discuss your specific situation and next steps.