eIDAS 2.0 pushes wallet-agnostic onboarding and QES by default

At a glance

What this is: This is an analysis of how eIDAS 2.0, AMLR and PSR/PSD3 are reshaping digital onboarding, with the key finding that wallet adoption and QES-backed self-ident are becoming the preferred operational path.

Why it matters: It matters because IAM, fraud, compliance and digital channel teams now need one evidence chain for identity proofing, customer due diligence and payment approval rather than separate control stacks.

Context

The central governance gap is no longer whether digital identity will matter, but how institutions will run multiple assurance paths without fragmenting evidence, auditability and customer experience. eIDAS 2.0, AMLR and PSR/PSD3 are converging on the same onboarding journey, so identity verification, due diligence and payment approval can no longer be treated as separate programmes.

In practical terms, the hardest problem is operating model design. Banks need a wallet-agnostic approach that can handle multiple national wallets, fallback proofing routes, and the evidence requirements that accompany supervision and dispute resolution.

Key questions

Q: What should banks do when wallet adoption creates multiple remote identity paths?

A: Banks should standardise one acceptance policy above the individual wallet or channel. The policy should define assurance level, evidence requirements, exception handling and audit review for each journey, so different wallets do not produce inconsistent trust decisions. The aim is not one wallet, but one defensible operating model across many wallets.

Q: When should organisations prioritise QES over video ident in remote onboarding?

A: Organisations should prioritise QES when they need a stronger evidential chain, especially where remote proofing must stand up to supervision, disputes or later legal challenge. Video ident can still exist as a fallback, but it should not be the default where a QES-backed route can provide clearer integrity and accountability.

Q: What breaks when fallback identity journeys are not tightly governed?

A: Fallback journeys often become the least defensible part of the programme. Without clear policy, teams accumulate inconsistent evidence, unclear exception approval and uneven customer treatment, which creates audit risk and weakens later dispute handling. The failure is not just operational slowness, it is the inability to prove why a lower-assurance path was used.

Q: Who is accountable for wallet readiness across onboarding and payments?

A: Accountability should sit with one end-to-end owner for identity and trust journeys, supported by compliance, fraud, legal, operations and IT security. Wallet readiness is not a single-team project because it affects evidence, channel design, service-provider oversight and regulated approval flows. Clear ownership prevents fragmented implementation and inconsistent control decisions.

Technical breakdown

Why wallet interoperability changes onboarding architecture

EUDI Wallet adoption does not create a single common login path. It introduces multiple issuers, credential formats, registration regimes and policy choices, which means relying parties need orchestration logic rather than a one-wallet assumption. That changes routing, evidence capture and exception handling. Institutions that design for one credential type often discover that the real complexity sits in acceptance policy, assurance level mapping and the proof that a given journey met the expected standard. See the Digital Identity, eID and Identity Wallets Guide.

Practical implication: Design onboarding to accept multiple wallet and eID variants without weakening evidence quality.

Why QES becomes the control that closes the remote proofing chain

A qualified electronic signature is not just a signing step. In the flow described by the article, it closes the legally relevant chain after remote identity proofing against a physical document, turning a verification journey into an end-to-end evidentiary path. That matters because the legal strength of the journey depends on how the proofing result, identity evidence and signature are bound together. Where wallet-based proofing is unavailable, the quality of the QES-backed route becomes the main differentiator between a defensible process and a merely convenient one. Read the Ultimate Guide to NHIs: Regulatory and Audit Perspectives.

Practical implication: Make QES support part of the default fallback architecture for remote onboarding and re-identification.

How self-ident shifts the operating model from queues to control points

Self-ident changes the operational economics of identity assurance. Instead of staffing queues and managing human-assisted video sessions as the default, teams must control image quality, fraud signals, exception routing, timing and evidential integrity. That is a governance shift, not just a UX change. The control question becomes whether the institution can prove the journey was executed consistently and whether exceptions were handled under explicit policy, not whether an operator was present. See the NHI Lifecycle Management Guide.

Practical implication: Move from agent capacity planning to governed exception handling and evidence review.

NHI Mgmt Group analysis

Wallet adoption is fundamentally a governance and evidence problem, not a channel-selection exercise. The article is right to frame interoperability, liability and auditability as the real blockers, because a wallet becomes useful only when the relying party can evidence what was accepted, why it was accepted and under what assurance profile. That is an identity governance issue as much as a digital identity issue. Practitioners should treat wallet acceptance as a policy and evidence architecture decision, not a front-end feature choice.

QES-backed self-ident creates a stronger default than video ident because it collapses the legal and operational gap between proofing and signing. The important shift is that the preferred journey is not merely faster, it is easier to defend later under supervision or dispute. That makes the evidence chain itself the control surface, and it should be designed as such from the outset. Identity teams should align policy, evidence retention and exception handling around that continuous chain.

Multiple wallets will widen trust fragmentation unless institutions standardise acceptance logic. There will be more than one wallet, more than one issuer policy and more than one registration model, so relying parties need a consistent assurance model that sits above the individual wallet. This is the kind of fragmentation that creates hidden operational risk because it looks like choice but behaves like inconsistency. Practitioners should standardise acceptance criteria before broad wallet rollout.

Strong onboarding in 2026 will be measured by how well it governs fallback, not by how quickly it adds another remote channel. The article correctly stresses that alternative methods become justified exceptions, not equal peers. That changes the programme scorecard from feature expansion to control discipline, because the weakest route often becomes the one auditors and supervisors scrutinise most. Identity and fraud teams should make fallback behaviour measurable, reviewable and owned.

Read next: NHI Lifecycle Management Guide

What this signals

Evidence-chain governance will become the decisive capability in wallet-era onboarding. Institutions that can prove how identity was established, which fallback was used and why the final decision was defensible will have a cleaner path through supervision and disputes. The programme risk is no longer only fraud or user abandonment, but fragmented evidence that cannot survive review.

Wallet-agnostic design should be treated as an operating principle, not a migration milestone. Multiple national wallets, varying issuer policies and mixed customer readiness mean the trust layer has to sit above the channel layer. Teams should prepare for a future where acceptance logic is standardised centrally while customer journeys remain locally varied.

For practitioners

• Define a wallet-agnostic acceptance policy Map which eID, wallet, QES and fallback combinations are acceptable for each journey, then tie each route to a documented assurance level and evidence package.
• Treat QES as the default fallback control Use QES-enabled remote proofing as the preferred non-wallet path for customers without eID or wallet support, with clear justification rules for exceptions.
• Rebuild onboarding around evidence packages Capture proofing artefacts, verification outcomes, risk decisions, consent and exception rationale in a format that auditors can reconstruct years later.
• Move video ident to an exception model Keep attended or agent-assisted sessions available only where the risk case or customer condition truly requires them, and measure how often they are used.

Key takeaways

• The article frames eIDAS 2.0, AMLR and PSR/PSD3 as one converging trust and evidence chain, not three separate compliance stacks.
• The main adoption risk is operational fragmentation, especially when multiple wallets, credentials and fallback routes produce inconsistent evidence.
• Practitioners should design wallet-agnostic onboarding, make QES the preferred fallback and treat auditability as a product requirement.

Related NHI Mgmt Group resources: NHI Lifecycle Management Guide · Ultimate Guide to NHIs: Regulatory and Audit Perspectives · Digital Identity, eID and Identity Wallets Guide

Key terms

• Electronic Identification Wallet: A digital wallet that stores and presents identity credentials for online and offline use. In the eIDAS 2.0 context, the wallet becomes part of a broader trust chain, where credential acceptance, issuer policy and evidence quality matter as much as the user experience.
• Qualified Electronic Signature: A higher-assurance signature backed by certificate-based identity and trust service provider controls. It is used where legal recognition and stronger evidentiary value are required, especially in cross-border or regulated workflows where the identity chain must remain defensible.
• Remote Identity Proofing: Remote identity proofing is the process of verifying that a person is who they claim to be without meeting in person. It combines document checks, biometric comparison, device and signal analysis, and fraud screening to establish confidence in identity remotely. It is used before account creation, recovery, or high-risk access.
• Evidence Chain: An evidence chain is the connected sequence of records that proves an identity action was requested, approved, executed, and reconciled. Without that continuity, access governance becomes fragmented and auditors are left to infer intent from incomplete system data.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, workload identity and secrets management in the context of modern trust architecture. It helps identity and security practitioners connect governance decisions to durable operating models.