Product tour

See how it works.

A walkthrough of the three experiences — issuing, holding and checking — using real product screens. Select any image to enlarge it.

Shown with sample organisations, people and credentials.

Book a demo Start with issuing

For the organisation issuing

Designing and issuing a credential

A credential type is designed once, then issued to people as often as you need.

A credential type being designed, showing the facts it will carry and the format it will be issued in — Designing the credential type: which facts it carries and how it appears to the person holding it.

Issuing a credential to one person, showing the issuer, the credential type and the details being entered for that person — Issuing to one person. The result is an offer — a link or QR code — that they accept in their wallet.

A table of credentials that have been issued, showing when each was issued, its current status and a control to withdraw it — What has been issued and its current status. Withdrawing a credential here takes effect on the next check.

For the person holding

Receiving, holding and sharing

The wallet sits on the person’s own device, and so do the credential and the key that proves it is theirs.

Credentials held in a wallet on a phone, each card naming the organisation that issued it and showing that it is currently valid — Credentials the person holds, each naming the organisation that issued it.

A request on a phone showing which organisation is asking, why, which facts are required and which are optional, with buttons to share or decline — A request arrives: who is asking, what for, which facts are required, and the option to decline.

A history on a phone of credentials received and shared, including requests the person declined — A record of what has been shared and with whom.

For the organisation checking

Asking for proof and reading the result

A check is defined once as a reusable request, then run whenever the decision comes up.

Setting up a check, showing the facts being asked for, the issuers that will be accepted and what happens when a check cannot be completed — Defining what a check asks for, and which issuers you accept it from.

An activity record listing who performed each action, what it affected and how it turned out, including a request the holder declined — The record of issuance and checking activity, showing who did what and how it turned out.

What a demo adds

These screens show the product. A demo shows it against your situation.

Your own credential

What a credential would carry for your organisation, how long it should last, and who would accept it. That is the part worth an hour of conversation.

A live exchange

We run issuance and checking end to end, so you see a credential arrive on a phone and a check come back.

Your integration

How this lands in your architecture, covered on the integration options page and in more depth with an engineer.

A sandbox

An isolated environment for your team to build against, set up as part of an evaluation.

Seen enough to have a question?

Tell us what you need people to prove, and we will walk through it against your own use case.

Book a demo Read the credential journey