What you can do

Issue digital credentials.

Give people a digital record of something your organisation can confirm — a qualification, a licence, a role, a membership, a clearance — that other organisations can check without ringing you up.

Where issuing helps

Example: education

Course and assessment results

A provider issues a qualification or micro-credential once, and the learner can show it to any employer afterwards.

Example: workforce

Roles, training and site clearances

An employer issues proof of an induction, a ticket or a current role, and withdraws it when someone leaves.

Example: membership and licensing

Current standing

A professional body issues proof that a person is currently registered, with an expiry that matches the registration period.

What the experience looks like

Issuing has two halves: setting up a credential type once, then issuing to people as often as you need.

  1. Design the credential

    Decide what the credential says — which facts it carries — and how it looks when someone sees it. This is a one-off setup per credential type.

  2. Issue it to a person

    Enter or send through the details for one person, and DiligenceID produces an offer: a link or a QR code you give to them.

  3. They accept it

    The person opens the offer in a supported wallet on their own device. The credential and its keys live there, not with us.

  4. You keep control of its status

    You can see what you have issued, and withdraw any credential. Checks made after that fail.

Issuing a credential to one person. Sample data throughout.

What you need to get started

Something you are genuinely authoritative for
A credential is only as good as the organisation behind it. Issue facts you already hold and already stand behind — not facts you would be guessing at.
A source of truth to issue from
A student record system, an HR system, a register. You can start by entering details by hand, then connect the system later through the API.
A decision about which provider to use

DiligenceID can issue its own credentials, where we manage the signing keys for you. It can also administer issuance through Microsoft Entra Verified ID, where you bring your own Microsoft tenant and Microsoft signs the credentials.

How the Microsoft option works

A way for people to hold it
Recipients need a wallet that supports the same credential format and protocol. What the wallet does.

Design decisions worth making early

You stay the authority

DiligenceID makes a credential tamper-evident and traceable to your organisation. Confirming the underlying facts remains your role, as it is today — which is exactly what makes the credential worth something.

Withdrawal takes effect on the next check

Withdrawing a credential means every check from that moment returns a failure. The copy on the person's device stays where it is; what changes is the answer any checker receives.

Expiry is a design decision

Set an expiry that matches the real-world fact. A permanent qualification and a twelve-month site clearance should not be issued the same way.

Status handling depends on the provider

Credentials DiligenceID issues use a published status list. Microsoft-issued credentials use Microsoft status handling. Both give you immediate withdrawal; plan for the one you choose.

DiligenceID issues through an issuer-initiated offer that the recipient accepts — the pre-authorised flow in OpenID4VCI 1.0. If your design assumes a browser redirect flow instead, raise it early and we will confirm fit.See the standards.

Have something you want people to be able to prove?

Bring the credential you have in mind. We will walk through what it would carry, who would check it, and whether this is the right tool.