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.

Dominika Cepek

September 4, 2026

Digital Identity Glossary | All terms in one table

Last updated: 4 September 2026

Every term from every Authologic glossary, in one place.

Authologic's glossaries define 22 terms across 4 pages: the roles in the EUDI Wallet ecosystem, the supply side behind them, what a wallet actually holds, and the infrastructure vocabulary of multi-method verification.

This index lists all of them with the layer each belongs to and the question it answers, so you can find a term without knowing which glossary it lives in.

Digital Identity Glossary title card: all terms in one table

How to use this page

Terms are listed alphabetically. The layer column says where a term sits in the ecosystem; the glossary column links to its full definition with practical and legal detail.
Six layers organise the whole vocabulary: supply side, wallet, contents, demand side, infrastructure, regulation. Every term belongs to exactly one.
One term appears in two glossaries by design. PID is defined as a role in part 1 and as a dataset in part 3.

All terms

Term	Layer	Glossary	Question it answers
Article 5f sectoral catalog	regulation	Part 2	Which sectors must accept the wallet, and from when
Combined presentation	contents	Part 3	How attributes from several credentials are requested at once
Dynamic routing	infrastructure	Identity Orchestration	How a verification method is chosen for each user
EAA (electronic attestation of attributes)	contents	Part 3	What a signed statement about a person is, and what it is not
eID-native architecture	infrastructure	Identity Orchestration	Which family of methods sits at the centre of a stack
EUDI Wallet	wallet	Part 1	What the wallet itself is, and who must provide one
Holder	wallet	Part 2	Who keeps the credentials and decides who sees them
Identity fallback	infrastructure	Identity Orchestration	What happens when a verification method fails
Identity orchestration	infrastructure	Identity Orchestration	What connects many verification methods into one flow
Issuer	supply side	Part 2	Who creates a credential and signs it
Method coverage	infrastructure	Identity Orchestration	How far a platform actually reaches, and how to check it
Orchestration layer	infrastructure	Identity Orchestration	Where in the architecture the routing logic sits
PID (person identification data)	wallet	Part 1 and Part 3	What the core identity credential is, and what it contains
PuB-EAA (public body attestation)	contents	Part 3	What an attestation from a public register is worth
QEAA (qualified attestation)	contents	Part 3	What the qualified tier of attestation carries
Qualified and non-qualified trust services	supply side	Part 2	What changes when a provider holds qualified status
Relying party	demand side	Part 1	Who reads data from a wallet, and what that triggers
Relying party intermediary	demand side	Part 1	Who operates the connection to wallets for others
Selective disclosure	contents	Part 3	How one attribute is shared without revealing the rest
Trust service provider	supply side	Part 2	Who supplies signatures, seals, timestamps and attestations
Verifier	demand side	Part 1	Which infrastructure checks that a credential is genuine
Wallet provider	supply side	Part 2	Who builds and operates the wallet app

What each glossary covers

EUDI Wallet & eIDAS 2.0 Glossary, part 1: who does what in the ecosystem - the demand side. The wallet, PID as a role, relying parties, intermediaries and verifiers: who reads data from a wallet and what infrastructure that takes.

Part 2: who issues, who provides, who guarantees - the supply side. Issuers, holders, wallet providers, trust service providers and the two tiers of trust service, plus the Article 5f catalog of sectors that must accept the wallet.

Part 3: what is inside the wallet - the contents. What PID actually contains, the three attestation types and what separates them, and the two mechanisms that shape what leaves the wallet: selective disclosure and combined presentation.

Identity Orchestration Glossary - the infrastructure underneath. Orchestration, the orchestration layer, dynamic routing, fallback, method coverage and eID-native architecture. Not part of the EUDI series: this vocabulary applies wherever more than one verification method is in play.

How the EUDI Wallet glossary series fits together: supply side, wallet contents, demand side, and the orchestration vocabulary underneath

How the layers fit together

A credential is created on the supply side by an issuer, under guarantees provided by a trust service. It lands in the wallet, where a holder keeps it. Its contents determine what can be proved and how much of it leaves the wallet in any single request. On the demand side, a relying party asks for attributes and verifier infrastructure checks them, either built in-house or operated by an intermediary. Underneath all of it sits the infrastructure layer, which decides which method a given user is routed to and what happens when that method fails. Regulation cuts across the whole picture and determines who has no choice but to take part.

The layers are not a hierarchy. They are a way of asking where a term belongs, which is the fastest route to understanding what it does.

What is not defined here yet

Two terms appear across these glossaries without a definition of their own: assurance levels, meaning the low, substantial and high tiers eIDAS defines for electronic identification, and qualified electronic signature (QES). Both are the subject of part 4.

Part 5 will cover the trust framework in practice: certification, trusted lists, conformity assessment and cross-border recognition. Further glossaries will extend this index beyond the EUDI ecosystem, starting with AML and KYC.

To test your own position against the vocabulary, see the EUDI Wallet Readiness Checklist and Are you ready for July 2027? A 32-question SCA & AMLR readiness checklist.

Changelog