Skip to main content
Didit Raises $7.5M to Build the Infrastructure for Identity and Fraud
Didit
Back to blog
Blog · October 25, 2026

8 Best EUDI Wallet Software Platforms in 2026

Compare 8 EUDI Wallet software platforms by live national eIDs, sandbox evidence, production access, wallet credentials, and pricing.

By DiditUpdated
Didit digital ID wallets

Start with the credential you need to accept and the country that issues it. An EUDI Wallet software provider may support a live age check in one market and offer full identity verification only in a sandbox.

  1. Didit
  2. Signicat
  3. Hopae
  4. Trinsic
  5. Authologic
  6. IDnow
  7. Lissi
  8. Procivis

Say you're opening accounts in Denmark and Germany. A Danish customer might already have a digital identity they can use, while your German integration is still in a government test environment. Your engineers can validate the wallet handoff in Germany and keep a separate document route available to customers. The German EUDI Wallet project describes the sandbox as a test-data environment and plans its first public release for early 2027.

The service requesting the credential is the relying party. It might ask for person identification data (PID) to verify a new customer, or only proof of age to let someone access a restricted service. Those are different requests. A working proof-of-age presentation tells you little about whether the same provider can return the identity fields your onboarding policy requires.

For each country, find out which wallet and credential the provider can verify, where you can test it, and who can use it in production. If you still need to decide which parts of the integration to operate yourself, start with the EUDI Wallet integration guide.

The 8 best EUDI Wallet software platforms in 2026

1. Didit

Didit fits teams that already need national eIDs and document verification in the same onboarding flow. The ID Verification step lets you configure digital ID methods by country. In Denmark, for example, you can enable MitID personal and configure a document fallback for someone who can't complete the digital ID check. The result can continue through the other checks you've configured for that onboarding session.

MitID personal and Finnish Trust Network cost $0.25 each per completed wallet verification. BankID Sweden costs $0.20. A document fallback runs separately and is billed according to the checks it uses. Estimate the cost of fallback using Didit's rates for individual checks and the document, liveness, and face match steps in your workflow.

Didit lists EUDI Wallet acceptance as coming soon for the same workflow and has published neither a launch date nor a price. You can test the available national eID and document routes today. If your milestone requires an actual EUDI credential presentation, plan that test around a verifier that can already demonstrate your target wallet.

2. Signicat

Signicat's eID and Wallet Hub suits organizations that already connect several European identity methods and want wallet requests to go through the same hub. Its developer documentation recommends OpenID Connect or its Authentication REST API for new wallet integrations and also describes a SAML route.

The sandbox guide pairs the connector with the iGrant Data Wallet. You load mock PID onto a phone, approve the request there, and inspect the attributes returned to your application. Run that flow early if you already map identity claims into an account record. You'll see which fields your mapping expects and which it actually gets back.

Signicat's pricing can include setup, subscription, and transaction fees. It shows method rates in its dashboard. Ask which charges apply to the EUDI connector and which apply to the national eIDs you intend to keep. Request access conditions for each production wallet separately from the test account.

3. Hopae

Hopae Connect is a single-API option for teams that want to add digital ID methods to an existing identity stack. Hopae documents testing Germany's d-you and Denmark's AltID through its sandbox. Its October 2026 announcement describes those two connections as sandbox-only for Hopae. If either is part of a planned launch, get the current production status for your use case in writing.

There is a separate piece of verification evidence. The OpenID Foundation's verifier conformance listings include Hopae Connect's August 2026 implementation for OpenID4VP 1.0 and the High Assurance Interoperability Profile (HAIP) for SD-JWT VC and mdoc presentations. Use that listing to ask which version you'll run and which credentials the sandbox can present. National production access has its own requirements.

Ask for a proposal that names the methods you're buying. If your pilot covers 2 countries, get separate terms for sandbox access, each production method, and any relying-party onboarding assistance.

4. Trinsic

Trinsic's identity acceptance network is worth checking when you need to know what a particular wallet returns today. Its documentation lists French France Identité age proofs as live via EUDI protocols, with full PID available in test. It also lists live Danish AltID age verification and says production AltID PID access requires a Danish entity. Germany is listed as test-only for PID. Denmark's public digital services portal explains how AltID proves a user's age.

Trinsic also has a reference wallet for testing the full round trip. Use it to build the handoff and complete an onboarding session with test data. Then repeat the test with the target national wallet and the exact attribute request you plan to ship. Pay particular attention to entity eligibility if your service operates in Denmark through a company established in another country.

The public pricing route leads to a contact form. Ask for the rate for each live credential type, whether the same agreement covers later markets, and how failed or abandoned attempts affect billing.

5. Authologic

Authologic is an option for product teams that want to see how a wallet request will work alongside other identity routes. Its free EUDI & Wallet Playground demonstrates how an end user presents PID, approves an authentication request, or interacts with a signing flow. Authologic also describes credential verification as part of its identity orchestration platform.

Bring a specific handoff to the next demo. If you ask for proof of age, check whether the application receives a boolean result, a date of birth, or some other field. Then cancel the presentation and see how your onboarding flow resumes. The answer affects what you can store and when you need the existing fallback route.

Request commercial terms for your live use case, including the issuer and credential scope, country access, and any fallback provider billed separately.

6. IDnow

IDnow's Trust Platform has a documented EUDI Wallet verification step inside its broader onboarding workflows. The v2 step is marked stable and generally available. It exposes outcomes for the application to route, including a successful verification and unsuccessful presentations. That can suit teams that want a wallet result to continue into a flow that also uses document or assisted verification.

For procurement, distinguish availability of the workflow step from availability of the wallet and credential in a specific country. Ask IDnow to activate the exact step in your test environment. Walk through the response fields your onboarding system needs, then ask which national wallet routes IDnow can enable for your legal entity in production.

Get a scoped quote for the wallet step and the alternate verification methods that your risk policy allows. If you use assisted verification for exceptions, budget it as its own class of event.

7. Lissi

Lissi's EUDI Wallet Connector fits teams that want to operate the connector in their own environment. Its software runs as containers in a customer data centre or private cloud, with Helm charts for Kubernetes. The same REST API covers wallet interactions such as requesting PID and issuing credentials.

Lissi publishes sandbox use cases, and the OpenID Foundation lists version 3.5.0 of its connector for the OpenID4VP and HAIP mdoc and SD-JWT VC verifier profiles. If you run it yourself, include certificate renewal, a software update and log access in the pilot. Your platform team needs to know what happens when it deploys a new connector version or replaces an expiring certificate.

Licence fees are contractual. Compare the connector licence, support, hosting, and maintenance hours. Ask whether non-production environments and multiple legal entities fall under the same contract.

8. Procivis

Procivis One is a modular credential stack with a verifier for relying parties. It is worth considering if one division needs to validate credentials and another plans to issue them. The vendor documents the components and provides a hosted trial on request.

Its EUDI interoperability documentation identifies the reference components and versions it tests, including flows for PID and mobile driving licences. Ask for the row that matches your intended setup. A test where Procivis issues the credential and a reference verifier reads it is different from a test where a national issuer supplies the credential and Procivis verifies it.

Request separate pricing for the verifier and any issuance components you need. If you're evaluating a self-managed setup, confirm who operates the trust material, tracks compatibility changes, and handles certificate rotation.

Compare wallet software by the evidence you can inspect

Platform

Evidence to start with

Procurement question

Didit

Live national eIDs and document checks. EUDI Wallet listed as coming soon.

Confirm the country catalogue for onboarding today and scope EUDI separately.

Signicat

Documented mock PID test via iGrant Data Wallet.

Which connector fees and production entitlements apply?

Hopae

Named d-you and AltID sandboxes. OpenID4VP and HAIP conformance listing.

Which credential can your organization use outside the sandbox?

Trinsic

Vendor docs name live French and Danish age-proof routes and restricted Danish PID access.

Can your legal entity use the exact production route you need?

Authologic

Free Playground and documented credential verification within orchestration.

What result and billing event come out of the live flow?

IDnow

Stable Trust Platform EUDI Wallet v2 step.

Which national wallets are available in your production tenant?

Lissi

Containerised connector, sandbox use cases, and version-specific conformance listing.

Who runs the connector and renews the certificates?

Procivis

Reference implementation interoperability matrix and hosted trial.

Which tested combination matches your issuer, wallet and credential format?

Provider status reviewed 14 November 2026. A public app release, a successful sandbox presentation, protocol conformance, and access for your production tenant are separate pieces of evidence. Ask a supplier to attach a date and a product version to each demonstration.

What does EUDI Wallet acceptance require from a relying party?

Register the organization and the intended use, then request the data that use calls for. Article 5b sets the relying-party registration requirements. The EU rules for relying-party registration apply from 24 December 2026. Give someone in your organization ownership of the registration details, including what data the application asks for and who updates the registration when that request changes.

Member States must provide at least 1 wallet within 24 months of the relevant implementing acts entering into force. The first wallet rules published in December 2024 put that date at 24 December 2026. Article 5f(2) of the amended eIDAS Regulation gives covered private relying parties 36 months, which puts their deadline at 24 December 2027. That provision applies where law or contract requires strong user authentication for online identification, excludes micro and small enterprises, and applies when the user asks to use the wallet. Public bodies and very large online platforms have separate provisions in Article 5f.

The verifier then has to check the presentation and return a usable result to your application. Ask which credential formats it handles, how it validates issuer trust and applicable credential status, and whether it binds each presentation to the expected session. The OpenID4VP 1.0 specification explains how Digital Credentials Query Language (DCQL), verifier identity, and the nonce fit into the request. Didit's developer guide explains how wallet connectors handle credential requests.

How much does EUDI Wallet software cost?

Get the cost of completing the journey you intend to launch. A vendor might bill for opening a session, accepting a credential, or completing another check after the wallet step. A self-hosted connector can shift part of the bill into the licence and the time your engineers spend operating it.

For example, model 10,000 starts. If 6,000 users complete with a wallet, 3,000 complete a separate document check, and 1,000 abandon, ask for the bill for those exact events. Include attempted wallet checks for anyone who went on to complete the fallback. Ask your supplier to show where setup fees, any monthly minimum, and support appear in the quote. Use your own forecast for the mix of wallet and document checks.

Run a pilot that includes a failed presentation

Pick a launch market, a credential type and the decision you need to make. For an age check, start with an age threshold and run it without collecting the full birth date if the credential and applicable policy allow that. For onboarding, use a test identity with the fields your verification policy needs.

  1. Run the request from a phone and from a desktop with a phone available. Check that users can get back to the correct application session after they approve.
  2. Run an expired or otherwise invalid presentation and try reusing a completed response. Confirm that your application gets a rejection it can act on.
  3. Cancel the request and resume through an approved alternative. Check that support can see why the wallet attempt ended and that the fallback preserves the original application reference.
  4. Review what your system retained. Ask whether a reviewer can see the method, result and timestamp without exposing unneeded identity data in logs.
  5. Before approving a launch, ask the supplier to show the production route for your entity and market. Record which team owns registration, credentials, trust updates and outages.

Put the production wallet and credential on the purchase order or statement of work. If that route isn't available yet, agree what can ship using national eIDs or documents, and what evidence must arrive before enabling the wallet path. If you use Didit, configure digital ID checks and document fallback in your existing onboarding flow so you can test handoffs and exceptions now.

Frequently Asked Questions (FAQs)

What is EUDI Wallet software?

For an organization accepting a customer's European Digital Identity Wallet, it's the software that requests a credential, validates the presentation, and gives the result to the service. It can be part of an identity verification platform, a managed eID hub, or a connector the organization runs itself.

Is an EUDI Wallet the same as a national eID?

A national eID is an electronic identification method. An EUDI Wallet holds and presents credentials within the EU wallet framework. A platform can support a national eID today and have a separate release schedule for accepting EUDI Wallet presentations.

Can I test EUDI Wallet software before national production access opens?

Yes. A reference wallet or national sandbox can exercise the credential request, the device handoff, and your application's response handling with test data. Before launch, repeat the acceptance checks against the production wallet and credential your legal entity is entitled to use.

Does buying a verifier complete relying-party registration?

Article 5b requires relying parties to register. Some suppliers can assist or support an intermediary arrangement. Confirm who is identified to the wallet, whose registration and certificates the flow uses, and who updates the record if the purpose or data request changes.

Can an EUDI Wallet replace my full KYC process?

A wallet can supply evidence for the identity step. Your remaining obligations depend on the service and its risk rules. For example, accepting a customer's PID does not perform a sanctions screen or establish who owns a corporate customer.

Infrastructure for identity and fraud.

One API for KYC, KYB, Transaction Monitoring, and Wallet Screening. Integrate in 5 minutes.

Ask an AI to summarise this page