# Charge for Verifiable Credentials

Credential Payments brings a significant evolution to the Verifiable Credentials landscape, allowing **verifiers to directly pay issuers to unlock Credential Status information**. Underneath the hood, we've engineered a robust and secure payment flow that streamlines the end-to-end payment process, with accuracy, speed, and cryptographic integrity.

## Get started

Create encrypted Status Lists on-ledger, and pay to unlock the Access Control Conditions in CHEQ, using our **cheqd Studio Payments APIs**:

<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>With Credential Payments, Issuers are able to create payment-gated Status Lists in order to charge for the verification of Credential Status information.</td><td><a href="payments/charge">charge</a></td></tr><tr><td><mark style="color:blue;"><strong>Issue Credential with Encrypted Status List</strong></mark></td><td>Issue a Verifiable Credential referencing an encrypted Status List in the body, with a specified bitstring index.</td><td><a href="payments/issue-credential">issue-credential</a></td></tr><tr><td><mark style="color:blue;"><strong>Verifier pays Issuer</strong></mark></td><td>Understand how a Verifier pays an Issuer in CHEQ to unlock Status List and verify Credential Status.</td><td><a href="payments/verifier-pays-issuer">verifier-pays-issuer</a></td></tr><tr><td><mark style="color:blue;"><strong>Bulk Update or Rotate Encryption Keys</strong></mark></td><td>Update a set of Credential indices or rotate the encrypted symmetric key for the Status List.</td><td><a href="payments/update">update</a></td></tr></tbody></table>

## Learn more

Build your understanding of How Credential Payments work, including Access Control Conditions and how the model preserves privacy.

<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>Understanding Credential Payments</strong></mark></td><td>Before diving into Credential Payments, developers may want to learn how the Payment gating and Access Control condition logic works.</td><td><a href="payments/learn">learn</a></td></tr><tr><td><mark style="color:blue;"><strong>Why are we payment gating Status Lists?</strong></mark></td><td>Learn about the role of cheqd in Trusted Data Markets and why we are payment gating the "reputability" of Credentials.</td><td><a href="https://cheqd.io/blog/the-role-of-cheqd-in-trusted-data-markets/">https://cheqd.io/blog/the-role-of-cheqd-in-trusted-data-markets/</a></td></tr></tbody></table>

## Alternatives

Below are a list of alternatives for using Credential Payments.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Veramo SDK Plugin</strong></mark></td><td>The <strong>Veramo SDK Plugin</strong> is an extension of the Veramo SDK, a JavaScript framework for Trusted Data, adding support for cheqd functionality.</td><td><a href="../sdk/veramo">veramo</a></td><td><a href="https://3569764573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVAMvpKH7PYzvXA6u6Cn%2Fuploads%2Fgit-blob-031af91fab341ad25703bd5d5924bda95df8e5fe%2Fveramo%20logo.png?alt=media">veramo logo.png</a></td></tr></tbody></table>


---

# 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.cheqd.io/product/studio/payments.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.