Trust
Built on open standards.
DiligenceID uses OpenID credential issuance and presentation protocols, with SD-JWT credentials supporting selective sharing of information. Credentials you issue are readable by any service that supports the same protocols.
The standards we apply
- OpenID4VCI 1.0Credential issuance
- Delivers a credential to a person. You create an offer, they accept it in their wallet, and the credential arrives on their device.
- OpenID4VP 1.0Credential presentation
- Requests proof. Your service shows a QR code or sends a link, the person approves in their wallet, and the result returns in the same session.
- SD-JWT — RFC 9901Selective sharing
- Lets a person share selected facts from a credential. Someone can prove a licence is current without their date of birth going across with it.
- SD-JWT VCCredential format
- The format every DiligenceID credential is issued in, so credentials are readable by any service that supports it.
- Token Status ListCredential status
- Publishes whether a credential is still valid. Every check reads it, so an issuer withdrawing a credential takes effect immediately.
Why it matters
Credentials that travel.
Using published protocols means a credential you issue can be checked by an organisation you have never dealt with, provided their service supports the same protocols. That is what turns a credential into something a person can reuse rather than a record locked inside one system.
Working with a particular wallet or provider? Tell us which one and we will confirm how it fits.
Assurance
For procurement and security reviewers.
- Implementation
- Each protocol is pinned to a published specification version and covered by an automated test suite. A conformance register setting out versions, supported flows and test coverage is available as part of an evaluation.
- Certification
- DiligenceID does not hold third-party conformance certification, and is not accredited under the New Zealand Digital Identity Services Trust Framework.
- Technical detail
- Supported flows, versions and integration boundaries are set out on the integration options page, which is written for architects.
Take it to your architecture
The integration overview covers responsibilities, interfaces and design decisions. For anything it does not answer, talk to the engineers who built it.