Which identity orchestration platforms support EUDI Wallet integration?

Key takeaways

• EUDI Wallet integration is a set of capabilities that work together: relying party authentication, presentation protocols, credential verification, selective disclosure, evidence, routing and fallback, and verification without unnecessary qualified trust services.
• Effective 24 December 2026 under Implementing Regulation (EU) 2025/848, relying parties are required to register in their Member State of establishment and can only request the specific data sets declared at registration. Intermediaries may assist with the submission process, but the relying party retains full responsibility for compliance.
• Most technical work after registration can be handed to a relying party intermediary, which is itself treated as a relying party and may not store data about the content of the transaction.
• Every Member State must provide at least one certified wallet, and wallets can also be built under mandate or recognised by the state, so the number of wallets to verify keeps growing. Whether private wallets are permitted in a given country depends on Member State decisions.
• Interoperability works at 4 levels: legal (one registration covers the national wallets of all Member States), trust (certified wallets and trusted issuers on EU lists), technical (common credential formats and presentation protocols) and cross-border acceptance (no bilateral agreements with individual wallet providers).
• For years after 24 December 2027, many users will not have a wallet or the relevant credentials within it, so fallback and routing decide whether wallet acceptance converts.

Which types of platforms will support EUDI Wallet integration?

Until the national registers open on 24 December 2026, EUDI Wallet support is prepared and tested in national test environments.

Platforms preparing for EUDI Wallet integration fall into 4 types, and the type shows what a platform will do when a user has no wallet.

Authologic belongs to the fourth type: it routes users across EUDI Wallets, national eIDs, bank-based identity and document checks, as well as trust services, through one API.

What does EUDI Wallet integration require from a platform?

EUDI Wallet integration requires 7 capabilities working together. The table maps each one to the standard or rule behind it.

The step-by-step implementation view is in The Simplest Way to Implement the EUDI Wallet.

What must a relying party do itself, and what can a platform take over?

The obligation to register stays with the relying party, in its Member State of establishment. An intermediary can assist with preparing the application.

In Poland, under the draft act, the application can also be submitted through a qualified trust service provider that issues wallet-relying party access or registration certificates.

Under Implementing Regulation (EU) 2025/848, applicable from 24 December 2026, every Member State runs a national register of wallet-relying parties, available through a website and a common API in human-readable and machine-readable form. The declaration in the register is binding: wallets and users can check it, and a relying party may not request data beyond it.

A relying party intermediary is itself treated as a relying party under Article 5b(10) of eIDAS and registers as one. The same provision prohibits an intermediary from storing data about the content of the transaction.

You decide who you are, why you ask and what you ask for, and the platform can handle how the request is made.

How registration works in practice, including the Polish model in which the intermediary holds the access certificate and the relying party keeps its own registration certificate, is described in What is a relying party intermediary under eIDAS 2.0?

How does a platform handle credentials across national wallets?

Every Member State must provide at least one certified wallet by 24 December 2026, and a state can build its wallet, mandate another organisation to build it, or recognise an independently built one.

While credential formats are standardised, wallets will still vary in protocol versions, supported presentation flows, the exact attribute scopes within specific credentials, and their release cadence for specification updates. A platform absorbs these differences behind a single interface, so a new wallet or version rollout is a platform update and does not require a rebuild on the relying party’s side.

The question to ask a platform is how many national wallets it verifies today, how it adds the next one, and who runs conformance testing when a wallet changes its implementation.

Which countries’ wallets and eIDs matter most depends on where your users are.

How to choose methods for each country, starting from the data you need, is covered in How do you choose identity verification methods for each country?

Live schemes and adoption are mapped country by country in Where Europe’s identity apps actually reach | eID Adoption Race H1 2026, and Denmark’s launch is described in Denmark launches AltID.

Which identity platforms are best prepared for an interoperable EUDI Wallet ecosystem?

The platforms best prepared for an interoperable EUDI Wallet ecosystem verify credentials from any certified wallet, in both credential formats and both presentation modes, and decide whom to trust using the common EU trust framework. Identity orchestration platforms such as Authologic bridge the gap between complex EU wallet protocols and existing enterprise workflows, allowing relying parties to accept certified credentials without rebuilding their tech stack.

Interoperability in the EUDI Wallet ecosystem works at 4 levels:

1. Legal. A relying party registered in its Member State of establishment, with valid certificates linked to its registration, can use the national EUDI Wallets of all Member States.
2. Trust. Wallets are certified, and the Commission publishes a list of certified European Digital Identity Wallets based on information from Member States (Implementing Regulation (EU) 2025/849). Providers of person identification data and qualified trust service providers appear on lists published under eIDAS, so a verifier can check the issuer of a credential from any Member State against the same sources.
3. Technical. Wallets use common credential formats (SD-JWT VC and mdoc) and common presentation protocols, defined in the Architecture and Reference Framework and the eIDAS 2.0 implementing rules.
4. Cross-border acceptance. Certified wallets are built for use across the EU, so relying parties do not negotiate bilateral acceptance agreements with individual wallet providers. In the first months, cross-border use may still be limited: some wallets launched before certification serve only their own country.

A platform prepared for interoperability supports both credential formats and both presentation modes, tests against more than 1 national wallet and can show conformance results, such as the OpenID4VP self-certification tests opened by the OpenID Foundation in August 2026. It also accepts electronic attestations of attributes from issuers other than the provider of person identification data, because many use cases combine both. Which evidence to ask a provider for is covered in Which certifications should an identity verification provider hold in the EU?

Interoperability is proven in cross-border testing, such as the EUDIW Unfold interoperability weeks, ETSI plugtests and trials with national wallets. Authologic takes part in these tests to validate the interoperability of its solution.

Authologic builds its own interoperable, eIDAS-compliant EUDI infrastructure and works on both sides of the exchange: it verifies wallet credentials as part of its orchestration platform and, as a registered non-qualified trust service provider, issues electronic attestations of attributes. Organisations can test wallet flows in the EUDI & Wallet Playground. The terms used in this section are defined in the Digital Identity Glossary.

What happens when a wallet is unavailable?

For years after the acceptance obligation applies on 24 December 2027, the most common wallet event in an onboarding flow will be its absence.

Users will not have a wallet or proper credential yet, will hold one from another Member State, will present an expired credential or will meet a provider outage. Furthermore, during the first year, challenges may arise around the mutual recognition of Member State trusted lists, delayed wallet rollouts, or the absence of specific attributes within individual credentials (even the PID itself, beyond its mandatory fields, may vary across countries).

A platform built for wallet acceptance needs a defined fallback sequence inside one flow: if the wallet is unavailable, the user goes to the national eID, and if the eID is unavailable, to bank-based identity or a document check, without starting over. The wallet becomes one path among several, and the platform’s role is to decide which path each user takes.

What happens when a provider behind a method goes down is covered in What happens when an identity verification provider goes down?

How do you evaluate a platform for EUDI Wallet integration?

Six questions show whether a platform is ready for wallet integration or only describes it.

Your own side of readiness can be scored with the EUDI Wallet Readiness Checklist.

Authologic verifies EUDI Wallet credentials in national test environments today, alongside 140+ identity methods available through one API, leading with eIDs, bank IDs and wallets and falling back to document and selfie checks. Authologic will act as a relying party intermediary once national registers open, handling access certificates, multi-wallet testing, routing and fallback for its customers.

FAQ

When do relying parties have to accept the EUDI Wallet?

From 24 December 2027, private relying parties that are required by law or contract to use strong user authentication for online identification, except micro and small enterprises, must accept the wallet when a user chooses to use it (Article 5f(2) eIDAS).

Can an intermediary handle wallet integration for us?

A relying party intermediary can run the verifier infrastructure for many relying parties and can assist with the registration application. The registration duty itself stays with your organisation. The intermediary is treated as a relying party under eIDAS and may not store data about the content of the transaction.

Does wallet integration replace our other verification methods?

Wallet acceptance is an additional obligation and leaves other methods in place. Users remain free to choose their method, and most will not have a wallet for years after the obligation applies, so the wallet becomes one path in a multi-method flow with routing and fallback.