# Verifiable Credentials Issuance

Social Registry can issue credentials in the form of [Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) (VC). Upon authentication, these can be downloaded into the beneficiary's **digital wallet** or printed on paper as a **QR code.** These credentials indicate that the individual is the member of the Social Registry. Credentials are sometimes also referred to as e-cards, Farmer Registry e-Card, etc.

## High-level workflow

{% embed url="<https://miro.com/app/board/uXjVKfQuzM4=/>" %}

## Feature and functionality

* Social Registry exposes [OpenID for VCI](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html) APIs. A wallet can use these APIs to retrieve the VCs.
* The content inside the VC can be configured without modifying the code.
* Any functional/foundational ID can be configured for authentication. For example, if the Registry contains National IDs (or National ID tokens) of individuals, and a valid eSignet authentication mechanism (or similar) exists against the given National ID, then the credential can be issued.
  * **Future possibilities**: If the Social Registry generates a unique ID, then that can be used to authenticate and retrieve the credential.

{% hint style="info" %}
Bulk VC issuance is not supported.
{% endhint %}

## Configuration & Technical documentation

VCI uses Odoo modules:

* [G2P OpenID VCI: Base](/products/pbms/previous-generation/developer-zone/odoo-modules/g2p-openid-vci-base.md)
* [G2P OpenID VCI: Rest API](/products/pbms/previous-generation/developer-zone/odoo-modules/g2p-openid-vci-rest-api.md)

## Related user guides

* [Configure Inji to download Social Registry VCs](/products/registry/registry/_archive/social-registry/features/verifiable-credentials-issuance/user-guides/configure-inji-to-download-social-registry-vcs.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openg2p.org/products/registry/registry/_archive/social-registry/features/verifiable-credentials-issuance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.