Verifier Identification (Verifier ID).
Verifier identification is how a digital wallet receives structured, verified information about the website or service requesting a credential, so the user can see who is asking before approving the share.
Passkeys solved phishing for login by binding each credential to an origin. Wallet credentials do not have that property. A mobile driver's licence or a verifiable credential is meant to be shown to many verifiers, so the question "who is asking for this?" has to be answered at request time. FIDO's announcement names that gap directly: wallets prove the user well but lack scalable ways to validate the verifier.
The Verifier ID framework is FIDO's answer: structured, verified information about the requesting site or service, delivered to the digital identity wallet so it can show the user an accurate requester before they approve. It is the wallet-side counterpart of verifier impersonation resistance in authenticators.
Our reading. For a CIAM team acting as a verifier, expect to register and prove your identity to wallets, much as you register an RP ID or an OAuth client today. FIDO had not published the framework when this entry was written, so the registration and trust-list mechanics are not yet known. Read it alongside the Credential Manager Reference Architecture, and see decentralized identity for CIAM for where wallets fit in a CIAM stack.
Common questions
What is verifier identification?
It is the process by which a digital wallet obtains verified information about the site or service requesting a credential, such as a mobile driver's licence attribute, and shows it to the user. The user then decides whether to share, knowing who is asking.
What did the FIDO Alliance announce about Verifier ID?
On October 20, 2026, at Authenticate 2026, FIDO announced a Framework for Verifier Identification as one of the working documents from its digital wallet certification work. FIDO said it would publish the documents in the coming weeks. It did not publish technical details with the announcement.
How is verifier identification different from passkey origin binding?
A passkey is scoped to the relying party ID, so the browser simply refuses to use it on another origin. A wallet credential can be requested by many verifiers, so the wallet needs a separate way to know and display who the verifier is. Verifier identification fills that gap; it is a trust display and check, not a cryptographic scope on the credential.
Related terms
In the guides
Decentralized Identity and Verifiable Credentials: What CIAM Teams Should Know
EUDI Wallet rolls out in 2026. US mDL adoption is uneven but real. DID and VC are no longer research projects. The CIAM-side impact, and when to start integrating.
Identity Verification and Proofing (IDV/KYC): A CIAM Guide for 2026
How to prove a real person matches a claimed identity at signup: document capture, liveness, authoritative-data checks. The 2026 stack, the deepfake escalation, and where CIAM ends.