> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/studio/payments/issue-credential.md).

# Issue Credential with Encrypted Status List

Issuers are able to add encrypted Status Lists to the body of the Credential if they have previously created an Encrypted Status List on-ledger.

## Step 1: Set up your account

Make sure you have set up your account with cheqd Studio and are logged in, using our guide below:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Set Up Your Account</strong></mark></td><td>Set up your account with cheqd Studio and log in to start using the APIs.</td><td><a href="/pages/zU8toGQIPPKgvPjEFrgj">/pages/zU8toGQIPPKgvPjEFrgj</a></td></tr></tbody></table>

## Step 2: Create an Issuer DID

Before you can create an encrypted Status List for charging for Credentials, you need to create a DID which is used to link the Status List on-ledger. Use the API in the page below to create a DID:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Create an Issuer DID</strong></mark></td><td>Create a W3C conformant DID on cheqd using the <code>did:cheqd</code> DID Method.</td><td><a href="/pages/qUmEjgDklCArrhh4j9e9">/pages/qUmEjgDklCArrhh4j9e9</a></td></tr></tbody></table>

## Step 3: Create an Encrypted Status List

Follow the tutorial here to create an encrypted Status List with a set of Payment Conditions to unlock:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Charge for Status List</strong></mark></td><td>Create an encrypted Status List on-ledger with Payment Conditions to unlock, to charge for unlocking Status Lists.</td><td><a href="/pages/wqtwAnDLncElws03qL47">/pages/wqtwAnDLncElws03qL47</a></td></tr></tbody></table>

## Step 4: Specify the encrypted Status List within Credential body

Follow the instructions within the `/credential/create` API below to format and issue a Verifiable Credential.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Issue Credential</strong></mark></td><td>Issue a W3C conformant Verifiable Credential using the cheqd Studio APIs.</td><td><a href="/pages/6jXbnli2176kASJM5rQC">/pages/6jXbnli2176kASJM5rQC</a></td></tr></tbody></table>

{% hint style="info" %}
Ensure that the "`statusListName`" and "`statusPurpose`" are the same as the Status List [created in Step 3](#step-3-create-an-encrypted-status-list). This makes sure that if the Credential Status is changed, for example, if it is revoked or suspended, the correct Status List will be updated.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.cheqd.io/product/studio/payments/issue-credential.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.