TL;DR: The article finds eIDAS 2.0, AMLR and PSR/PSD3 converging into one trust chain, with Namirial saying wallet-agnostic operating models and QES-enabled self-ident become the practical default. Identity journeys need one defensible evidence model across wallets, credentials and fallback paths.
Editorial analysis by NHI Mgmt Group, based on content published by Namirial: “The boardroom guide to digital trust in banking”.
Key questions
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.
Q: What breaks when fallback identity journeys are not tightly governed?
A: Fallback journeys often become the least defensible part of the programme.
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.
Practitioner guidance
- 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.
Bottom line: The article frames eIDAS 2.0, AMLR and PSR/PSD3 as one converging trust and evidence chain, not three separate compliance stacks.
Glossary terms: Electronic Identification Wallet, Qualified Electronic Signature, Remote Identity Proofing, Evidence Chain
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full 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.
A question worth separating out:
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.
👉 Read our full editorial: eIDAS 2.0 pushes wallet-agnostic onboarding and QES by default