Student ID - credential schema
When to use
Use this skill when you issue or verify a Student ID credential. The credential attests that a person is a student, and it carries the eduPerson and SCHAC attributes that the education federations use.
The registry gives the credential type VerifiableStudentID for SD-JWT VC
(dc+sd-jwt) and for mdoc (mso_mdoc), and VerifiableStudentIDJWT for W3C
JWT VC (jwt_vc_json). The namespace in the metadata is
eu.europa.ec.eudi.studentid.1.
The registry keeps this schema under
credentialSchemas/claimPathPointer/studentId. Version 2025.7.1 is the latest
version directory, and this skill uses it. The registry publishes the schema
in three formats: dc+sd-jwt, jwt_vc_json and mso_mdoc.
What the claims describe
Every claim in this schema is mandatory. The three formats hold the same claim names.
- Person:
firstName,familyName,commonName,displayName,dateOfBirthandmail. - Identifiers:
id,identifier,eduPersonPrincipalName,schacPersonalUniqueID, andschacPersonalUniqueCode(an array). - Affiliation:
eduPersonPrimaryAffiliationfor the main role,eduPersonAffiliation(an array) for every role, andeduPersonScopedAffiliation(an array) for the role with the organisation scope. - Organisation and assurance:
schacHomeOrganizationfor the home institution, andeduPersonAssurance(an array) for the identity assurance profiles.
Four claims are arrays, so their pointers end with null:
eduPersonAffiliation, eduPersonAssurance, eduPersonScopedAffiliation and
schacPersonalUniqueCode.
Claim path pointer documents
Each document below is the file that the registry holds. Copy it without a change.
SD-JWT VC (dc+sd-jwt)
| Fact | Value |
|---|---|
| Title | Student ID |
| Format | dc+sd-jwt |
credentialType |
VerifiableStudentID |
vct to send |
VerifiableStudentID |
| Namespace in the metadata | eu.europa.ec.eudi.studentid.1 |
validationPath |
$ |
| Claim carrier in the request | claims |
{
"claims": [
{
"path": [
"commonName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"dateOfBirth"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"displayName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"eduPersonAffiliation",
null
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"eduPersonAssurance",
null
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"eduPersonPrimaryAffiliation"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"eduPersonPrincipalName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"eduPersonScopedAffiliation",
null
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"familyName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"firstName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"id"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"identifier"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"mail"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"schacHomeOrganization"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"schacPersonalUniqueCode",
null
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"schacPersonalUniqueID"
],
"mandatory": true,
"limitDisclosure": true
}
]
}
W3C JWT VC (jwt_vc_json)
| Fact | Value |
|---|---|
| Title | Student ID |
| Format | jwt_vc_json |
credentialType |
VerifiableStudentIDJWT |
type to send |
an array that holds VerifiableStudentIDJWT |
| Namespace in the metadata | eu.europa.ec.eudi.studentid.1 |
validationPath |
$.vc |
| Claim carrier in the request | credentialDefinition |
This format uses the credential type VerifiableStudentIDJWT, not
VerifiableStudentID. The document also has no limitDisclosure field, because
jwt_vc_json has no selective disclosure.
{
"claims": [
{
"path": ["credentialSubject", "commonName"],
"mandatory": true
},
{
"path": ["credentialSubject", "dateOfBirth"],
"mandatory": true
},
{
"path": ["credentialSubject", "displayName"],
"mandatory": true
},
{
"path": ["credentialSubject", "eduPersonAffiliation", null],
"mandatory": true
},
{
"path": ["credentialSubject", "eduPersonAssurance", null],
"mandatory": true
},
{
"path": ["credentialSubject", "eduPersonPrimaryAffiliation"],
"mandatory": true
},
{
"path": ["credentialSubject", "eduPersonPrincipalName"],
"mandatory": true
},
{
"path": ["credentialSubject", "eduPersonScopedAffiliation", null],
"mandatory": true
},
{
"path": ["credentialSubject", "familyName"],
"mandatory": true
},
{
"path": ["credentialSubject", "firstName"],
"mandatory": true
},
{
"path": ["credentialSubject", "id"],
"mandatory": true
},
{
"path": ["credentialSubject", "identifier"],
"mandatory": true
},
{
"path": ["credentialSubject", "mail"],
"mandatory": true
},
{
"path": ["credentialSubject", "schacHomeOrganization"],
"mandatory": true
},
{
"path": ["credentialSubject", "schacPersonalUniqueCode", null],
"mandatory": true
},
{
"path": ["credentialSubject", "schacPersonalUniqueID"],
"mandatory": true
}
]
}
mdoc (mso_mdoc)
| Fact | Value |
|---|---|
| Title | Student ID |
| Format | mso_mdoc |
credentialType |
VerifiableStudentID |
doctype to send |
eu.europa.ec.eudi.studentid.1 |
| Namespace in the metadata | eu.europa.ec.eudi.studentid.1 |
validationPath |
$ |
| Claim carrier in the request | claims |
The first element of every path is eu.europa.ec.eudi. That value is the mDoc
namespace of the claims. It is not the same string as the doctype
eu.europa.ec.eudi.studentid.1. Send the doctype in the doctype field, and
keep eu.europa.ec.eudi as the first path element, as the registry has it.
{
"claims": [
{
"path": ["eu.europa.ec.eudi", "commonName"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "dateOfBirth"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "displayName"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "eduPersonAffiliation", null],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "eduPersonAssurance", null],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "eduPersonPrimaryAffiliation"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "eduPersonPrincipalName"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "eduPersonScopedAffiliation", null],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "familyName"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "firstName"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "id"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "identifier"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "mail"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "schacHomeOrganization"],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "schacPersonalUniqueCode", null],
"mandatory": true,
"limitDisclosure": true
},
{
"path": ["eu.europa.ec.eudi", "schacPersonalUniqueID"],
"mandatory": true,
"limitDisclosure": true
}
]
}
How to read a claim path pointer
A claim path pointer selects one claim in the credential. Each item of the
claims array holds these fields.
pathis mandatory and holds at least one element. Read the elements from left to right. A string element selects an object key. An integer element selects one array index. Anullelement selects every element of an array, so["nationalities", null]covers each entry of thenationalitiesarray.mandatorysays whether the issuer must supply a value for the claim. The issuer reads a missingmandatoryfield astrue.limitDisclosuresays that the holder can disclose the claim on its own. Set it only inside theclaimsobject of adc+sd-jwtormso_mdocconfiguration. Thejwt_vc_jsonformat has no selective disclosure, so its documents leave the field out.
A path that names a parent object, such as ["address"], and a path that names
a child, such as ["address", "country"], can both appear. The parent pointer
lets the holder disclose the full object. The child pointers let the holder
disclose one field at a time.
For mso_mdoc, the first element of the path is the mDoc namespace, every
path holds at least two elements, and every path of one configuration uses the
same first element.
For jwt_vc_json, the first element of the path is always credentialSubject.
Use with the iGrant.io API
Create a credential definition with
POST /v2/config/digital-wallet/openid/sdjwt/credential-definition. Put the
claims array of the registry document into the configuration entry, and set
the format fields that the table above gives.
{
"label": "Issue Student ID",
"version": "version_01",
"credentialDefinitions": [
{
"credentialFormat": "dc+sd-jwt",
"vct": "VerifiableStudentID",
"validationPath": "$",
"claims": {
"claims": [
{
"path": [
"commonName"
],
"mandatory": true,
"limitDisclosure": true
},
{
"path": [
"dateOfBirth"
],
"mandatory": true,
"limitDisclosure": true
}
]
}
}
]
}
Notes on the request.
labelmust hold at least 3 characters. The platform reserves the labelsPayment User Credential,Payment Card Credential,Payment Account Credential,PID IssuanceandPhoto ID Issuance, so pick another label.- Always send
versionwith the valueversion_01. The issuer falls back to an earlier version of the specification when you leave the field out, and you cannot change the value after you create the credential definition. - Add one entry of
credentialDefinitions[]for each format that you want to publish. You can publish more than one format from one credential definition. - Keep the
idthat the response returns for each entry. The issue operation uses that value to match the claims to a configuration. - Add
supportRevocation,revocationMethod,expirationInDays,displayand the other entry fields as your use case needs them.
Read igrantio-api-issuer for the full operation reference, the other request
fields, and the issue operation that follows.
Source is the registry
The verifiable data registry is the source of truth. If this skill and the registry file disagree, the registry wins. Fetch the source before you rely on a claim path, and report the difference so this skill can be corrected.
- Template directory: https://github.com/decentralised-dataexchange/verifiable-data-registry/tree/main/credentialSchemas/claimPathPointer/studentId
- Raw dc+sd-jwt document: https://raw.githubusercontent.com/decentralised-dataexchange/verifiable-data-registry/main/credentialSchemas/claimPathPointer/studentId/2025.7.1/dc+sd-jwt.schema.json
- The metadata file sits next to each schema file, with the suffix
.schema.metadata.json. It carries the title, the credential type, the doctype and the format flags.
Cross-references
igrantio-api-issuer- the create credential definition and issue credential operations.igrantio-api-verifier- the DCQL query that asks a holder for a Student ID credential.igrantio-ows-overview- architecture and glossary.