Skip to main content

Issuing Credentials

This guide covers the step-by-step process for issuing any credential type in DPP Kit.

Step-by-Step​

1. Navigate to the Issue Page​

Go to Toolkit > Credentials > Issue or click "Issue a Credential" from the dashboard.

2. Select Credential Type​

Choose from the available types. Each type is shown as a selectable card with a brief description:

  • DFR — Digital Facility Record (Admin only)
  • DPP — Digital Product Passport
  • DTE — Digital Traceability Event (coming soon)
  • DCC — Digital Conformity Credential (coming soon)
  • DIA — Digital Identity Anchor (coming soon)

Disabled types show a "coming soon" label. Types restricted by your access level are noted.

3. Fill in Details​

Each credential type has its own form fields. Required fields are marked with a red asterisk.

4. Review​

Before issuing, review all fields. Once issued, credentials cannot be edited — the cryptographic signature locks the content.

5. Issue​

Click Issue Credential. DPP Kit runs the full pipeline:

  1. Runs UNTP Tier 2 schema validation (checks VCDM v2 context, UNTP schema, and VCDM schema)
  2. Creates a revocation status entry
  3. Signs with your organization's DID
  4. Uploads to storage
  5. Registers in the Identity Resolver

If schema validation fails in step 1, the credential is set to error status with details about what went wrong. You can edit the draft and re-attempt issuance.

You'll see a success message with a link to view the issued credential.

Draft Behavior​

When you start filling in a credential form, a draft is saved automatically. Drafts:

  • Can be edited freely
  • Can be deleted without consequence
  • Appear in your credential list with a "draft" status badge
  • Are not signed or published

Error Recovery​

If issuance fails partway through the pipeline:

  • The credential status is set to error
  • You can view the error details
  • Edit the credential to fix the issue and re-attempt issuance
  • The pipeline compensates by cleaning up any partial artifacts (e.g., deleting from storage if resolver registration fails)

Tips​

tip
  • Run Tier 2 Tests before issuing — Click "Run Tier 2 Tests" in the editor to catch schema errors before committing to issuance
  • Issue DFRs before DPPs — Facility records need to exist before you can link products to them
  • Use pilot mode for iteration — Re-issue freely in pilot mode until you're happy with the content
  • Check the credential after issuance — Click "View" to see the signed credential and verify it renders correctly