The training provider confirms the result
Kauri Trades Academy checks its own records: Mere completed the course and passed the assessment.
It issues the credential
Staff choose the credential type, confirm the details and send Mere an offer. It carries an expiry date and can be withdrawn later.
Mere receives and holds it
She opens the offer on her phone. The credential and its keys stay on her device — DiligenceID holds no copy.
She shares it with an employer
A contractor asks for proof of the qualification. Mere sees who is asking and what they want, and approves just that.
The employer gets a checked answer
The check confirms the academy issued it, that it is Mere's, that it is in date and that it has not been withdrawn.
Digital credentials
Digital credentials people can hold and organisations can check.
Issue a digital record of something your organisation can confirm. The person keeps it on their phone. When someone else needs proof, they check it in seconds.
Three parties, three jobs. DiligenceID runs the issuing and the checking, built on open protocols.
The issuer
An organisation that can vouch for something — a training provider, an employer, a regulator — creates the credential and keeps control of its status.
The holder
The person it is about. They keep the credential in a wallet on their own device and choose when to share it.
The checker
Any organisation that needs proof. It asks for the specific facts it needs and gets a result it can act on.
What would you like to do?
Start with the job in front of you. Each page covers the experience, what you need, and how to get going.
I want to issue credentials
Give people a digital record of a qualification, a licence, a role or an entitlement your organisation can confirm.
See how issuing worksI want to check a credential
Ask someone to prove something and get a checked answer in seconds, instead of collecting copies of documents.
See how checking worksI want to use a wallet
Receive a credential on your phone, see exactly who is asking for what, and decide each time whether to share it.
See the walletExample: professional qualifications
A qualification, from the course to the next employer.
One credential followed the whole way, using a fictional training provider.
A check confirms the credential is genuine, unchanged, current and held by the person presenting it. Confirming the underlying facts stays with the issuing organisation — which is why choosing the issuers you accept is the decision that carries the weight.
Questions people ask early
What happens when something changes?
An issuer sets an expiry date and can withdraw a credential at any time. The next check reads current status, so the change takes effect immediately.
Can we ask for less?
Yes. A request can ask for specific facts — that a licence is current, say — without a date of birth or an address coming across with it.
Will it fit what we already run?
DiligenceID handles issuing and checking. Your systems, accounts and decisions stay yours. Explore integration options.
Does it work with Microsoft?
DiligenceID can administer Microsoft Entra Verified ID alongside its own credentials, from one interface. How that works.
Trust
Built on open standards, designed for privacy.
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 implementing the same profile.
Credentials and the private keys that bind them to a person stay on that person's own device. DiligenceID keeps the issuance and verification records issuers and checkers need, and no copies of issued credentials.
See it against your own use case
Tell us what you need people to prove and who needs to check it, and we will walk you through it.