Service
Verifiable Credentials
W3C VC and DID implementations that ship to production — not just proofs of concept. Credential issuance, verification, wallet integration, and trust registry design built for real-world use.
Portable Identity That Doesn't Phone Home
Verifiable Credentials let you issue tamper-proof, cryptographically signed digital credentials that users carry in their own wallets. Verifiers can check them without calling back to your server — giving users privacy while giving verifiers confidence.
The W3C VC Data Model is a mature standard. The hard part isn't the specification — it's integrating it with existing identity infrastructure, designing the right trust model, and actually getting wallets and verifiers to work together. That's where DVLY comes in.
W3C VC Data Model 2.0
Credential issuance conformant with W3C VC Data Model 2.0 — including JSON-LD and JOSE/SD-JWT credential formats with selective disclosure support.
DID Method Implementation
did:web, did:key, did:jwk, and did:ion — we select and implement the DID method that fits your trust model and infrastructure constraints.
Credential Issuance
OIDC4VCI (OpenID for Verifiable Credential Issuance) issuer implementation — pre-authorized code flow, authorization code flow, deferred issuance.
Credential Verification
OIDC4VP (Verifiable Presentations) verifier implementation — presentation request, wallet response, proof verification, and status list revocation checking.
Wallet Integration
Integration with Microsoft Entra Verified ID, Trinsic, Walt.id, and custom wallet builds using the OIDC4VC suite of protocols.
Trust Registry
Trust registry design and implementation for multi-party ecosystems — defining which issuers your verifiers will accept and how that list is governed and updated.
How a Verifiable Credential Flow Works
A complete VC ecosystem involves three parties: issuer, holder, and verifier. DVLY can implement any or all of these roles.
Issuer authenticates the user — through your existing CIAM platform (Auth0/Okta), identity verification, or out-of-band process.
Issuer signs and issues the credential — using an OIDC4VCI flow. The credential is signed with the issuer's DID key and includes the user's verified attributes.
User stores the credential in their wallet — a standards-compliant wallet app (mobile or browser-based) that the user controls.
Verifier requests a presentation — using OIDC4VP, the verifier specifies which credential types and attributes it needs.
User approves and presents — the wallet creates a Verifiable Presentation, signed with the user's key, and presents it to the verifier.
Verifier checks the proof — verifies the issuer's signature against the trust registry, checks revocation status, and grants access based on the verified claims.
Frequently Asked Questions
What are Verifiable Credentials and why do they matter?
Verifiable Credentials (VCs) are tamper-proof digital credentials issued by a trusted authority and cryptographically signed so they can be verified by anyone without calling back to the issuer. They enable portable, privacy-preserving identity — users carry their own credentials and share only what's needed.
What DID methods does DVLY support?
DVLY has worked with did:web, did:key, did:jwk, did:ion, and did:ethr. We recommend did:web and did:key for most enterprise use cases due to their simplicity and lack of blockchain dependency. We'll advise on the right method for your trust model and infrastructure constraints.
Can DVLY integrate VCs into our existing Auth0 or Okta platform?
Yes. DVLY integrates VC issuance and verification into Auth0 Actions and Okta Hooks, so that verified credentials can gate access, populate user profile attributes, or drive authorization decisions within your existing CIAM platform.
What wallet integration options does DVLY support?
DVLY integrates with OIDC4VCI (OpenID for Verifiable Credential Issuance) and OIDC4VP (Presentation) for wallet-agnostic credential exchange. We've worked with Microsoft Entra Verified ID, Trinsic, Walt.id, and custom wallet builds.
What is a trust registry and do I need one?
A trust registry is a directory of authorized issuers whose credentials a verifier will accept. If you're building a multi-party ecosystem where different organizations issue credentials that your platform needs to verify, you need a trust registry. DVLY designs and implements trust registry infrastructure appropriate to your governance model.
Ready to issue your first verifiable credential?
We'll get you from zero to a working OIDC4VCI issuer faster than you expect.
Talk to DVLY