Skip to main content
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.

Key concepts

How a credential is issued

  • 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.

Manage credential types

1

Open Credentials

Click Credentials in the sidebar. The list shows each type, its description and status. Click a type’s menu (2) to edit it.
Credentials page listing Know Your Issuer and Proof of Collateral as Active, with callouts on New Credential and the first row

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 dialog filled with an example licence, with callouts on Credential title, Description and Register credential

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.
Edit credential type dialog for Know Your Issuer with the registry ID redacted, and callouts on Compliance Engine Credential ID and Copy

Edit credential type

What a credential contains

Bluprynt credentials follow the W3C Verifiable Credentials data model. A KYI credential has this shape:
KYI credential (example values)
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.

Verify a credential

1

Check it in the Watchlist

Open Watchlist, then the Credentials tab (1). Each row shows the credential, its asset, jurisdiction, status, and issue and expiry dates.
Watchlist Credentials tab with columns Credential, Asset, Jurisdiction, Status, Issued On and Expires On, and a callout on the tab

Credentials on the Watchlist

2

Check the status

Trust a credential only when its status is Active and it hasn’t expired.
3

Check it outside the Compliance Hub

KYI credentials are public. Look one up with KYI or the Public API.

Reference

Credential statuses

Supported networks

The attestation service supports KYI verification on Solana, Ethereum and Plume.

Worked example

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.

Errors and troubleshooting

FAQ

A credential is a kind of attestation: one your organization issues about a regulated status, such as a licence.
The type and issued credential are written to the on-chain registry. Your forms and answers stay in your organization.