What is identity verification orchestration?

Identity verification orchestration connects multiple verification methods and providers behind a single API, automatically routing each user to the best method for their country and use case, with instant fallback when a method fails. Instead of integrating vendors one by one, businesses integrate once and gain access to the full landscape of eIDs, wallets, biometrics and document checks.

How many verification methods does Authologic support?

Authologic supports over 90 verification methods from more than 80 providers, covering over 230 countries and territories - including national eIDs, government identity wallets, BankIDs, biometrics and document-based verification.

Is Authologic ready for eIDAS 2.0 and the EUDI Wallet?

Yes. Authologic supports EUDI Wallet integration alongside national eIDs and government wallets such as mObywatel, Diia, SPID and FranceConnect+, helping regulated businesses prepare for mandatory EUDI Wallet acceptance under eIDAS 2.0.

How does Authologic improve onboarding conversion?

By routing users to electronic identity methods instead of document scans wherever available. eID-based verification removes photo capture and manual review, which shortens onboarding and increases pass rates, with automatic fallback to other methods when needed.

How is Authologic different from traditional KYC providers?

Traditional KYC vendors offer their own verification methods; Authologic is a neutral orchestration layer that connects them all. One integration provides access to over 90 methods from more than 80 providers, with routing, fallback and coverage that no single vendor offers.

Jarek Sygitowicz

June 19, 2026

EUDI Wallet & eIDAS 2.0 Glossary: Who Does What in the Ecosystem (pt. 1)

Last updated: August 11, 2026

EUDI basics, made simple. Read and understand the EUDI ecosystem in 2 minutes.

This glossary defines the five core roles in the EUDI Wallet ecosystem under eIDAS 2.0 (Regulation (EU) 2024/1183): the wallet itself, PID, relying parties, relying party intermediaries, and verifiers.

Each entry starts with a plain-language definition and adds the practical and legal detail underneath.

Part 1 covers who reads data from the wallet; EUDI Wallet & eIDAS 2.0 Glossary: part 2 covers who issues credentials and guarantees trust.

EUDI Wallet & eIDAS 2.0 Glossary pt. 1 - cover with a navy map of Europe circled by golden EU stars

The EUDI wallet is set to make our lives easier. We will be able to log in to services without usernames and passwords, onboard to services without plastic documents, and authorise payments and money transfers without one-time passwords sent via SMS.

Let’s see what makes the whole ecosystem work.

What is the EUDI Wallet?

An app on your phone. Each EU country will have one, and they should all work in the same way. The wallet is your document folder or a database of different credentials.

In practice: By December 24, 2026, every Member State must provide at least one certified wallet, and both governments and accredited private entities can issue them - so "one wallet per country" is the floor, not the ceiling. Wallets from different countries must work cross-border: a Spanish user can present their wallet to a German bank. Denmark's AltID is already live.

Who this applies to: Every EU resident (use is voluntary), and every business in the mandated sectors that will have to accept a wallet from December 24, 2027.

Legal basis: Regulation (EU) No 910/2014 (eIDAS), Article 5a, as amended by Regulation (EU) 2024/1183.

What is PID (Person Identification Data)?

Your main government-issued identity credential. In the beginning, you will be able to add PID only to the government wallet. Think about PID as an alternative to your plastic ID document.

In practice: PID covers the core identity attributes - name, date of birth, and other data defined in the implementing acts. The exact data set will differ between Member States: the EU's PID Rulebook defines the common baseline, and countries can add national attributes on top of it. Unlike a document scan, PID arrives as structured, cryptographically signed data issued under a government scheme, which is why it can satisfy customer due diligence requirements under AMLR Article 22 without a photo of a plastic card.

Who this applies to: Issued to wallet holders by or on behalf of the Member State; consumed by relying parties during onboarding, login and payment authorisation.

Legal basis: Regulation (EU) No 910/2014 (eIDAS), Article 3(3) (definition of person identification data) and Article 5a, as amended by Regulation (EU) 2024/1183. Technical reference: PID Rulebook.

What is a relying party under eIDAS 2.0?

(Wallet) Relying party, or RP in short, is a business that wants to read data from the wallet. A car rental company or a bank is a “relying party” that needs to process data from a wallet.

In practice: Relying party status triggers registration obligations: you register in your Member State of establishment and state the purpose and scope of the data you request. Separately, organisations in the Art. 5f sectors - among them banking and financial services, telecommunications, health, energy, transport and education - must accept the EUDI Wallet wherever the law requires strong user authentication, from December 24, 2027. A practical first check: if your organisation holds a banking, payment or e-money licence and falls under PSD2 (transitioning to PSR), the SCA-linked acceptance obligation applies to you.

Who this applies to: Any natural or legal person relying on electronic identification or trust services - from banks and telecoms to a car rental checkout.

Legal basis: Regulation (EU) No 910/2014 (eIDAS), Article 3(6) (definition) and Article 5b (registration), as amended by Regulation (EU) 2024/1183.

What is a relying party intermediary?

Most businesses will work with intermediaries to get access to wallets. It’s easier and much cheaper to use one of the intermediaries than to deal directly with the complexities of hosting your own verifier service.

In practice: An intermediary connects to wallets once and lets many relying parties request and receive data through that single connection - covering protocol differences between wallets, certificate management and updates as the ecosystem evolves. The alternative is hosting, maintaining and testing your own verifier against a minimum of 27 national wallets. The build-vs-intermediary decision compounds over time: every new wallet, protocol version and certification update lands on whoever owns the integration.

Who this applies to: Relying parties that want wallet acceptance without operating verifier infrastructure in-house. Authologic operates as a relying party intermediary.

Legal basis: Regulation (EU) No 910/2014 (eIDAS), Article 5b, as amended by Regulation (EU) 2024/1183, and the implementing regulation on relying party registration.

What is a verifier in the EUDI Wallet ecosystem?

The technical infrastructure needed for Wallet communication is called “verifier”. The name comes from the fact that you need to verify incoming information, if it comes from a legitimate source and hasn’t been tampered with.

In practice: The verifier authenticates itself to the wallet as a registered relying party, requests attributes, checks that the presented credential is genuine, untampered and not revoked, and returns the result to your systems. Note on terminology: the EU's Architecture and Reference Framework (ARF) sometimes uses "verifier" for the relying party role itself; in practice the market distinguishes the business (relying party) from the infrastructure it uses (verifier), which is the distinction this glossary follows.

Who this applies to: Anyone accepting wallet credentials needs verifier capability - built in-house or provided by an intermediary.

Legal basis: Not a defined term in the eIDAS regulation; specified in the ARF and implementing acts.

Infographic explaining EUDI Wallet and eIDAS 2.0 glossary terms including PID, Verifier, and Relying Party.

How do these five roles fit together?

A user holds credentials in the wallet, starting with their PID. A business that wants to read that data is a relying party, and it needs verifier infrastructure to do so - built in-house or provided by a relying party intermediary.

These five roles cover the demand side of the ecosystem: who reads data from the wallet and how. Part 2 covers the supply side - issuers, wallet providers and trust services.

The infrastructure vocabulary behind these roles - orchestration, routing, fallback and eID-native architecture - is defined in the Identity Orchestration Glossary.

To test where your organisation stands against these roles in practice, see the EUDI Wallet Readiness Checklist and the SCA & AMLR Readiness Checklist.

Changelog

August 11, 2026 - Linked part 2 and the Identity Orchestration Glossary, aligned the Art. 5f sector list with the regulation, updated structured data.
July 31, 2026 - Entries expanded with practical implications and legal basis; definitional introduction added.
June 19, 2026 - Initial publication.