Skip to main content

Validating Credentials

DPP Kit lets you validate any UNTP credential — whether it was issued by your organization or someone else — against the official UNTP schemas and W3C Verifiable Credentials Data Model.

When to Validate​

  • Before issuing — Run Tier 2 Tests in the editor to catch schema errors in your draft
  • After receiving — Validate credentials from supply chain partners to check conformance
  • For auditing — Verify that previously issued credentials still pass current schema versions

Validate Page​

Go to Toolkit > Credentials > Validate to access the two validation methods.

Verify by URL​

Use this to validate a credential hosted at a known URL or IDR link.

  1. Paste the URL into the input field
  2. Click Verify Credential
  3. Review the step-by-step results

Supported URL types:

  • Direct storage URLs — Links to a credential JSON file (e.g., from the Storage Service)
  • IDR links — GS1 Digital Link resolver URLs (e.g., https://idr.example.com/api/1.0.0/gs1/01/04823171200019). DPP Kit automatically resolves the IDR linkset to find and fetch the credential.

URL verification runs both cryptographic verification (hard requirement) and schema validation.

Verify Credential File​

Use this to validate a downloaded credential file.

  1. Drag and drop a .json file onto the upload area, or click to browse
  2. Review the step-by-step results

File upload verification handles EnvelopedVerifiableCredential (JWT-wrapped) credentials automatically. Cryptographic verification is best-effort for file uploads — it shows as a warning if it fails, since your local system may not be able to resolve the issuer's DID.

Understanding Results​

Results are displayed as a series of validation steps, each with a status:

StatusMeaning
Passed (green)The check succeeded
Failed (red)The check found errors that must be fixed
Warning (yellow)The check found issues that don't prevent passing (e.g., extra fields, unresolvable DID)
Skipped (gray)The check was not applicable (e.g., no proof on an unsigned credential)

Click on any step with errors to expand it and see the details, including:

  • The JSON path where the error occurred (e.g., /credentialSubject/product/name)
  • What went wrong (e.g., "must have required property 'name'")
  • Additional context from the schema validator

Getting Help with Errors​

When validation fails, click the Copy button in the results header. This copies a structured summary of all errors — including JSON paths, error messages, and context — formatted for pasting into an AI assistant.

tip

If you use an AI assistant (like Claude) with UNTP schema context loaded, pasting the copied error summary gives the AI everything it needs to suggest specific fixes to your credential JSON.

Validation in the Editor​

You don't need to leave the editor to validate. See Editing Drafts for details on using the Run Tier 2 Tests button.