What is an eID-native identity platform? | Identity Infrastructure Explained

Key takeaways

• An eID-native identity platform uses eIDs, bank IDs and digital identity wallets as the primary verification path, with document and selfie checks as the fallback.
• Identity verification now spans 3 generations of methods: identity documents and biometrics, national eIDs and bank IDs, and digital identity wallets such as the EU Digital Identity (EUDI) Wallet.
• By 24 December 2026, every EU Member State must provide at least one EUDI Wallet. From 24 December 2027, private relying parties, except micro and small enterprises, must accept it wherever strong user authentication for online identification is required by law or contract.
• The EU Anti-Money Laundering Regulation (AMLR) applies from 10 July 2027 and recognises electronic identification means at assurance level substantial or high as a route to verify customer identity.
• An eID-native platform orchestrates all 3 generations through one integration: routing, fallback and method coverage per country.

What does eID-native mean?

Most identity stacks grew up document-first: a photo of an ID card or passport, a selfie and a liveness check. An eID-native stack reverses that order. The primary path consumes structured, cryptographically signed data from government schemes, banks and wallets, and the document scan exists for users and markets where no eID is available. The term is defined in the Identity Orchestration Glossary.

An eID-native identity platform applies that architecture as a product: one place where a regulated business connects eIDs, bank IDs, wallets and document checks, and decides which method each customer sees first.

What are the 3 generations of identity?

The first generation of identity verification is the identity document and biometrics: a photo of an ID card or passport, compared with a selfie of the person holding it. Document and selfie checks work in almost every country and remain the method of last resort where nothing else is available.

The second generation is national eIDs and bank IDs: electronic identification issued by governments or provided by banks, where the person logs in with credentials they already use and the business receives verified data from the source. Which eIDs and bank IDs exist, and what data they return, differs by country, as How do you choose identity verification methods for each country? explains.

The third generation is digital identity wallets. In the EU, eIDAS 2.0 requires every Member State to provide at least one EUDI Wallet by 24 December 2026. The wallet holds a person identification data set and attestations, and shares only the attributes the user agrees to present.

Why are regulated businesses moving from documents to eIDs?

Document and selfie checks are under pressure from generative AI. Synthetic identities, deepfakes and injection attacks make a photo of a document weaker evidence than it used to be, as Beyond deepfakes describes. eIDs, bank IDs and wallets return data signed at the source, which a fraudster cannot edit in an image file.

For the business, an eID-first flow has 3 practical effects. Verification costs less than a document and selfie check. Onboarding feels as fast as paying with Apple Pay or Google Pay, so more genuine customers complete it. And the result rests on cryptographic proof from the source, so the business can trust it.

What does the EU AMLR mean for identity verification?

The EU Anti-Money Laundering Regulation (AMLR) applies directly in all Member States from 10 July 2027. It sets the customer due diligence rules for obliged entities such as banks, payment institutions, crypto-asset service providers and gambling operators, including how they identify customers and verify their identity.

Article 22(6) of the AMLR recognises 2 routes to verify a customer's identity: identity documents together with, where relevant, information from reliable and independent sources, or electronic identification means at assurance level substantial or high together with relevant qualified trust services. The EUDI Wallet is one such means.

The draft regulatory technical standards on customer due diligence (draft CDD RTS) make electronic identification the expected first choice. Under the draft CDD RTS, obliged entities are expected to verify customers remotely using electronic identification at assurance level substantial or high, including the EUDI Wallet, or relevant qualified trust services under eIDAS, wherever possible. Alternative solutions are reserved for cases where a natural person cannot reasonably be expected to present an identity document, passport or equivalent in a face-to-face context and does not have access to electronic identification means or relevant qualified trust services meeting the requirements of Article 22(6)(b) of the AMLR. The obliged entity must be able to justify why the customer could not be verified using the methods referred to in Article 22(6). AMLA submitted the draft to the European Commission on 1 October 2026, and the Commission may still amend it. What the draft changes is covered in How to verify customers remotely under AMLR.

The AMLR also sets one customer data set for the whole EU. For a natural person, Article 22(1) requires, among other data, all names and surnames, place and full date of birth, nationalities and usual place of residence. A single eID does not always return all of it: in the eIDAS minimum data set the current address is optional, and so is the resident address in the person identification data of the EUDI Wallet, as How do you choose identity verification methods for each country? explains.

Identity checks under the AMLR continue after onboarding. Article 26 of the AMLR requires customer information to be updated at least every year for higher-risk customers, at least every 5 years for all other customers, and whenever relevant circumstances change. An eID or wallet lets the customer confirm current data with the same method used at onboarding.

How identity platforms compare on AMLR requirements is covered in Best AML and KYC identity verification platforms. Readiness can be checked with Are you ready for July 2027? A 32-question SCA & AMLR readiness checklist, and the key terms are defined in the AML and KYC Glossary.

How is an eID-native platform different from document-first identity verification?

A document-first identity verification service starts every customer with a document photo and a selfie and adds eIDs case by case, if at all. Its core is image analysis and fraud detection on pictures that the user supplies.

An eID-native platform starts with the methods that return verified data from the source and keeps the document check for customers and countries without them. Its core is orchestration: knowing which methods exist in each country, at what assurance level, what data each returns, and routing each customer accordingly. The 2 approaches use some of the same tools. They differ in which tool comes first.

How does one infrastructure orchestrate 3 generations of identity?

Orchestration is what turns many methods into one product. Through one integration, the platform routes each customer to the best available method for their country, falls back to the next method if the first one fails or is unavailable, and keeps track of which method and data were used. Routing, fallback and method coverage are the building blocks of that layer. What a verification result should record is covered in What does "verified" mean in identity verification?

eID-native identity platform:
how does one infrastructure orchestrate 3 generations of identity?

Which eIDs and bank IDs are available on the primary path differs by country.

A business that connects eIDs one by one meets 2 problems. Each national eID scheme, bank ID and EUDI Wallet is a separate integration to build, certify and maintain. And one credential often lacks part of the data the AMLR requires, so the missing attributes have to come from another source. An orchestration layer solves both: one integration covers all methods, and the EUDI Wallet can present several attestations in a single request, known as combined presentation.

Orchestration also covers what happens behind each method. One method can be delivered by one or more providers, and a platform can switch between them when one goes down, as What happens when an identity verification provider goes down? explains. For the EUDI Wallet, the same layer handles verifier integration, as described in Which identity orchestration platforms support EUDI Wallet integration? The capabilities to expect are listed in What capabilities should an identity orchestration platform provide for EUDI Wallet adoption?

What should you look for in an eID-native identity platform?

1. Which eIDs and bank IDs does it cover in your markets, and at what assurance level?
2. Can it accept EUDI Wallets as they launch, and what does it need from you to do so?
3. How does it fall back to document and selfie checks, and can you set the order of methods per country?
4. What does the verification result record: which method, which source, and when?
5. Which certifications and test reports can it show, and on what terms?
6. Can you show the EUDI Wallet and eIDs first and offer document checks only when no eID is available to the customer?
7. Does it record why a customer was verified with a document instead of an eID?
8. Does it build on open standards and interoperable interfaces?

How to check certifications is explained in Which certifications should an identity verification provider hold in the EU?

How does Authologic build eID-native identity infrastructure?

Authologic is a tech company that builds eID-native identity infrastructure to help regulated businesses identify, onboard and authenticate their customers. Its single API connects 140+ identity methods across 250+ countries and territories, leading with electronic IDs (eIDs), bank IDs and digital wallets, and falling back to document and selfie checks. Authologic matches every customer to the most secure, best-converting and lowest-cost method available.

New EU rules, including eIDAS 2.0 (the updated digital identity framework) and the Anti-Money Laundering Regulation (AMLR), are moving regulated markets from legacy verification towards cryptographic identity. Authologic is the only platform covering all three generations of identity, from document checks to eIDs and digital wallets, and runs its own EU Digital Identity (EUDI) Wallet infrastructure.

Authologic is a registered non-qualified trust service provider issuing electronic attestations of attributes and a member of the OpenID Foundation. The methods available in each country are listed on the Integrations page.

Identity Infrastructure Explained: the series

This page is the starting point of the Identity Infrastructure Explained series. Each part answers one question buyers ask before choosing an identity provider:

• What happens when an identity verification provider goes down?
• Which certifications should an identity verification provider hold in the EU?
• How do you choose identity verification methods for each country?
• What does "verified" mean in identity verification?
• What capabilities should an identity orchestration platform provide for EUDI Wallet adoption?

FAQ

What is an eID-native identity platform?

An eID-native identity platform is identity infrastructure that uses government eIDs, bank IDs and digital identity wallets as the primary way to identify, onboard and authenticate customers, with document and selfie checks as the fallback. One integration connects all methods and routes each customer to the most suitable one available in their country.

Does eID-native mean that document checks are no longer used?

An eID-native platform keeps document and selfie checks as the fallback. They remain necessary for customers without an eID, for countries where no eID or bank ID is available and when an eID method fails. The difference lies in the order: eIDs and wallets come first, documents second.

What is the difference between an eID and a bank ID?

An eID is electronic identification issued or recognised by a government, such as a national eID card or a government identity app. A bank ID is identification provided by banks, based on the identity checks the bank performed when it opened the account. Some bank ID schemes are notified under eIDAS, others operate under national rules.

Is the EUDI Wallet an eID?

The EUDI Wallet is an electronic identification means under eIDAS 2.0. Every Member State must provide at least one EUDI Wallet by 24 December 2026. Under the AMLR, the EUDI Wallet is one of the electronic identification means a business can use to verify customer identity.

Does the AMLR require eIDs for customer verification?

The AMLR recognises 2 routes in Article 22(6): identity documents together with, where relevant, information from reliable and independent sources, or electronic identification means at assurance level substantial or high together with relevant qualified trust services. Under the draft CDD RTS, obliged entities are expected to verify customers remotely using electronic identification wherever possible. The AMLR applies from 10 July 2027.

Who needs an eID-native identity platform?

Regulated businesses that identify, onboard and authenticate customers across several EU markets benefit most, such as banks, fintechs, gaming operators and crypto-asset service providers. The AMLR, applicable from 10 July 2027, and the obligation for many private relying parties to accept EUDI Wallets from 24 December 2027 make electronic identification part of their onboarding plans.