Checks
A check is the question you put to a wallet: which documents you accept, which information you need from them, and which issuers you trust.
What a check decides
| Information asked for | The attributes the wallet must share, such as a birth date or an over-18 answer |
| Accepted documents | Which document types satisfy the check, in which formats |
| Issuer trust | Only issuers on trusted lists, or any issuer (testing only) |
| Purpose | Why you ask. Wallets show it to the customer before they share anything |
Ask for the minimum. A check that requests a birth date where an over-18 answer would do is one your customers are entitled to refuse.
Add a check
Owners and admins manage checks under Setup → Checks. Select Add from catalogue and choose a ready-made check from the LutraID catalogue.
If the catalogue has nothing that fits, tell us what you need to establish and we will add the narrowest check that answers it.
Change a check
Open the actions menu on a check:
- Edit details: the name and description your team sees.
- Edit attributes: the information the check asks for.
- Configure issuer trust: choose Only issuers on trusted lists and pick the lists, or Any issuer (testing only). Then select Save issuer trust.
Changes apply to future check requests. Requests already started keep their original question.
The purpose comes from the check's template and is read-only. To change it, use Ask support to change it on the check.
Checks are shared. Saving changes this check for every verifier that uses it. In Production, changing the information a check asks for can mean you need a new registration certificate from the Registrar.
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. Use it for Production.
Give a check to a verifier
A check runs only through a verifier. Open the verifier under Setup → Verifiers, go to its Checks tab and select Add check. Choose from Your checks or From the catalogue.
- Sandbox: adding a check prepares its test certificate, so you can run it right away.
- Production: a new check needs registration before it can run. See Production setup.
Archive a check
Archive check hides a check you no longer use. A check that is still on a verifier can't be archived: remove it from those verifiers first. Archived checks stay in records but can't be added to a verifier or run. Restore check brings one back.
For developers
Each check has a Check ID, shown on its details page. This is the verificationProfileId you pass when you start a check over the API. See Verify a credential.