01 / VITNI
The achievement and the award are different records
An achievement definition describes what an issuer awards: its name, explanation, criteria, and optional skills or standards alignment. A credential records that a particular recipient received that achievement from that issuer.
Vitni authors the achievement in an organization workspace. When an issuer awards it, Vitni creates a separate signed credential snapshot. This lets the award carry its own dates, recipient reference, proof, and status while pointing back to the achievement definition.
02 / VITNI
The badge image is only one part
Badge artwork helps people recognize an achievement at a glance. Vitni’s structured editor selects its palette, shape, and symbol, then publishes an SVG image. The actual credential data is delivered as a JSON-LD document using Open Badges 3.0 and the W3C Verifiable Credentials Data Model 2.0.
A printable certificate and a social preview help present the award, but they do not replace the signed credential. The holder can share its public page or download the credential document for inspection.
03 / VITNI
Issuer identity and status matter after issuance
Each Vitni customer organization has one issuer identity. A verifier can dereference the published issuer information and key, check the proof, inspect the credential dates, and check the signed status list for revocation.
A valid signature shows that the credential matches the issuer’s published key. It does not prove that the achievement happened or that the issuer’s statements are true. Verification results need to be interpreted with that boundary in mind.
04 / VITNI
Portability depends on compatible implementations
Open formats make it possible for different services to exchange and inspect credentials without treating one vendor’s screen as the only source of truth. Vitni exposes public credential and issuer documents and offers downloads for recipients.
Interoperability depends on more than naming a standard: proof methods, status handling, and how services resolve public documents all need to agree. Vitni’s behavior-level review against independent Open Badges implementations remains active work.
GO DEEPER
Step-by-step product documentation
Use the Vitni documentation for the operational details behind this workflow.
Read Vitni’s credential documentation