EUDI Wallet integration for enterprise applications

The European Digital Identity Wallet (EUDI Wallet, or EUDIW) is a framework introduced by eIDAS 2.0, Regulation (EU) 2024/1183, that lets individuals identify themselves and share verified credentials digitally across Europe. Its technical foundations are described in the EUDI Architecture and Reference Framework. For organizations, it creates a new, standards-based way to request and verify identity data.

A relying party is an organization that requests and accepts credentials or identity attributes from a wallet in order to deliver a service, for example a bank, a retailer or an online platform. Becoming a relying party typically means adapting existing applications to request credential presentations and to verify the results as part of an established business process.

OpenID for Verifiable Presentations (OpenID4VP) is an OpenID Foundation specification that defines how a verifier requests, and a wallet presents, digital credentials. It is relevant because it is among the protocols used in the EUDI ecosystem for credential presentation. Which profiles and requirements apply depends on the use case and deployment environment.

OpenID4VCI covers credential issuance: how an issuer delivers a verifiable credential to a wallet. OpenID4VP covers presentation: how a wallet shares credentials with a verifier. Organizations that only need to accept credentials focus mainly on presentation, while those that issue their own credentials also need to consider issuance.

In general, yes. Wallet-based identity is designed to be added to digital services rather than to replace them. The practical questions concern customer journeys, existing identity systems, security requirements and business processes. Convex helps organizations assess these and integrate wallet capabilities into their existing software with minimal disruption.

Often they can. Many organizations already operate identity and access management platforms that support established sign-in and authorization processes. The aim of an integration is typically to connect wallet-based capabilities with those systems rather than replace them. What is feasible depends on the specific platform, the use case and the requirements involved.

No. Accepting a credential from an EUDI Wallet does not by itself establish compliance with KYC or other regulatory obligations. Those obligations depend on the sector, the jurisdiction and the organization's own risk assessment. Wallet credentials can be one input to a compliant process, and organizations should take legal and compliance advice for their situation.

Start with the business use case: which credentials or attributes are needed, and in which customer or employee journeys. Then consider existing identity systems, security and privacy requirements, the applicable regulatory context and interoperability needs. Because standards and regulatory status continue to evolve, they should be reviewed periodically against official sources.

Yes. Convex provides software architecture and engineering expertise and is open to working with identity technology providers, enterprise software companies and system integrators. We contribute to the part of the solution that has to fit existing enterprise software, while partners continue to own their own products and responsibilities.