> For the complete documentation index, see [llms.txt](https://docs.zapsign.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zapsign.com.br/zapsign-api/english/creditos-e-pagamento.md).

# How Payment Works

{% hint style="info" %}
**Attention:** To use the ZapSign integration in production you must have an active API plan. To learn more about the plans [click here](https://zapsign.co/pricing) and for more documents [contact our sales team](https://zapsign.co/contact-sales). 
{% endhint %}

To use the production environment, you need to subscribe to an API plan via credit card which is automatically renewed. You have the option to choose between monthly or annual payments. If you exceed the number of documents included in your plan, the excess will be charged to your registered credit card at the end of the month.

You are responsible for tracking the volume of documents used. We will only provide a usage report at the end of the month if you exceed the document volume of your plan.

 **Unsigned and deleted documents do not "recover" credits. Once created, the document will be counted towards your API Plan usage.**

<figure><img src="https://github.com/AmandaAmani/documenta-ocurso/blob/main/plans%20and%20prices.gif?raw=true" alt="A user navigating within the platform goes to Settings > Plans and Pricing and subscribes to an API plan."><figcaption><p>Remember that you will always need an API plan to integrate tools with ZapSign.</p></figcaption></figure>


---

# 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.zapsign.com.br/zapsign-api/english/creditos-e-pagamento.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.