Digital credential infrastructure · Aotearoa New Zealand
DiligenceID gives organisations the infrastructure to issue, verify and govern digital credentials through APIs, wallets and existing identity systems.
Prove identity, relationships and organisational authority without rebuilding the same evidence checks inside every service.
For issuers, verifiers and organisations that rely on trusted evidence. Get started opens the separate DiligenceID platform application.
Why change
People repeatedly upload and re-enter evidence. Organisations repeatedly collect, check, retain and reconcile it across disconnected systems.
DiligenceID is not a universal central identity database. Credential content stays in the holder's wallet or the issuing organisation's own environment; DiligenceID governs the issuance, verification and status of that evidence rather than aggregating it into one central store.
The product
DiligenceID connects issuers, holders, wallets, verifiers and business systems across the complete credential lifecycle.
Support approved issuers, credential definitions and controlled issuance from trusted source information.
Give people a supported wallet journey to receive and present the evidence requested for a clear purpose.
Validate issuer, integrity, claims and status, then pass the result into the relying service’s own policy. Checking a cryptographic signature and current status is faster than manual document inspection and back-and-forth requests for further proof.
Operational proof
DiligenceID separates lifecycle, signing, trust and protocol readiness so an operator can see whether an issuer is prepared for a credential journey.
Product surfaces
Platform operations, holder experience, enterprise integrations and trust governance remain distinct while working as one journey.
Credential lifecycle
A trustworthy credential service needs ownership from initial policy through status, expiry, revocation and operational evidence.
What can be proven
A credential can represent a trusted fact, relationship or authority—not merely a digital copy of an identity document.
Credential content and assurance must be defined by an authoritative issuer and accepted by a relying service for a specific purpose.
A transparent exchange
The holder sees who is asking, what evidence is required and why before choosing whether to present it.
Organisational identity
A sign-in can identify an account. DiligenceID can add evidence of the organisation represented, the current relationship, and the defined authority to act.
Organisation context
The platform keeps organisation context, issuer relationships and operational state visible before evidence is issued or relied upon.
Identity and evidence
Microsoft Entra ID, CIAM, MFA and Conditional Access establish accounts, sessions and access policy.
DiligenceID carries evidence from an authoritative issuer into an application, portal, API or business process.
Microsoft identity
DiligenceID can add journeys, trust policy, lifecycle, organisational authority and application integration around Microsoft’s managed verifiable credential capability.
Use cases
Carry evidence of employment, contractor status, role, training or permission across organisational boundaries.
Issue and verify qualifications, certifications and completed learning without relying on copied documents.
Present current evidence of a licence or professional standing at the moment it matters.
Request defined evidence before creating or linking an account, while retaining only what the process needs.
Diligence Wallet
Diligence Wallet is the holder experience within the DiligenceID ecosystem. It gives people a way to receive, review and present supported credentials.
It is distinct from DiligenceID administration and issuer systems, and it is not Microsoft Authenticator. Where a use case relies on Microsoft Entra Verified ID, the selected Microsoft-supported wallet journey and current product requirements must be confirmed.
Privacy by design
Privacy depends on the complete journey: what is requested, what the holder sees, what is presented and what the relying organisation retains.
Design requests around the claims required for the decision rather than collecting an entire record.
Make the verifier, purpose and requested evidence clear before the holder presents it.
Use selective disclosure where the selected format and platform support it.
Keep operational evidence of the trust decision without retaining unnecessary credential content.
API-first integration
DiligenceID is not only an administration portal. APIs and webhook events connect issuance, verification and status to existing applications and authoritative systems.
Connect credential issuance to authoritative source systems and existing workflows.
Start presentation journeys from an application and receive a verified outcome.
Use webhook events to coordinate asynchronous issuance and verification journeys.
Connect revocation and credential-state changes to business lifecycle events.
Embed the journey into existing portals and applications using thin integration layers.
Keep business policy separate from wallet, credential format and platform-specific concerns where practical.
Thin clients, SDKs and plugins are part of the integration direction; public availability and supported capabilities will be documented as they are released.
Why DiligenceID
Connect credential operations to existing products and business workflows. Issuance, verification and status changes are called from your own application rather than a separate portal.
Use supported open credential and presentation patterns to reduce lock-in. Data models and protocols such as W3C Verifiable Credentials keep evidence portable across issuers and wallets.
Represent relationships, roles and delegation—not identity alone. A credential can describe which organisation someone represents and what they are authorised to do, not just who they are.
Request proportionate evidence and define retention deliberately. Verifiers ask for the specific claims a decision needs, and DiligenceID does not require holding a copy of the underlying record.
Complement Microsoft Entra environments and Verified ID where selected. Sign-in and access stay with Entra ID; DiligenceID adds the evidence layer around it.
Built locally for organisations operating here, using global standards. Development and support are grounded in Aotearoa New Zealand privacy and regulatory expectations.
Built in Aotearoa
DiligenceID is developed by MAITS Limited in Wellington for organisations working through real identity, privacy and authority decisions in Aotearoa New Zealand.
The product builds on MAITS expertise across Microsoft identity, access governance and security architecture. It is intended to work with existing identity providers and evolving digital identity ecosystems—including public service, business, education, iwi and community contexts where the use case and trust model support it.
About MAITS LimitedFrequently asked questions
A digital credential is evidence issued by an authoritative source that a holder can present for verification. It can represent a fact, relationship or authority—not simply another account.
DiligenceID is credential infrastructure. It complements identity providers and access systems by carrying trusted evidence into the decisions made by applications and business processes.
No. Microsoft Entra ID continues to manage authentication, sessions and access. DiligenceID helps prove trusted facts or authority relevant to a transaction.
A person can hold a supported credential in a wallet such as Diligence Wallet. The exact wallet and holder journey depend on the selected credential ecosystem and implementation.
Yes. Credential designs can include expiry and issuer-managed status or revocation. Verifiers must evaluate the appropriate current status when making a decision.
Yes, where an authoritative issuer and relying policy support it. Evidence can describe which organisation a person represents, their relationship, and the scope or duration of delegated authority.
Put trusted evidence to work
Bring the use case, authoritative source and relying decision. Open the platform or talk with the DiligenceID team about an integration path.
