> 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/sdk/veramo/payments.md).

# Credential Payments

Get started with Payment Rails for Verifiable Credentials using Veramo.

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

<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="/product/studio/payments/learn.md">Understanding Credential Payments</a></td></tr><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="/product/sdk/veramo/payments/charge.md">Charge for Status List</a></td></tr><tr><td><mark style="color:blue;"><strong>Issue Credential with Encrypted Status List</strong></mark></td><td>Once an encrypted Status List has been created, it is time to issue a Credential referencing this Status List within the Credential body.</td><td><a href="/product/sdk/veramo/payments/issue-paid-credential.md">Issue Credential with Encrypted Status List</a></td></tr><tr><td><mark style="color:blue;"><strong>Verifier pays Issuer</strong></mark></td><td>Understand how a Verifier can pay an Issuer and how the Verifier receives access to the Status List.</td><td><a href="/product/sdk/veramo/payments/verifier-pays-issuer.md">Verifier pays Issuer</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-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>cheqd Studio</strong></mark></td><td>Our API product enables users to <strong>use cheqd's functionality with minimal complexity</strong> and easily integrate APIs into existing apps.</td><td><a href="https://3569764573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPVAMvpKH7PYzvXA6u6Cn%2Fuploads%2Fgit-blob-7f1ffe5c0546f0ee4f106ac1a71308c5ee5ad7c8%2Fcheqd_logo_card.jpg?alt=media">cheqd_logo_card.jpg</a></td><td><a href="/product/getting-started/studio.md">Get Started with cheqd Studio</a></td></tr></tbody></table>

##


---

# 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://docs.cheqd.io/product/sdk/veramo/payments.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.