Schemas, programmable
Five scenarios — from ecosystem schema standardisation to safe schema deprecation.
Five scenarios — from ecosystem standardisation to wallet rendering to safe schema deprecation.
Customer: A sector body (healthcare, financial services, logistics) that wants credential schemas standardised across issuers.
Outcome: Publishes VCTs like HealthcarePractitionerLicense; all member issuers mint against the shared schema. Verifiers see consistent claim shapes regardless of which member issued.
Customer: A member state hosting qualified attestation schemas (e.g. `NationalPIDCredential`).
Outcome: Centralises the schema so every national issuer and verifier reads from one source. Schema updates propagate to the whole ecosystem via VCT Registry, not email chains.
Customer: A wallet developer wanting rich, localised credential previews.
Outcome: Resolves `vct` → gets display name, description, icon URI, claim ordering. Wallet renders 'Driving Licence' with appropriate branding, not just a raw JSON blob.
Customer: A verifier platform that shouldn't need to ship credential schemas in its config.
Outcome: Resolves VCTs at runtime as presentations arrive. New credential types are immediately supported without a verifier redeploy.
Customer: An issuer rolling out v2 of a credential schema without breaking the existing population.
Outcome: Publishes v2 metadata, marks v1 as deprecated with `superseded_by` pointing to v2. Wallets surface v2 to users; outstanding v1 credentials continue to resolve and verify.
Request access to host VCT metadata with caching, versioning, and admin controls.