Credential types, how a credential is issued, what it contains and how to verify it.
A credential is your organization’s on-chain answer to “is this licensed?” or “has this been disclosed?”. You define credential types, link each to a form, and the Compliance Hub issues a credential when an application is approved or a filing is submitted. Anyone can then check the credential against the on-chain registry.
Application forms issue the credential when the last approver approves. The confirmation reads This action will approve the application and issue the credential.
Filing forms issue the credential when the issuer submits. No approval is needed.
Issuance runs in the background, so the credential can appear a short time after the decision.
Application forms issue a licence-kind attestation. Filing forms issue a disclosure-kind attestation.
Click Credentials in the sidebar. The list shows each type, its description and status. Click a type’s menu (2) to edit it.
Your organization's credential types
2
Create a credential type
Click New Credential (1). Enter a Credential title (1) and a Description (2). Click Register credential (3). The type is published to the Credential Registry and becomes available for issuance.
Create credential type
3
Find the registry ID
Open an existing type to edit it. Compliance Engine Credential ID (1) shows its registry identifier. Click Copy (2) to copy it.
Signature metadata when present. null in the KYI payload.
The Compliance Hub also keeps a record for each issued credential: its type, issuer, asset, application, jurisdiction, status, issue and expiry dates, and the IPFS content ID of the stored payload.
You register a credential type Example Licence. You create an Application form for Issuer recipients that uses it. An issuer applies, and your two approvers approve. The issuance job writes the credential on-chain, and it appears on the Watchlist Credentials tab as Active. An exchange checks the issuer’s status with KYI before listing their token.