Set up a verifier
A verifier runs checks on the documents people show you from their wallets. You manage verifiers under Setup → Verifiers.
Create a verifier
- Open Setup → Verifiers and select Create verifier.
- Give it a name your team and customers will recognize.
- On the new verifier, select Add check to choose what it checks.
Owners and admins create and change verifiers. Members can open them and read their settings.
The tabs
| Tab | What it holds |
|---|---|
| Overview | Requests started this week, the checks it runs, recent activity and a link to its records |
| Checks | The checks this verifier runs. Add, run or remove them here |
| Registration | Sandbox registration and what Production still needs |
| Result delivery | The HTTPS endpoint where results go. Intermediary mode only, owners and admins. Required: checks can't send results until it is set |
| Settings | Name, description, verifier ID, and Archive verifier |
Add checks
A verifier with no checks can't run. On the Checks tab, select Add check and pick one:
- Your checks: a check your organization already has, perhaps on another verifier.
- From the catalogue: a ready-made check from LutraID. It is also added to your checks on Setup → Checks.
Checks are shared. A check used by several verifiers has one set of details, so a later change affects all of them. See Checks.
In Sandbox, LutraID prepares the test certificate when you add a check, so you can run it right away. In Production, a new check needs registration before it can run.
Remove from this verifier stops the verifier running the check. The check stays in your checks and on other verifiers, and its records stay available.
Issuer trust
Which issuers a check accepts is set on the check, not on the verifier. Open Setup → Checks, then Configure issuer trust on the check:
- Only issuers on trusted lists: accepts documents only from issuers on the lists you pick. Use this in Production.
- Any issuer (testing only): accepts a document from any issuer whose signature is valid.
The change applies to every verifier that uses the check.
Production setup reports a check that accepts any issuer but doesn't block it yet, so such a check can still run in Production. A check set to Only issuers on trusted lists does reject documents from other issuers. Set it for Production; it is a step on Production setup.
Registration
In Sandbox, the Registration tab shows Sandbox registration: how many checks are ready to test and the test access certificate. If a check shows Action needed, select Refresh Sandbox registration.
For Production, the same tab collects the purpose of each check, your privacy policy and the registration certificates from the Registrar. Production setup walks through every step.
API keys
Keys for your systems are under Developers → API keys, one set per environment. See API keys.