eIDAS 2.0 and EUDI Wallets

eIDAS 2.0 Identity Verification API

Build a relying-party integration for supported EUDI Wallet presentations with an API and TypeScript SDK. Verify the evidence your flow requests, then apply your own regulatory and business rules.

01 / eIDAS 2.0 and EUDI Wallets

Connect your service to wallet presentations

The European Digital Identity framework introduces wallets and electronic attestations into a broader identity ecosystem. A verification integration still needs to request specific evidence, validate the presentation, and decide how that evidence may be used.

  • Create a session for the credential claims and formats your service accepts
  • Let the user review and approve the presentation in their wallet
  • Return the verification outcome to your application

02 / eIDAS 2.0 and EUDI Wallets

Keep verification distinct from compliance decisions

A technically valid credential is evidence for your process; it is not an automatic legal conclusion. Your team must define the lawful purpose, required assurance, accepted issuers, retention period, and downstream decision rules.

  • Configure issuer and credential trust for your use case
  • Request only the attributes required for the stated purpose
  • Keep eligibility, KYC/AML, and account decisions in your policy layer

03 / eIDAS 2.0 and EUDI Wallets

Prototype the relying-party flow

Use the sandbox and implementation guides to exercise wallet requests and verification responses before production. Confirm the credential and wallet profiles required by your jurisdiction and customer journey.

  • Start with the EUDI integration checklist
  • Use the API reference and SDK quickstarts for implementation
  • Plan for issuer, wallet, and trust-list differences across markets

Continue exploring

Implementation guides and related pages

DLBR provides presentation verification infrastructure. It does not itself grant notified status, register a relying party, issue credentials, establish a legal basis, or determine whether a service satisfies a particular eIDAS obligation.