Standards-Based Digital Credentials

Build privacy-preserving credential experiences with DiligenceID

Issue, verify, and govern digital credentials with standards-first protocols. Built on OpenID4VCI, OpenID4VP, and SD-JWT VC, DiligenceID replaces document copying and centralized data collection with minimal verified assertions.

Core Architecture Invariant

Credentials remain with the holder

“Credentials remain with the holder. Applications ask questions of credentials through explicit verification policies. DiligenceID returns the minimum verified assertion required to make the application’s decision. Persistent identity data is the exception, not the default.”

Choose your path

Task-oriented starting points tailored to your role and integration goals.

How DiligenceID works

Resources are configured on the Management plane, then issued, held, presented, and verified across standard protocols.

1ConfigureManagement2IssueOpenID4VCI3HoldWallet Hardware4PresentOpenID4VP5VerifyPolicy Engine6DecideMinimal Assertion

Read the complete credential lifecycle, or how the two API planes divide administrative and transactional work.

Platform Building Blocks

Eighteen decoupled components designed for Zero Trust and DISTF accreditation.

View all 18 building blocks →

Issuer

Issues cryptographic credentials bound to holder hardware keys.

Verifier

Requests minimal verified assertions through explicit policies.

Holder & Wallet

Possesses credentials in non-custodial hardware-backed storage.

Verification Policy

Declarative question and evidence rules evaluated fail-closed.

Status List

Compressed cryptographic bitstring for real-time revocation.

Trust Register

Decentralized registry of accredited ecosystem participants.

Popular SDKs & developer tools

Common tasks