How it works
DiligenceID connects authoritative issuers, holders, wallet experiences, verifiers and relying services across the full lifecycle.
Three-party model
A clear credential architecture starts with authority and policy, not a QR code.
Service lifecycle
The exact platform and format vary by use case, but ownership must cover every stage.
Platform operations
An issuer is not ready merely because it exists. DiligenceID exposes lifecycle, signing, trust and protocol state so operators can resolve gaps before a holder journey begins.
Policy before technology
Identify the authoritative organisation, source information and operational owner for issuance and lifecycle changes. Day to day, this is an HR system, a licensing authority or a training provider signing off evidence it is genuinely positioned to attest.
Make the requesting party, purpose, evidence and next step visible before presentation. The holder decides whether to present a credential from their wallet for a given request—nothing is pushed or shared automatically.
Define trusted issuers, credential types, required claims, status rules and the relying service’s decision. A verifier checks the issuer's signature, the credential's current status and the specific claims requested—not the whole record.
Diligence Wallet
The Diligence Wallet is a holder experience for receiving, holding and presenting supported DiligenceID credentials.
It is separate from issuer administration. It is also distinct from Microsoft Authenticator; Microsoft Entra Verified ID scenarios must use wallet experiences supported by Microsoft’s current product configuration.
Standards and interoperability
The selected credential, wallet and trust ecosystem determines the exact profile; support should be confirmed for each deployment rather than assumed from a standards label.
A standards-based way to express issuer-provided claims and proofs for portable digital evidence.
An OpenID-family protocol for credential issuance journeys where supported by the selected ecosystem.
A protocol for requesting and returning verifiable presentations between holder and verifier components.
A credential format that can support selective disclosure patterns when all participating components implement the required profile.
DIDs may identify and resolve issuer authority in profiles that use them; they are not required to replace every existing identity identifier.
Separate business trust policy from one wallet, format or vendor-specific interface where practical.
Lifecycle controls
Verification should evaluate supported status information as part of the relying service’s policy.
Credential validity and renewal should reflect the underlying fact, relationship or authority.
A designed revocation process lets the authoritative issuer respond when eligibility, accuracy or security changes.
Issuance, status and verification events support troubleshooting, assurance and accountable service operation.
Put trusted evidence to work
Start with the authoritative evidence, holder experience and relying decision—then select the right credential and integration pattern.
