Logging in with EUDI wallets

We connect wallet login to your existing portal through the Ver.iD platform, with agreed rules for requesting data and linking accounts.

Discuss your wallet login

Illustrative wallet login setup

An integration with your existing portal

Registration and data: Use, the data request, trusted issuers and required certificates are documented.
Authentication and accounts: Ver.iD provides the authentication result through OIDC; your portal handles accounts and access.
Certificates and use: Ver.iD manages certificates through the platform. Test scenarios, go-live and support are agreed.

European Digital Identity wallets (EUDI wallets) let users log in to your own portal or application. Multiple wallets and providers can coexist within a Member State. Users confirm their identity with their own wallet and gain access to their account and your online services.

We connect this login option to your existing portal and identity and access management (IAM) environment. You determine which identity data is needed; your accounts and access rules remain the starting point. This service is delivered on the Ver.iD platform.

More about trust frameworks More about the categories in eIDAS 2.0 More about EUDI wallets

From wallet to your service

From login to access

Identity from the wallet: The user shares the requested identity data from their own EUDI wallet.
Logging in to your portal: The verified identity is used to link the user to the correct account.
Access to your services: The user continues in your portal with the permissions associated with their account.

We arrange registration and certificates, help you select the data and issuers you need, and integrate wallet login with your systems through OpenID Connect. With your team, we agree how privacy, accounts, access rules and day-to-day use will be handled.

What do we need to arrange to request the right data from wallets? We guide relying-party registration and arrange the required registration and access certificates. Together we determine the identity data and additional credentials needed, the issuers you trust and the acceptance agreements that fit your service.

PID means person identification data; PID providers issue that data. We assess the data, sources and trust conditions your service needs. We also help assess the purpose, necessity, legal basis and any additional privacy requirements, particularly for sensitive data. The people responsible in your organisation confirm the decisions. The registered data request and technical setup must reflect them.

Example configuration choices

What does your portal request?

Purpose and data: Which PID data or additional credentials are needed, for what purpose and from which trusted issuers?
Registration and privacy: Registered use, the data request and applicable privacy conditions align.
Registration and access certificates: The required certificates are arranged with authorised parties and configured for the integration.

Add EUDI wallet login to the environment where you already manage accounts and access. Our specialists implement the connection through OpenID Connect (OIDC) with your technical team. This standard lets your application or IAM platform receive the authentication result from Ver.iD.

We assess the configuration of environments such as Keycloak, Okta, Auth0, PingOne, Amazon Cognito or Microsoft Entra External ID. We agree the required data and account linking and test the agreed login scenarios. Your application or IAM platform validates the result and manages sessions, permissions and account recovery. A matching name or email address alone is not sufficient evidence for linking an account. Any use of shared data for registration or forms falls within the agreed scope.

View wallet login on the platform More about verifying data

Example login responsibilities

From identity to access

OIDC integration: Ver.iD acts as the identity provider; your application validates the received authentication result.
The correct account: Your account process determines the link and what happens with an unknown user.
Session and permissions: Your portal starts the session and applies its own access rules.

How do we make sure the integration works and certificates are properly managed? Ver.iD manages certificates through our platform, including security, renewal and revocation. We test the agreed login scenarios and exceptions. You receive findings that let your team assess whether the process is ready for use.

After approval we guide the agreed go-live. We document how changes and incidents are handled and what support is available. Your organisation remains responsible for its own portal and connected systems.

Illustrative test scenarios, not test results

Test login and certificate management

Authentication successful: The portal validates the result and handles the agreed account link.
No matching account: The account process determines the next step without automatically granting access.
Certificate invalid or expired: We test the response to an invalid certificate and agreed recovery or renewal steps.

We work with your existing portal, the people who manage it and the agreements already in place. Before starting, we agree what we will deliver, the work required and the conditions for your team to accept the integration.

Our specialists

Our specialists configure the platform and implement the OIDC integration with your technical team or IAM provider. We help you make informed choices and clarify dependencies on wallets, certificate providers and suppliers. Ver.iD manages the associated certificates and keys through the platform.

Your team and suppliers

You share how login, accounts and access currently work and involve the administrator or provider of your IAM environment. You provide technical contacts and the agreed test environment. Your organisation confirms the data request, privacy choices and access rules.

Reviewing the result together

We agree in advance which login scenarios and exceptions must work. During the review, we discuss test findings and outstanding issues. Your team decides whether the integration meets the agreed conditions and can go live.

What you receive at handover

The agreed registration, certificate setup and tested OIDC integration with your application or IAM platform.
Test findings, documented agreements on credential acceptance and accounts, and outstanding decisions.
Agreements and instructions for go-live, configuration and certificate management and support.

We complete the engagement once the agreed results have been delivered and accepted. We document the guidance included for go-live, who handles subsequent changes and incidents, and the support agreed.

Yes, it prepares your online service to accept wallet login. We work through the required setup, agreements and integration. Other use cases or organisation-wide questions are scoped separately; this service is not a general assessment of every eIDAS obligation.

Is this preparation for eIDAS 2.0?: Yes, it prepares your online service to accept wallet login. We work through the required setup, agreements and integration. Other use cases or organisation-wide questions are scoped separately; this service is not a general assessment of every eIDAS obligation.
Do you arrange registration and certificates?: Yes. We guide registration and arrange the required certificates with the authorised parties. The registration certificate describes the registered use and data request; the access certificate authenticates the relying party to the wallet. Ver.iD manages certificates through the platform, including security, renewal and revocation.
How do we handle sensitive data?: We help determine the data your application needs and the conditions for requesting and processing it. With the responsible parties we assess purpose, necessity, legal basis and any additional requirements. We then align registration, the data request and processing accordingly. A registration certificate does not replace that assessment.
Do we need to replace our existing accounts?: No. Your existing accounts and access rules can remain the starting point. Together we determine how the verified identity links to the correct account and what happens when no matching account exists.
Do we also have to accept EUDI wallets from other Member States?: If your service falls under the eIDAS acceptance obligation, you must accept compliant EUDI wallets from all Member States. Whether and when that obligation applies depends on your service. We configure the integration for the common EUDI framework and test it with available wallet implementations.
Can we also use data for a form or registration?: Yes, if the required data and integration are supported and included in the engagement. Together we define the purpose, data request and processing in your application. The intended use and privacy decisions remain part of the agreed review.
What determines planning and costs?: We start with a no-obligation conversation. Planning and costs depend on your existing login environment, account processes, data request and required integrations. We agree effort, test scenarios, go-live and support in advance.

#wallet-login-questions-accordion{display:none!important}

Is this preparation for eIDAS 2.0?

Do you arrange registration and certificates?

Yes. We guide registration and arrange the required certificates with the authorised parties. The registration certificate describes the registered use and data request; the access certificate authenticates the relying party to the wallet. Ver.iD manages certificates through the platform, including security, renewal and revocation.

How do we handle sensitive data?

We help determine the data your application needs and the conditions for requesting and processing it. With the responsible parties we assess purpose, necessity, legal basis and any additional requirements. We then align registration, the data request and processing accordingly. A registration certificate does not replace that assessment.

Do we need to replace our existing accounts?

No. Your existing accounts and access rules can remain the starting point. Together we determine how the verified identity links to the correct account and what happens when no matching account exists.

Do we also have to accept EUDI wallets from other Member States?

If your service falls under the eIDAS acceptance obligation, you must accept compliant EUDI wallets from all Member States. Whether and when that obligation applies depends on your service. We configure the integration for the common EUDI framework and test it with available wallet implementations.

Can we also use data for a form or registration?

Yes, if the required data and integration are supported and included in the engagement. Together we define the purpose, data request and processing in your application. The intended use and privacy decisions remain part of the agreed review.

What determines planning and costs?

We start with a no-obligation conversation. Planning and costs depend on your existing login environment, account processes, data request and required integrations. We agree effort, test scenarios, go-live and support in advance.

Wallet login for your portal.

Logging in to your own portal.

Our guidance.

Registration and data.

Connect to your existing login environment.

Ready for use.

How we work together.