Overview
Institutions issue a digital student ID credential to every enrolled student, stored securely in their wallet and usable across campus services and partner ecosystems.
Why it matters
Student identity is used across many interactions: portal access, facility entry, exam attendance, and partner discounts. A verifiable student ID reduces friction while keeping verification consistent and privacy‑preserving.
Ecosystem roles
- Issuer: The institution’s student management system.
- Holder: The student.
- Verifier: Campus services, libraries, facilities, and partner organisations.
Operational considerations
Credentials can be refreshed when status changes (active, suspended, graduated). Photo and attributes are controlled by the issuer and verifiable by relying parties.
| Objective | To issue a student ID card to a registered student |
| Description | The student ID card will contain identification information about the student. |
| Actors | Student |
| Dependencies | Student: is registered; is active; has a mobile device. |
| Preconditions | The student has all details entered in the Student Management System, including a passport quality photo |
| Postconditions | The student has a digital ID card stored on their mobile device. |
flowchart LR
UNI@{icon: "fa:building-columns", label: "Institution", pos: "b"} -->|Issues student ID VC| WAL@{icon: "fa:wallet", label: "Wallet", pos: "b"}
WAL -->|Presents credential| VER@{icon: "fa:id-badge", label: "Campus verifier", pos: "b"}
VER -->|Verify issuer, status| REG@{icon: "fa:book", label: "Student registry", pos: "b"}
sequenceDiagram
participant Institution
participant Wallet
participant Student
participant Verifier as Campus verifier
participant Registry as Student registry
Institution-->>Wallet: Issue student ID VC
Student->>Wallet: Stores credential
Student->>Verifier: Present student ID VC
Verifier->>Registry: Check issuer and status
Registry-->>Verifier: Valid
Verifier-->>Student: Access granted