News
November 19, 2026

EUDI Wallets: what a relying party must do first

Before a business can ask a EU Digital Identity Wallet for data it must register in its Member State, declare what it will request, and not exceed it.

The first constraint a business meets when it decides to accept European Digital Identity Wallets is not technical. Before you can ask a wallet for anything, you register in the Member State where you are established, and you declare in that registration exactly what data you intend to request.

You are then held to it. The European Commission's guidance for service providers states the obligation flatly: do not request any extra user data than what was specified during registration. Data minimisation stops being a principle you interpret and becomes a fact recorded about you in a register.

Registration happens where you are established, not where the user is

The Commission's guidance is that to become a recognised service provider in the wallet ecosystem, you must register in the Member State where you are established. You supply registration information and contact details, and you must inform that Member State of any change to what you registered, without delay.

The guidance is candid that the detail is still arriving, noting that more will be provided as it becomes available. National onboarding processes are the operative layer here, and they are not uniform. If you operate across several Member States, the question of where you are established is worth settling before it is settled for you.

Declaring intended use is the obligation with the longest tail

Registration requires you to detail how you intend to use wallets, specifying the data you will request from users. On its face this is paperwork. In practice it couples your registration to your product roadmap.

Consider what happens when a product team adds a field to an onboarding flow. In a conventional identity integration that is a sprint task. Here, requesting an attribute you did not register is a breach of your obligations as a relying party, and the fix runs through a registration update rather than a deployment. Organisations that treat the registered attribute set as a living artefact, owned by someone, will have a far easier time than those that file it once and forget where it is.

You must identify yourself to the user, and the asymmetry is deliberate

A further obligation runs the other way: a service provider must identify itself to users when it intends to rely on their wallets. The user learns who is asking before deciding what to share.

This inverts the familiar pattern, in which the person proves who they are to an organisation that remains an unverified logo on a login page. It also has a design consequence that is easy to miss. If your request will be presented to the user alongside your identity and the attributes you are asking for, then an over-broad request is now visible to the person best placed to refuse it.

Pseudonyms must be accepted where identification is not legally required

This is the obligation most often skipped in summaries, and it is the one with the sharpest product implications. The Commission's guidance requires service providers to accept pseudonyms where identifying the user is not legally required.

It forces a question most services have never had to answer: for which of our flows is identification actually a legal requirement, as opposed to a convention, a convenience, or an analytics preference? Age-restricted purchasing, to take an obvious case, generally requires proof that someone is over a threshold, not proof of who they are. A service that cannot separate those two things in its architecture will struggle to comply without rebuilding.

Person Identification Data and attestations are different instruments

The ecosystem distinguishes identity from claims about a person, and the vocabulary matters because the trust model differs.

A relying party must carry out authentication and validation procedures for both PID and attestation data. They are not interchangeable: asking for PID when an attestation would do is precisely the over-collection the registration regime is built to constrain.

    What is settled, and what is not

    The European Digital Identity Framework Regulation requires Member States to issue at least one wallet, and the Commission's published timeline gives the end of 2026 as the expected point at which wallets become available. The Commission describes that timeline as tentative, and its own two statements of it reason to the same target by different routes.

    We would rather say that plainly than round it off. If a date is load-bearing in your plan, confirm it against the Regulation itself and against your national implementation, not against a summary. The implementing rules covering issuance, management, and revocation of PID and attestations sit in separate instruments that are worth reading directly.

    What to do while the detail lands

      None of this requires waiting. The registration obligations, the minimisation constraint, and the pseudonym requirement are all knowable now, and all four actions above can be completed before a single wallet is issued in your market. Our identity capabilities page sets out where verification fits in a compliance workflow.

      Would you like to discuss how Semansys supports credential verification and wallet readiness? Book a discovery call