eIDAS 2.0 and the EUDI Wallet: Integrating Digital Identity into Enterprise IT Architecture

SHARE:

eIDAS 2.0 and the EUDI Wallet

With the EUDI Wallet, users present digital credentials in different transactions. This raises a concrete architectural question for companies: where do these credentials enter the system, how are their origin and validity assessed, and how is the result passed to the relevant application?

In many companies, identity verification, customer logins and electronic signatures are handled by separate applications. This separation often reflects how systems have evolved over time: a service was added for onboarding, a login solution for the customer portal, and a separate signature workflow for contract signing. The result is a landscape of different data models, interfaces and responsibilities.

With the EUDI wallet, digital identity information originating outside a company’s own systems enters a process. The architecture needs to define how applications handle that information and what they receive to support a decision.

Separate systems, separate identity logic

An onboarding method, a customer-portal login and a separate signature workflow: each solution often follows its own process. Data is collected more than once, which can mean that context is lost as users move between applications. Changes to processes or requirements affect several systems.

For teams, this means manual hand-offs, bespoke interfaces and recurring maintenance effort. New digital processes bring further integrations, while operations and governance teams support multiple variants.

Wallet credentials, accounts and authentication

Customer accounts, identity credentials and authentication serve different purposes. The wallet does not replace customer accounts or access management; depending on its implementation, it can also be used for authentication and electronic signatures. It introduces another source of credentials into the process. Companies need rules defining which information is used for each process and how the result is passed on.

For architecture planning, it helps to keep responsibilities distinct:

  • Identity credential: Information about a person or organization presented for a particular process.
  • Authentication: The process through which a person authenticates to a service.
  • Authorization decision: Determines which actions or resources are permitted for an account.
  • Electronic signature: A step in the document and signing workflow. A qualified electronic signature (QES) has its own requirements.

During onboarding, electronic identification is used to establish identity. A wallet-based credential may be used during onboarding or in a later process, depending on the use case. These processes are connected, but they serve different purposes.

Consider the full customer relationship

Onboarding marks the start of a digital customer relationship. It is followed by logins, changes to personal data, approvals, contract actions and recurring access. An architecture focused only on the initial interaction leaves these later events out.

For each process, teams should define which information is needed, which service assesses it and what result is passed to the next application. This keeps responsibilities and data flows traceable during recurring interactions.

Add an integration layer for credentials

An integration layer centralizes credential processing. Front ends and back ends use defined outputs rather than implementing separate logic for each credential type. The architecture design specifies:

  • which credentials a process accepts,
  • how origin and validity are assessed,
  • which attributes are passed to Identity and Access Management (IAM) or business applications,
  • what response the process receives to approve or stop an action,
  • how each step is logged.

Modular, API-oriented components separate credential processing from the workflows of individual business applications. Those applications receive the information they need for their specific processes. New methods connect through the defined integration point.

Questions for architecture planning

Before adding new wallet-based processes, map current responsibilities:

  • Which credentials are needed for each business transaction?
  • Which component assesses origin and validity?
  • Which attributes are passed to IAM, and which to the business application?
  • What response does the process need to approve or stop an action?
  • How does logging keep each step traceable?

eIDAS 2.0 and the EUDI Wallet extend the architecture challenge beyond onboarding. For companies, the key design work lies in defining data flows and responsibilities for handling credentials presented from external sources. A central integration point connects the wallet, IAM, authentication and signature processes, while business rules remain in a defined location.

Similar resources

Looking for the best trust services to digitize your business?

Evrotrust’s reliable, well-rounded toolkit will meet all digitization needs your company faces.

Happy office workers