Trust & Verification
In design — architecture definedMake achievements easier to verify, carry and present—with consent.
W3C Verifiable Credentials and trusted achievement records
Digital credentials provide a structured way to represent achievements such as qualifications, certifications, course completion, professional licenses or assessed capabilities. DISHA 4.0 HCOS™ can support credential experiences aligned with W3C Verifiable Credentials concepts, subject to issuer support, wallet interoperability, applicable standards versions and implementation validation. A digital credential should communicate who issued it, what it asserts, and how a verifier can check its integrity and status.
Explore how portable, verifiable achievements can reduce repeated document handling while keeping the holder in control of presentation.
The credential data model and wallet architecture are defined; issuance is not yet live.
In depth
What a verifiable credential represents
A credential is an issuer’s digitally signed claim about a subject. It may include an achievement, award, qualification, competency or membership. The credential holder can receive and store it, then present it to a relying party. Verification checks authenticity and integrity; it does not automatically prove that every assertion is current, complete or equivalent to another credential.
The credential lifecycle
An issuer defines a credential schema and eligibility process, verifies the claim, issues the credential and delivers it to the holder. The holder reviews and stores it. When needed, the holder chooses what to present. A verifier checks issuer trust, cryptographic proof, schema, validity dates and revocation or status information where available.
Interoperability and standards
Standards alignment requires more than displaying a W3C label. Implementation must specify the credential data model and version, proof mechanism, issuer identifiers, status mechanism, presentation protocol, key management and interoperability profile. Different ecosystems may have distinct requirements, so conformance and partner testing should be documented.
Credential quality and meaning
A cryptographically valid credential proves that an issuer made a particular claim under a particular process. It does not itself guarantee the quality of the issuer, the rigor of assessment or equivalence across jurisdictions. DISHA should show issuer identity, credential scope, issue date, expiry if applicable, and the verification result in understandable language.
Holder control and privacy
Credential presentation should be initiated by the holder, limited to the requested purpose and restricted to necessary claims where the technology supports selective disclosure. Avoid public exposure by default. Provide clear information about recipients, retention and how a credential may be used.
How it works
Capability domains
Frequently asked questions
Does a valid signature prove the achievement is equivalent everywhere?
No. It supports integrity and issuer authentication; recognition and equivalence depend on issuer authority and receiving-party requirements.
Can credentials be revoked?
A supported status mechanism may allow validity checks; exact behavior depends on the credential ecosystem and issuer.
Trust & Verification
Experience it inside the live platform.
Open the module that carries this capability, or talk it through with the team.