Wallet connector

A Wallet Connector lets relying parties accept EUDI Wallet attestations without building the underlying wallet protocols themselves.

A Wallet Connector is the software layer that lets a relying party accept identification, attributes or signatures from the EUDI Wallet without building the underlying wallet protocols itself. It sits between the relying party's application and the wallet: it generates the presentation request, exchanges it with the wallet using OpenID4VC, and checks the returned attestation - signature, issuer trust, revocation status and selective disclosure - before handing back a verified result.

Building this integration directly is demanding: it means handling multiple credential formats (such as mdoc and SD-JWT), validating trust chains against national and EU trust lists, and keeping pace with an evolving Architecture and Reference Framework. A Wallet Connector abstracts that complexity behind a simpler interface, so a webshop, bank or government service can request "a verified age" or "a verified company mandate" and receive a trustworthy answer.

"Wallet connector" is a market term rather than a role in eIDAS or the ARF. The regulated counterpart is the relying party intermediary: Article 5b(10) deems an intermediary acting on behalf of a relying party to be a relying party itself, and forbids it from storing data about the content of the transaction. Using a connector therefore does not move the relying party's own duties: it still has to register in its member state (Article 5b(1)), may ask only for the data it declared at registration (5b(3)), must identify itself to the user (5b(8)) and may not refuse a pseudonym where identification is not legally required (5b(9)).