> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/credentials/technical-overview/high-level-architecture.md).

# High-Level Architecture

The microservices behind Sunbird RC credentialling, and how identity, schema, issuance and verification flows work.

Sunbird RC's credentialling service is made up of three microservices. Expand each to learn what it does.

<details>

<summary>Identity microservice</summary>

The central lynchpin for maintaining identities across the system. All identities in Sunbird RC are DID-compliant and web-resolvable. The other two microservices (Credential Schema and Credential Issuance) depend on it to generate any identity.

</details>

<details>

<summary>Credential Schema microservice</summary>

Stores the schema of each verifiable credential, along with its associated view template.

</details>

<details>

<summary>Credential Issuance microservice</summary>

The core issuance service. It takes a payload, transforms it into a W3C-compliant verifiable credential in JSON-LD format, and signs it using the private key generated when the issuer was created.

</details>

## High-level component diagram

<figure><img src="https://content.gitbook.com/content/t31Mw1vCDrqioMWJh6yJ/blobs/E1qd9DvxACTxgxhLk6dr/component.png" alt=""><figcaption></figcaption></figure>

## How it works

{% tabs %}
{% tab title="Direct API flow" %}
This sequence diagram explains the following flows:

* Creating an identity
* Creating a schema
* Issuing a credential
* Verifying a credential

<figure><img src="https://content.gitbook.com/content/t31Mw1vCDrqioMWJh6yJ/blobs/4EzOPuqpCslNlWSBfIbF/credential-sequence-1.png" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="OID4VC / VP wallet flow" %}
This sequence diagram explains the OID4VC/VP flow:

* Creating an identity
* Creating a schema
* Fetching issuer metadata (OID4VCI discovery)
* Issuing a credential (OID4VCI, wallet-initiated pre-authorized flow)
* Verifying a credential (OID4VP, DCQL-based presentation)

<figure><img src="https://content.gitbook.com/content/t31Mw1vCDrqioMWJh6yJ/blobs/jlyeCSnl7IHbMkPjuA7E/sequence_diagram_oid4vc.png" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://rc.sunbird.org/credentials/technical-overview/high-level-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.