Core Capabilities

What Sunbird RC can do out of the box — registries, verifiable credentials, verification and wallet interoperability.

Registry

A governing body or authority can build a registry that acts as a single source of truth.

1. Define schema as per policy

   • Fields and field types: Create new fields in the registry to store specific types of information, and specify the type of data each field accepts. For example, a student registry might define fields for student name, father's name, mother's name, school name and age — with the age field accepting only numbers.

   • Field-level privacy: Set different levels of privacy for different fields based on how sensitive their data is. For example, in a patient registry, fields containing health information can be restricted to authorized healthcare professionals, while less sensitive fields such as demographics are available to a wider range of users.

   • Consent framework at schema level

2. Create entities

   • Bulk invite or onboard users via CSV

   • Link to external systems

   • Let users self-register

   • Decide, at field level, who can view the content

3. Define ownership

   • Define which entities can log in and how authorization is handled

4. Discovery

   • Control the visibility of discovery attributes through access control mechanisms such as consent-based sharing. Users can mark each discovery attribute as public (visible to all users), private (visible only to the user) or consent-based (visible to selected users or groups based on their consent).

5. Analytics

   • Basic analytics for registries

Verifiable Credentials (VC)

1. Define attestation and claim workflows

   • Tenants (users) can define an add-on workflow, customizing its steps to suit their needs, and configure whether claims are approved automatically or manually.

   • Attestation can run on an internal system like Sunbird RC, or on an external system the tenant connects to.

   • Claims can go through multi-level attestation — reviewed by multiple parties or levels of approval.

   • Define validity

2. Consent

   • Grant or revoke consent: Receive consent requests and grant or revoke access.

   • Consent auditing

3. Issuance services

   • W3C compliant

   • Create and issue verifiable credentials

   • Update and revoke credentials

   • Unique ID generation

   • Wallet interoperability via OpenID4VCI/OpenID4VP (optional, flag-gated on the registry side)

VC Verification

• Consent-based access: Give another system or person consent to access your verifiable credentials for the purpose of a transaction or interaction.

Digital Wallet (Interoperability)

The Sunbird RC platform implements OpenID4VCI and OpenID4VP, so citizens can use any compliant wallet — Sunbird-built or third-party — to hold and present their credentials.

Fetch and store credentials

• Issuance via OpenID4VCI 1.0 (draft-13 compatible): the issuer publishes a credential offer, the wallet resolves it, exchanges a pre-authorized code for a token, then proves key possession (nonce + PoP) to fetch the credential.

• Supports deferred issuance and issuance notifications.

• Formats: ldp_vc, jwt_vc_json, vc+sd-jwt, mso_mdoc

• Standard .well-known discovery endpoints — no custom wallet integration needed.

Share with consent

• Presentation via OpenID4VP 1.0 (draft-23): the verifier describes the claims it needs via DCQL, and the wallet fetches the request object and returns a vp_token.

• Consent is enforced at the wallet — the holder decides what to disclose against the query; there is no blanket handover.

• The verifier polls the presentation status to confirm what was shared.

Core Registry Verbs