Docs Using the wallet Publishing and verification

Public Registry and Verification

Understanding the Public Registry

What is the Registry?

The Public Registry is a service where:

  • Your DID Documents are published automatically
  • Public credentials can be published for verification
  • Anyone can resolve and verify published items
  • No authentication needed for read access

Think of it as a public directory where verifiers can look up your credentials and DIDs.

Publishing Credentials

Making a Credential Public

When a credential is public, anyone with its id can view it, verify its signature, check its status, and download it.

To publish a credential:

  1. Open the credential
  2. Open the actions menu and choose Change visibility
  3. In Update Credential Visibility, select Public

The credential’s id is its public address. When the company has no registry base URL, that address is:

https://your-wallet.com/api/registry/vc/{uuid}

Company Registry Base URL in company settings replaces that prefix. The wallet appends the same UUID. Revocation and suspension lists stay on the deployment host. The full patterns, including GS1 licenses, are in Registry addresses.

When to Make Credentials Public

Good for public credentials: - Business licenses anyone can verify - Public certifications - Membership in public organizations - Product compliance certificates - Published attestations

Keep private: - Confidential business information - Internal authorization credentials - Personally identifiable information - Trade secrets - Credentials with sensitive claims

Verifying Published Credentials

Give verifiers the credential id. That id is the URL. Copy it from the credential with Copy ID.

Opening that URL in a browser goes to the verifier page for the credential. A tool that asks for JSON-LD or a VC-JWT receives the credential itself.

QR codes

A credential offer can be shown as a QR code so a holder can redeem it. That code is the offer, not a public registry address. To let someone check a published credential, share the credential id.

DID Document Publication

Automatic Publication to Registry

Your DID Documents are automatically published to:

  • The wallet’s registry
    • Accessible via API endpoints
    • Enables credential verification through the wallet

Publishing to Your Domain (did:web)

An identifier this wallet creates for a company is already on the wallet’s registry:

did:web:your-wallet.com:api:registry:did:{name}
https://your-wallet.com/api/registry/did/{name}/did.json

{name} is the company name in lower case, with spaces written as underscores.

An identifier on your own domain needs that domain to serve the DID document. A domain-only identifier such as did:web:your-domain.com is served at https://your-domain.com/.well-known/did.json. A path uses slashes and still ends in did.json. Forward the path to the wallet, or host a copy of the document. See how did:web works.

Verifying DID Resolution

To check if your DID resolves correctly:

  1. Go to Identities
  2. Look at the resolution status on each identity
  3. A check mark means the DID resolves
  4. A warning mark means resolution failed. Hover it for the reason

Public API Access

For Verifiers

Share these endpoints with parties verifying your credentials:

Resolve a DID:

GET https://your-wallet.com/api/registry/did/{did}
GET https://your-wallet.com/api/registry/did/{did}/did.json

{did} is a full DID, or the short name {name} from the default identifier above.

Resolve a credential: request the credential id. For a credential issued without its own id, and with no company registry base URL, that is:

GET https://your-wallet.com/api/registry/vc/{uuid}

Check credential status: {purpose} is revocation or suspension.

GET https://your-wallet.com/api/registry/status/{purpose}/{uuid}

These endpoints require no authentication. Private credentials are not returned. The patterns are collected in Registry addresses.

Using Verification Tools

Provide verifiers with:

  1. Your wallet’s base URL
  2. The credential or DID identifier
  3. They can use standard verification tools

Many SSI verification tools automatically: - Resolve your DIDs - Fetch credentials - Verify signatures - Check status lists