4 min read

How Agencies Evaluate Digital Identity Vendors: 5 Questions to Ask

Five questions state agencies should ask when evaluating digital identity vendors, focused on open standards, interoperability, and long-term vendor independence.

How Agencies Evaluate Digital Identity Vendors: 5 Questions to Ask

Selecting a digital identity vendor is one of the most consequential infrastructure decisions a state agency can make. The technology will shape how residents prove who they are, how agencies verify that proof, and how easily the state can adapt as standards evolve and requirements change. A procurement decision made today may define the state's identity architecture for a decade.

The challenge is that every vendor in this space claims to support open standards, protect privacy, and enable interoperability. Those claims are not equally substantive. The following five questions help procurement teams distinguish genuine capability from marketing language and evaluate whether a solution will serve the state's interests over the full lifecycle of the investment.

1. Which Open Standards Does the Solution Support?

This is the most foundational question, and the most frequently answered in vague terms. "Standards-based" can mean anything from full conformance to a published specification to loose alignment with a set of principles.

Ask vendors to name the specific standards their solution implements: ISO/IEC 18013-5 for mobile driver's licenses, the W3C Verifiable Credentials Data Model v2.0 for credential structure, OpenID for Verifiable Presentations (OID4VP) for credential exchange, and NIST SP 800-63-4 for identity assurance levels. Ask which version of each standard is supported, and whether the implementation has been tested against other vendors' implementations in interoperability events.

A vendor that cannot name the specific standards and versions it supports, or that describes its approach as "aligned with" rather than "conformant to" a specification, may be offering a proprietary implementation with a standards-adjacent label. That distinction matters when other systems need to interact with the state's credentials.

2. Can It Handle Multiple Credential Formats?

The digital identity ecosystem does not run on a single credential format. Mobile driver's licenses use the mdoc format (defined in ISO/IEC 23220-4, with the mDL-specific application in ISO 18013-5). Many government and enterprise credentials use the W3C Verifiable Credentials model, often with SD-JWT (Selective Disclosure JSON Web Token) for privacy-preserving presentation. Some jurisdictions are adopting both formats simultaneously because in-person verification and online verification may rely on different formats and protocols.

A solution locked to a single format limits the state's ability to participate in cross-jurisdictional verification and serve emerging use cases. Ask vendors whether the solution can issue and verify in multiple formats, and whether adding a new format requires a platform upgrade or an architectural change.

Interoperability without lock-in depends on format flexibility, not just protocol compliance.

3. Does It Work Offline?

Many government identity use cases do not have guaranteed network connectivity at the point of verification. A state trooper verifying a mobile driver's license at a traffic stop, a poll worker checking a voter's identity, or a field inspector verifying a professional license may be operating in areas with limited or no cellular coverage.

ISO 18013-5 specifies a proximity-based verification protocol that works over Bluetooth Low Energy and NFC without requiring a network connection at the moment of presentation. Ask whether the vendor's solution supports this offline verification model, or whether it requires a network call to a central server for every verification event.

A solution that depends on real-time network connectivity for basic verification introduces a single point of failure that can affect the most critical use cases, often in the environments where reliable connectivity is least available.

4. How Is Data Minimized During Verification?

Privacy-preserving verification is a design requirement, not a feature add-on. When a resident presents a credential to prove their age, the verifier should learn that the resident is over the required age. The verifier should not need to see the resident's full name, address, date of birth, and license number.

Selective disclosure makes this possible at the technical level. The SD-JWT format, for example, allows a credential holder to reveal only specific claims from a credential while keeping others cryptographically hidden. The verifier can confirm that the disclosed claims are authentic and were issued by a trusted authority, without seeing the rest of the credential's contents.

Ask vendors how their solution implements data minimization. Can the holder choose which attributes to share for each verification event? Does the system support age-over proofs without revealing the date of birth? Can the verifier request only the attributes needed for the specific transaction? If the vendor's answer involves sharing the full credential and filtering on the verifier side, that is not selective disclosure; it is data collection with display restrictions.

5. What Happens If We Switch Vendors?

This may be the most important long-term question, and the one vendors are least eager to answer directly. If the state decides to change technology providers in three or five years, what happens to the credentials already in residents' hands? Can those credentials be verified by a new system? Can the state's trust infrastructure, including issuer keys, revocation lists, and trust registries, be migrated to a different platform?

A solution built on open standards with documented, non-proprietary interfaces is inherently more portable than one built on a proprietary stack with a standards-compatible API layer. Ask whether credentials issued by the vendor's system can be verified by any conformant verifier, or whether verification requires the vendor's own infrastructure. Ask whether issuer key material and revocation data are stored in standard formats that another provider could ingest.

Vendor lock-in in digital identity is particularly costly because the switching cost is not just technical. It potentially involves re-issuing credentials to every resident who holds one. Open standards reduce this risk by ensuring that the credential itself is vendor-independent, even if the platform that issued it is not.

Putting the Questions Into Practice

These five questions are not designed to favor one vendor over another. They are designed to ensure that the state's identity infrastructure supports interoperability across jurisdictions, preserves resident privacy through architectural design, works in the real conditions where verification happens, and protects the state's investment against future technology transitions. The answers should be specific, testable, and verifiable through interoperability demonstrations rather than slide decks.

Building digital services that scale take the right foundation.
Talk to our team

About SpruceID: SpruceID builds digital trust infrastructure for government. We help states and cities modernize identity, security, and service delivery — from digital wallets and SSO to fraud prevention and workflow optimization. Our standards-based technology and public-sector expertise ensure every project advances a more secure, interoperable, and citizen-centric digital future.