Skip to main content
Version: v4

Receive a credential for your service

A certification, a membership, a licence: a credential issued to your service by an accredited issuer of some ecosystem, published in your DID Document so wallets and peers see it in your Proof-of-Trust. Public credentials about services are W3C JSON-LD credentials issued over vt-flow.

Two paths​

Schema's holder modeWhat happens
Issuer onboarding processYou apply as Holder with the issuer as validator (onboarding process); after validation the issuer issues the credential in the same flow. The issuer can later revoke it by revoking your holder entry.
PermissionlessNo entry on the registry. Your agent sends an issuance request to the issuer's agent over DIDComm; the issuer accepts or declines and issues.

In both cases the agent verifies the credential it receives (format, schema credential, the issuer's accreditation for the schema at the issuance time) before accepting it, and refuses otherwise.

Steps​

  1. Find the issuer: the schema's active issuers in the frontend or the indexer, each a Verifiable Service you can resolve.
  2. Apply, or request: for issuer onboarding process, the frontend wizard with the issuer as validator; for permissionless, your backend starts a direct issuance flow on your agent against the issuer's DID. The Admin API route for the applicant side of direct issuance is part of the flow management scope.
  3. Provide what the issuer asks for: evidence through out-of-band links, or claims.
  4. Receive: the agent stores the credential and publishes it as a linked presentation, with a fragment of its own.

Verify​

The DID Document gains a LinkedVerifiablePresentation entry; resolving your DID lists the credential under presentations[].vtcCredentials with its schema and ecosystem; the playground's Proof-of-Trust shows it under "Other credentials" with its own validity mark.

Next​