Issue credentials people can reuse
You already hold facts about people — qualifications, registrations, roles — and other organisations keep asking you to confirm them. Issuing turns that into something they can check themselves.
Company
Partners.
Credentials work when both ends are in place: someone issuing, and someone accepting. We work closely with early partners on both sides to get a first exchange running.
Four ways in
Accept credentials instead of documents
You currently collect scans and check them by hand. Accepting credentials replaces that with a checked answer, for the issuers you choose to trust.
Build credentials into a product
You build software other organisations use, and credential issuing or checking would fit inside it. We will work through the interfaces and the boundaries with you.
Help organisations adopt it
You advise organisations on identity, onboarding or compliance, and want to bring credentials into that work. We will brief your team on the product and where it fits.
What we will ask you
Four questions in the first conversation. They get us to a useful answer quickly.
What needs to be proven?
The specific fact rather than the category — "a current gas fitting licence" rather than "identity".
Who can properly assert it?
Which organisation already knows it and stands behind it. That authority is what the credential carries.
Who is doing that checking today, and how?
The manual work happening now is what a credential replaces, and it is the clearest measure of what you gain.
What happens when it changes?
Expiry and withdrawal are where credentials pull ahead of documents, so how often the fact changes shapes the design.
DiligenceID is building its first credential ecosystem in New Zealand. Early partners work directly with the team that builds the product and help shape how it fits their sector.
Tell us the problem you can help solve
The most useful first message names the fact, the issuer and the decision that depends on it.