Website →

SpruceID Blog

Thoughtful perspectives on identity, interoperability, and the systems that turn public policy into usable services.

Cross-Jurisdictional Digital Identity: Why Credentials Issued in One State Need to Be Accepted in Another
Interoperability

Cross-Jurisdictional Digital Identity: Why Credentials Issued in One State Need to Be Accepted in Another

Credentials issued in one state increasingly need to be accepted in another. That requires agreement on trust frameworks, credential formats, and governance, not just technical standards.
What Makes a Digital Identity Framework Trustworthy?
Digital Identity

What Makes a Digital Identity Framework Trustworthy?

As more states consider digital identity legislation, the question is not whether to build the infrastructure but what makes a framework trustworthy enough to deserve public confidence.
HR1 Verification Readiness Checklist for State Medicaid Agencies
Document Intake

HR1 Verification Readiness Checklist for State Medicaid Agencies

Before selecting technology for HR1 verification, states should understand what they can already verify ex parte, where evidence gaps exist, and what capabilities are needed to resolve them.
5 Questions Banks Should Ask Before Accepting Digital Credentials
Digital Identity

5 Questions Banks Should Ask Before Accepting Digital Credentials

The FinCEN ruling opens the door to digital credential acceptance, but banks need answers to five infrastructure questions before they walk through it.
How VDC Acceptance Changes Bank Account Opening
Document Intake

How VDC Acceptance Changes Bank Account Opening

The FinCEN ruling allows banks to accept digital credentials across in-person, remote, and digital channels. Here is what the account opening process looks like in each.
Why Wallet Choice and Interoperability Matter in SEDI
Interoperability

Why Wallet Choice and Interoperability Matter in SEDI

Meaningful wallet choice requires more than publishing an open standard. Credentials, wallets, and verifiers must work across organizational and vendor boundaries through governance and conformance, not just specifications.
What Is ISO/IEC 18013-5, and How Does the mDL Standard Actually Work?
Interoperability

What Is ISO/IEC 18013-5, and How Does the mDL Standard Actually Work?

ISO/IEC 18013-5 is the technical foundation that allows a mobile driver’s license issued in one state to be trusted in another.
Accepting a Credential Is Not the Same as Verifying It
Zero Trust

Accepting a Credential Is Not the Same as Verifying It

Reading data fields from a digital credential is not verification. Without cryptographic validation of the issuer's signature, revocation status, and device binding, a digital credential offers less assurance than a physical ID.
What Would It Actually Take for a State to Implement SEDI?
Digital Identity

What Would It Actually Take for a State to Implement SEDI?

Adopting SEDI-style legislation is only the beginning. States need governance, trust infrastructure, credential issuance, wallet interoperability, conformance processes, and a deployment strategy across agencies.
How Intelligent Document Processing Is Changing Government Intake
Document Intake

How Intelligent Document Processing Is Changing Government Intake

Intelligent document processing can dramatically reduce manual review time for government agencies. But extracting data from documents is not the same as verifying it. The trust problem requires a different solution.
What Does a Bank Need From a State to Verify Its mDL?
Interoperability

What Does a Bank Need From a State to Verify Its mDL?

When a bank receives a mobile driver's license from another state, it needs to verify the issuer's signature. That requires trust infrastructure most banks don't have yet.
Digital Identity Without Surveillance: Understanding SEDI's No-Phone-Home Principle
Zero Trust

Digital Identity Without Surveillance: Understanding SEDI's No-Phone-Home Principle

Utah's SEDI statute prohibits architectures where the issuer can observe every credential presentation. Enforcing that requirement means choosing verification designs where the data is never generated in the first place.