Picture a customer opening a bank account in 2028. They don't photograph a passport or record a selfie video, and they don't wait while someone reviews the files. They tap “Verify with my wallet,” approve one prompt on their phone, and the verified data arrives in seconds.
This is the promise of the European Digital Identity (EUDI) Wallet. It raises an obvious question for every company that onboards customers: if the wallet verifies identity, what happens to the KYC provider you pay today? The short answer is that the wallet will take over part of the job and leave the rest, and the details matter for your architecture.
What the EUDI Wallet is, and what it means for users
The EUDI Wallet is a free mobile app, issued or recognized by an EU Member State, in which citizens and residents store verified digital credentials. These start with the core identity data (name, date of birth, nationality), known as the Person Identification Data (PID). Over time they extend to documents such as driving licenses, diplomas, and health insurance cards.
The wallet is built around selective disclosure. A user can prove they are over 18 without revealing a birth date, or confirm a name without handing over a full ID scan. Each time, the user sees exactly what is requested and who is asking, and consents explicitly. Using the wallet is voluntary, and a service cannot refuse a customer solely because they don't present one.
For users, the change is mostly about convenience and control. Identity is proven once, in the wallet, and reused wherever it is needed, so there are fewer photocopies and uploads. Companies receive only the attributes they actually need. A wallet issued in one Member State has to be recognized in the others. The regulation also lets users create qualified electronic signatures through the wallet, free of charge for non-professional use, which gives it legal weight beyond simple login.
Who makes the rules
Several layers of institutions are involved.
The EU legislature created the framework. The European Digital Identity Regulation, Regulation (EU) 2024/1183, commonly called eIDAS 2.0, entered into force on 20 May 2024 and amends the original 2014 eIDAS Regulation.
The European Commission writes the detailed rules beneath it. In late 2024 it adopted the core implementing acts for the wallet, which started the roughly 24-month countdown to the Member State deadline.
Member States build and certify the wallets. Each must offer at least one, and each runs its own national registers and supervisory arrangements. Romania has chosen to adopt the open-source solution developed in Germany for its national wallet, called RO Wallet. The Ministry of Internal Affairs is the official provider of the app and its backend infrastructure.
The deadlines that matter
The timeline comes from Regulation (EU) 2024/1183 (eIDAS 2.0), which entered into force on 20 May 2024. The wallet deadlines are counted from the entry into force of the Commission's first implementing acts on 24 December 2024.
24 Dec 2026
Every Member State must make at least one EUDI Wallet available to its citizens and residents (Article 5a). The rules for registering relying parties also apply from this date.
14 Jan 2027
Romania: the RO Wallet is scheduled for public launch, shortly after the EU-level deadline.
24 Dec 2027
Private organizations required by law or by contract to use strong user authentication must accept the wallet when a user chooses to present it (Article 5f). Micro and small enterprises are excluded, and the trigger is the authentication requirement, not the sector.
How a user will actually use the wallet
The first step happens once. The user downloads the national wallet app and activates it using a trusted identity source. In Romania, the new electronic identity card is the basis for activation.
After that, using it is simple. A bank, telecom, or marketplace presents a request, often as a QR code or an in-app prompt, naming the exact attributes it needs. The app shows who is asking and what will be shared, and the user approves with biometrics or a PIN. The service then verifies the result cryptographically, checking that the credentials are authentic, unaltered, and issued by a trusted authority. The company never has to inspect a document image for forgery, because the data is signed at the source.
Replacement or complement?
The wallet changes how identity is proven. It does not change what regulated companies must do with that identity afterwards.
What the wallet replaces
For a user who has a wallet, it can take over the most expensive and failure-prone part of digital onboarding: document capture and OCR, document authenticity checks, selfie and liveness checks, and manual review of poor-quality uploads. This is where conversion is lost today, and where wallet-based onboarding promises the biggest gains.
What it does not replace
The wallet proves who a person is, and nothing more. It cannot tell you whether a customer appears on sanctions or PEP lists, how risky the relationship is, or where the funds come from. It also cannot cover ongoing monitoring after onboarding. Those checks stay with you, but they now start from a more reliable verified identity.
Why you'll still need a fallback
- Adoption will be gradual. The wallet is voluntary, and you cannot turn away customers who don't use it. The EU's own target is 80% of citizens using it by 2030, so for years you will serve a mix of wallet and non-wallet users.
- Not everyone is in scope. Non-EU customers, cross-border customers whose countries are at different stages, and corporate customers will keep needing other verification routes.
- Rollout is uneven. Some national wallets will be late, limited, or still stabilizing when your obligations begin.
A realistic target picture
Treat the wallet as a new, preferred way to verify identity, and keep your existing provider as the fallback and the source of the checks the wallet doesn't cover. For customers who use the wallet, verified identity data comes straight from it, so document and liveness checks are largely unnecessary. For everyone else, your provider still verifies documents. Screening, risk scoring, and ongoing monitoring stay in place whichever route the customer takes, and your records need to bring the wallet data and everything else together in one clear, consistent trail.
The real challenge is integration
The hardest part of this transition is not the regulation but the engineering. To accept the wallet, you must register as a relying party, declare what data you request and why, and obtain the required access certificates. Your systems also need to support new technical standards for receiving and verifying wallet credentials.
On top of that, your onboarding flow has to handle several verification routes at once. It must decide when to offer the wallet, when to fall back to document verification, and when to ask for extra evidence, while keeping clear, time-stamped records of each route. Rollout will also differ from one Member State to another, so the flow can't assume every country works the same way.
For this reason, many teams will need an orchestration layer between their products and their verification sources. Plan it as a deliberate part of your architecture, not a plugin bolted onto the existing flow.
What to do now
A sensible plan works backwards from December 2027. Start by mapping every identity-dependent journey, including onboarding, re-KYC, step-up authentication, and payment authorization, because each is a candidate for wallet acceptance. Then check whether the obligation applies to you. What matters is whether law or contract requires strong user authentication for your service, not just your sector, and your legal advisers can answer that question. Next, design your onboarding so that a wallet, a document-based flow, and other eID schemes can sit side by side behind a single interface. Finally, pilot in 2027 with a limited group of customers, and measure completion rates, failure causes, and support load before full rollout.
This is where Convex can help. We work with your product and compliance teams from the first assessment of your current flows to production rollout. We design and build the integration layer that connects the wallet, other eID schemes, and your existing KYC providers, so you don't have to replace everything at once. That includes the orchestration logic that picks the right verification route for each customer, the technical side of relying-party onboarding, and a single, consistent audit trail for every verification. We can also build and monitor your 2027 pilot, so the decision to scale rests on real numbers.
Ready for December 2027?
The EUDI Wallet will change how identity is proven online, but it won't make your KYC and compliance stack obsolete. It will take over the identity-proofing step for customers who use it, while screening, risk assessment, monitoring, and fallback routes remain in place. The companies that benefit most will treat the wallet as one trusted source among several, and will build the architecture to support it before the 2027 deadlines arrive.