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.
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.
Verify Credentials
Ask questions of credentials through declarative policies. Verify age, licensing, and identity with zero PII retention.
Explore Verification →IssuersIssue Credentials
Design credential configurations, configure signing keys, and issue SD-JWT VCs directly to user wallets.
Design Credentials →DevelopersIntegrate Applications
Step-by-step integration guides for .NET, TypeScript, Python, Go, PHP, iOS, Android, and WordPress/WooCommerce.
View Guides →Mobile & WalletExplore the Wallet
Hardware key binding (Secure Enclave/StrongBox), OpenID4VCI, OpenID4VP, non-custodial index, and consent controls.
Wallet Architecture →ArchitectsPlatform Building Blocks
Deconstruct the 18 platform building blocks, DISTF alignment, Zero Trust boundaries, and privacy patterns.
View Building Blocks →API ContractsAPI Explorer & Reference
Test requests interactively with the API Explorer, inspect OpenAPI specs, and review response envelopes.
Launch API Explorer →How DiligenceID works
Resources are configured on the Management plane, then issued, held, presented, and verified across standard protocols.
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.
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
.NET SDK Quickstart
Issue and verify credentials in ASP.NET Core & C#
TypeScript SDK Quickstart
Node.js, Next.js, and browser integration
Integration Wizard
Interactive code generator for your exact stack
Credential Studio
Visual schema designer and SD-JWT VC builder
Mobile Deep Links
Universal links, QR codes, and app hand-offs
Sign in with DiligenceID
Credential-based login vs federated SSO