eIDAS 2 for Insurance

Insurance is unique in having two separate tracks toward EUDI wallet acceptance. One is regulatory: life and investment insurers must comply by 10 July 2027, when the EU's new anti-money laundering rulebook takes effect and recognizes digital identity as a valid way to verify customers. The other is commercial: motor, home and travel insurers face no legal deadline, but still stand to gain from adopting wallets. This guide covers both tracks and the benefits EUDI Wallets offer insurers across the board.

What changes for insurers

1. The date for life and investment products. The EU's Anti-Money Laundering Regulation applies from 10 July 2027 across all Member States, with a dedicated section for the life and investment-related insurance sector — and it accepts electronic identification meeting the EU's substantial or high assurance levels as a way to verify customers.
2. Underwriting stops relying on self-declaration. A driving licence, a professional qualification or a company registration presented from a wallet becomes instantly cryptographically verifiable.
3. Proof of cover becomes issuable. An insurance certificate in a customer's wallet can be verified instantly by a landlord, employer or contracting authority — and stops being valid the moment cover ceases.
4. Most of the work is being done by other organizations. The credentials insurers want are being created because licensing authorities, health authorities and registries will begin to issue credentials.

The deadline depends on the type of insurance.

Life and investment-related insurance. From 10 July 2027 the Anti-Money Laundering Regulation applies directly in every Member State, replacing the patchwork of national implementations with one rulebook covering customer due diligence, beneficial ownership and ongoing monitoring. It contains provisions specific to the life and other investment-related insurance sector, and it allows identity to be verified using electronic identification meeting the EU's substantial or high assurance levels — which is exactly what the EUDI Wallet provides.

Commercial lines. Business customer due diligence raises the same questions about company identity, signing authority and beneficial ownership, and the same answers apply.

Motor, home, travel and general insurance. There is no clear obligation here. The case for these lines is commercial — better underwriting data, less claims leakage, and faster onboarding.

A growing credential ecosystem for insurers

Something unusual is true of insurance that is not true of any other sector covered by the eIDAS 2 hub.

Insurers often price risks, issue policies, and settle claims using facts maintained by other institutions: whether someone holds a valid driving licence and for which categories, whether a professional holds a current qualification, whether a company is registered and who may act for it, or whether another policy already covers the same risk. Today, insurers commonly obtain these facts through customer declarations, submitted documents, registry checks, intermediaries, and sector-specific data exchanges. Access is often fragmented, jurisdiction-specific, or difficult to automate.

With the EUDI wallet all of this facts are becoming credentials which are instantly and cryptographically verifiable:

• Driving licences are moving into wallets under the EU's new driving licence rules, with the digital licence becoming the main format across the EU. See the transport and mobility guide.
• Health and coverage data is being made portable through the European Health Data Space and related work on digital insurance entitlements. See the healthcare guide.
• Professional qualifications are being issued as credentials by authorities and professional bodies. See the education guide.
• Company registrations are becoming verifiable through business registers and the proposed European Business Wallet. See the public sector guide.

Insurers can greatly benefit from these various types of credentials which will be issued into the market – to improve processes, reduce cost, and enhance the user experience.

The roles insurers play

Verifier

As a verifier, an insurer requests and checks credentials. This means registering as a relying party with the national registrar, declaring which data each process will request, and being able to check that credentials received are genuine, still valid, and belong to the person presenting them.

Issuer

As an issuer, an insurer can put credentials into customer wallets — most usefully a proof of cover. See more below.

Wallet Provider

As a wallet provider, an insurer can extend its existing products with wallet capabilities for users to receive, present, and store credentials.

Core insurance use cases at a glance

Customer due diligence for life and investment products

The Anti-Money Laundering Regulation is a regulation rather than a directive, which means it applies directly and identically in every Member State from 10 July 2027, with no national transposition.

The verification step is where the EUDI wallet provides a great solution. AMLR permits identity to be verified using electronic identification meeting the EU's substantial or high assurance levels. The credential in a certified EUDI Wallet is issued by the customer's Member State and verified at the highest of those levels, so a single presentation replaces document capture, liveness checks and manual review.

Selective disclosure helps with the data minimisation problem. Onboarding processes routinely collect more than the rule requires because the document happens to contain it. The wallet lets the insurer request only what the process needs.

What it does not do is discharge the rest of the requirements. Sanctions and PEP screening, risk assessment, and ongoing monitoring remain exactly where they are. The wallet replaces the identification step, not the rest of the compliance.

Underwriting from verified facts

Many of the facts insurers use to assess risk still reach them through application forms, uploaded documents, and manual checks. A motor applicant provides their licence details and driving experience. A professional indemnity applicant submits evidence of their qualifications or professional status. A commercial applicant enters company information and identifies who may act for the business.

Some information can already be checked through registers, industry databases, external data providers, and direct integrations. However, access differs between countries, insurance products, and individual insurers, and relevant data may not be available in a standardized, real-time form during quotation. Insurers may therefore price a policy using information that has not yet been independently verified, with inaccuracies potentially being identified during later underwriting checks or claim handling.

Wallets could bring authoritative evidence directly into the application process, provided the relevant institutions issue it as digital credentials. A digital driving licence can provide licence categories and validity information authenticated by the issuing authority. A professional attestation can confirm a qualification or current professional status. Company credentials can confirm registration details and who is authorised to represent the business.

Issuing proof of cover

An insurance certificate is a document people are asked to produce constantly: by landlords, by employers, by contracting authorities, in tender processes, at borders, at the roadside.

Today that document is a PDF. It is trivially editable, tedious to verify, and — the important part — it still looks valid after the policy has lapsed. Nobody checking a certificate can tell whether the cover behind it is still in force.

Issued as a credential into the customer's wallet, proof of cover is verifiable instantly by whoever is asking, and it can be revoked the moment cover ends.

For commercial lines in particular, where certificates of insurance are part of contracting and procurement, this removes a genuine administrative burden on both sides.

Build vs buy: how to build a compliant solution

Whether acting as verifier, issuer, or wallet provider, an insurer faces the same decision as every other organisation in the ecosystem: how much of the solution to build, and how much to buy. The customer-facing applications — quote and buy journeys, the claims process, broker portals — are where an insurer differentiates and will always be built in-house or with existing partners. The identity layer underneath — credential formats, exchange protocols, trust checks, key management, revocation — is standardised by definition and changes every time the EU specifications evolve. For that layer, there are three possible implementation paths:

• Build apps, buy infrastructure (recommended) — build only the customer-facing applications and use a proven, standards-compliant provider for the identity layer. Fastest time to market, lowest regulatory and technical risk.
• Build apps, own infrastructure — use open-source identity infrastructure to retain full control of the stack, while still avoiding implementing the credential formats, protocols, and trust validation from scratch.
• Build everything in-house — implement and maintain the full stack internally, and keep it current as the specifications evolve. Viable only for organisations with a dedicated identity engineering team.

The walt.id solution

walt.id covers both of the first two paths. The walt.id Community Stack provides open-source issuer, verifier, and wallet infrastructure for organisations that want to own their stack; the walt.id Enterprise Stack is the enterprise-grade offering on top of it — built on open-source technology used by more than +55.000 developers, governments, and businesses. For insurance specifically:

• Verifier, in every format — accept identity credentials, driving licences (ISO/IEC 18013-5), professional attestations and company credentials from one integration, with trust, revocation and wallet-authenticity checks handled automatically and results passed to underwriting, claims and AML systems.
• Issuer — issue proof of cover and certificates of insurance in all mandated formats (SD-JWT VC, ISO/IEC 18013-5, W3C VC), with revocation built into the issuance workflow so a certificate stops being valid the moment cover ceases.
• Cross-border by default — the same verification works for customers, brokers and companies from every Member State, without country-by-country integration.

A role-by-role compliance breakdown is available in the eIDAS 2 Implementers Guide or reach out to our team to learn more.

Frequently asked questions

Do insurers have to accept the EUDI Wallet?

It depends on the line of business. For life and investment products the EUDI wallet can be a great solution for customer authentication, because of the Anti-Money Laundering Regulation which brings customer due diligence obligations from 10 July 2027 and expressly allows eIDAS-conformant electronic identification.

Can insurers verify a driving licence directly from a customer's wallet?

Yes. The EU digital driving licence is being introduced under Directive (EU) 2025/2205 and is issued into EUDI Wallets, using the international mDL standard. An insurer can verify cryptographically licence categories, validity, issue date and more.

Can insurers issue proof of cover into customer wallets?

Yes, and the interesting part is revocation. A PDF certificate still looks valid after a policy ends; a credential can be revoked the moment cover ends, so whoever checks it gets an answer about current cover rather than evidence that a policy once existed.

Does wallet-based identification satisfy AML obligations?

It satisfies the identification and verification step. Sanctions and PEP screening, risk assessment and ongoing monitoring remain the insurer's responsibility, exactly as they are today.