7 Min. Read Time<\/p>\n
The European Digital Identity Wallet has become a mandatory roadmap for all EU member states with the eIDAS 2.0 coming into effect in May 2024. From May 2026, national pilot rollouts will start in Germany, Austria, and a growing number of other countries. By November 2027 at the latest, private acceptance points in banking, energy, telecommunications, and platform business models must accept the wallet as proof of identity. Those who don’t adapt their KYC and onboarding stack now will either have to manage two parallel identification processes in 2027 or lose out on time-to-yes in the competition.<\/strong><\/p>\n 04.05.2026<\/em><\/p>\n Related:<\/span>2026 Risk Profile: Caution as the Costliest Strategy<\/a> \/<\/span> ePA Rollout as a Growth Market<\/a><\/p>\n With eIDAS 2.0, the identification market is changing structurally for the first time since the introduction of the ID card eID in 2010. Not because a new technology is emerging, but because the regulation is enforcing acceptance. Those who offer bank accounts, SIM cards, or electricity contracts online will no longer be able to refuse proof of identity via the wallet from November 2027.<\/p>\n What is the EUDI Wallet exactly?<\/strong> A smartphone app issued or certified by a member state, in which citizens store, control, and release their official identity attributes to acceptance points. Technically, it is based on the eIDAS reference frameworks, OpenID4VC, Verifiable Credentials, and the EU Architecture and Reference Framework specification 1.4. Mid-sized companies will interact with the wallet in two roles: as a relying party that verifies identity or, less commonly, as an attribute provider that issues membership proofs or certificates.<\/p>\n The onboarding stack in the DACH mid-market looks like this in 80 percent of cases: customer form on the web frontend, video identification or eID jump, AML database comparison, contract document generation, signature via DocuSign or Adobe Sign, handover to ERP. EUDI Wallet intervenes in five of these six steps.<\/p>\n In the future, identification will not be done via video identification, but via wallet presentation. The AML database comparison will receive additional attributes that the wallet can provide (e.g. tax ID, commercial status, PEP marker). The signature layer benefits from qualified electronic signatures that the wallet can issue without a separate smart card. The ERP interface receives structured JSON-LD attributes instead of PDF attachments.<\/p>\n The effort is not just in one of these points, but in the concatenation. A pure wallet acceptance library on the website is not enough. If you don’t pass on the data records to the ERP, you have integrated the wallet at the front and the old paper workflow at the back.<\/p>\n Onboarding Step Mapping: Before \/ After<\/p>\n Sources: BMI EUDI Wallet Architecture Paper 2026-02, Bitkom Study Identity Onboarding 2025, three DACH bank onboarding audits 2026 Q1, eIDAS-2.0 Regulation Art. 5a-5d.<\/p>\n<\/div>\n \n“Whoever doesn’t restructure their KYC and onboarding stack now will be running two parallel identification paths in 2027 or lose out on Time-to-Yes in the competition.”<\/p><\/blockquote>\n Banks and savings banks<\/strong> have by far the tightest deadline. AML obligations plus PSD2 Strong Customer Authentication plus GDPR data minimization converge in the wallet use case. Those who currently operate three identification paths in parallel (branch identification, video identification, eID) will get a fourth one that cannot be rejected from 2027 onwards. Most DACH banks have scheduled the architecture review for Q4 2025, and the pilot rollout in 2026 is visibly being prepared by the cooperative banking associations.<\/p>\n Energy suppliers<\/strong> face less AML pressure, but more volume. Municipal utilities process an average of 20,000 to 80,000 online contract closures per year, with each step involving eID costing between 2.80 and 4.50 Euro. Wallet identification reduces this to under one Euro per transaction. For 50,000 transactions, that’s a difference of 100,000 to 175,000 Euro per year. Investment calculation: 6 to 9 months amortization for medium-sized municipal utilities.<\/p>\n Telecommunications providers<\/strong> are in the surprising position of benefiting from the wallet without feeling the pressure from banks. The identification requirement under the Telecommunications Act has been in place since July 2017, and the process is now being simplified. The question here is not if, but when: joining in 2026 reduces CAPEX, while catching up in 2027 costs double.<\/p>\n Those who plan the roadmap backwards from the mandatory date arrive at four phases.<\/p>\n Three silent frictions can be gleaned from the first architecture reviews. Firstly, ERP integration: old SAP versions with self-built identity mapping tables cannot process JSON-LD fields without middleware. Secondly, the AML vendor: not every AML database connection accepts wallet attributes instead of classic input data, and some providers will only update in Q3 2027. Thirdly, the customer service cut: without clear escalation paths for citizens without a wallet (estimated 15 to 25 percent of adults in 2027), a double service burden looms.<\/p>\n The honest expectation: not everything will run smoothly in 2027. Those who utilize the pilot in 2026 will learn about these frictions before the deadline.<\/p>\n No, mandatory acceptance applies to defined sectors: banks, insurance companies, telecommunications, energy, and very large online platforms under DSA. Traditional B2B mid-sized companies without these profiles are not directly obligated but benefit from voluntary integration into procurement and contract processes.<\/p>\n<\/details>\n For a DACH mid-sized company onboarding with video identification connection, AML layer, and ERP integration, implementation costs typically range between 80,000 and 320,000 Euro, depending on the existing architecture and whether a proprietary Wallet acceptance stack or a provider service is used. Ongoing costs are reduced by 60 to 80 percent compared to video identification per transaction.<\/p>\n<\/details>\n The Wallet is GDPR-compliant by design because the user individually releases each attribute (Selective Disclosure). Acceptance points may only request attributes necessary for the specific transaction. Requesting more data risks a fine under GDPR and an eIDAS-2.0 violation.<\/p>\n<\/details>\n Existing data remains valid; re-onboarding is not mandatory. From 2027, the Wallet can be used as a preferred re-verification path for security-relevant changes (address, account holder change, contract adjustment). AML supervisory authorities recommend testing re-verifies voluntarily during the 2026 pilot phase.<\/p>\n<\/details>\n About the Author<\/p>\n Eva Mickler<\/strong> writes for MyBusinessFuture about regulatory issues, compliance, and the gap between regulatory text and mid-sized company everyday life. Focus: interfaces between law, technology, and operations.<\/p>\n<\/div>\nKey Takeaways<\/h2>\n
\n
What’s really new in 2026<\/h2>\n
Where the restructuring starts in a typical mid-market onboarding process<\/h2>\n
\n\n
\n \nStep<\/th>\n Status 2025\/2026<\/th>\n With EUDI Wallet from 2027<\/th>\n<\/tr>\n<\/thead>\n \n Identification<\/td>\n Video identification, eID citizen portal, POSTIDENT<\/td>\n Wallet presentation with selectable attributes<\/td>\n<\/tr>\n \n Proof of address<\/td>\n Registration confirmation PDF, Schufa inquiry<\/td>\n Verifiable credential from the registration office directly in the wallet<\/td>\n<\/tr>\n \n AML \/ PEP check<\/td>\n External list connection, manual review<\/td>\n Wallet attributes plus reduced external list run<\/td>\n<\/tr>\n \n Contract conclusion<\/td>\n DocuSign, Adobe Sign, eIDAS-1.0 signature<\/td>\n QES directly from the wallet, without separate signature hardware<\/td>\n<\/tr>\n \n ERP handover<\/td>\n PDF attachment plus manual data typing share 8 to 15 percent<\/td>\n JSON-LD from wallet presentation, typing share under 1 percent<\/td>\n<\/tr>\n \n Time-to-Yes median<\/td>\n 3 to 5 working days (banking), 24h (mobile)<\/td>\n Sub-15 minutes in both cases, if ERP is well connected<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Three industries, three different pressure points<\/h2>\n
Timeline from May 2026 to November 2027<\/h2>\n
\n
Where mid-market plans typically fail<\/h2>\n
Frequently Asked Questions<\/h2>\n
Will all DACH mid-sized companies have to accept the Wallet from November 2027?<\/strong><\/summary>\n
What costs are associated with a typical mid-sized company onboarding?<\/strong><\/summary>\n
How does the Wallet comply with GDPR and data protection?<\/strong><\/summary>\n
What happens to existing customers whose identification still relies on video identification?<\/strong><\/summary>\n