Preview release. These docs are a work in progress. Pages are still being written, links may break, and structure may shift without notice. Treat everything here as a draft and report issues on GitHub.
Verify a status fact about a registered entity without sharing the full record
Use this pattern when a relying party needs to confirm one narrow status fact about a registered entity (active, suspended, dissolved, registration class), and the existing API returns the full record alongside the answer. The worked example below uses a national business registry; the same shape fits any registry that publishes a status-coded record about a registered entity.
Starting situation
Section titled “Starting situation”A national business registry records company incorporations, legal-status changes, and gazette references in a relational database. A public procurement platform must confirm that a supplier is actively registered before it processes a tender submission. The procurement platform needs a yes/no answer tied to the national business number. It does not need the company’s beneficial-ownership chain, registered address, or filing history.
What you set up
Section titled “What you set up”Configure a Registry Notary claim for the active-status fact. The claim definition names the source binding (the business registry table or extract), the rule (registration status equals “active”), the disclosure mode (predicate: true/false), and the issuer identifier.
Configure Registry Relay to expose the consultation route that accepts a national business number or LEI and routes the request to Notary for evaluation. Use Registry Manifest to publish BRegDCAT-AP-shaped catalog metadata for the business registry, including a link to the evidence offering document that describes the active-status claim.
What a caller does
Section titled “What a caller does”The procurement platform sends an authorized POST to the Notary evaluation endpoint, passing the national business number as the subject identifier and naming the active-status claim. The platform authenticates with the configured identity provider.
For a credential issuance flow, the supplier (or an agent acting on their behalf) receives an SD-JWT VC from Notary. The supplier presents only the active-status disclosure to the procurement platform, keeping unselected credential fields hidden.
What the caller gets back
Section titled “What the caller gets back”A signed evaluation containing: the national business number, the predicate result (active: true or false), the evaluation timestamp, and the issuer identifier.
The full company record, beneficial-ownership chain, gazette reference list, registered address, and internal registry notes do not appear in the response.
For a dissolved or suspended company, the predicate returns false. The specific legal-status code (suspended, dissolved, struck off) can be included as a separate configured disclosure if the governing policy permits it.
Related patterns
Section titled “Related patterns”The same Notary predicate pattern fits an eligibility or entitlement check against a different registry; see Verify an eligibility or entitlement fact without sharing the full record for a social-protection worked example.