> For the complete documentation index, see [llms.txt](https://cpay-2.gitbook.io/cpay-coinprice-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cpay-2.gitbook.io/cpay-coinprice-api-documentation/guides/plan-and-billing/billing-history.md).

# Billing History

Here's the Billing History block:

![](/files/wu94WptKCXmyLeklXIvV)

Transactions for the purchase of a user plan or an additional package are displayed in this block.

The block consists of:

* Transaction date;
* Transaction status:\
   \- waiting - the first status that is assigned to a transaction after the start of the purchase of a fee or an additional package, that is, when the user opens the payment widget.\
   \- active - the status that is assigned to the transaction if the payment was successful.\
   \- declined - the status assigned to a transaction if it is no longer relevant. For example, a user created transactions for the purchase of Startup and Standard plans, eventually bought Startup, so transaction for the Standard plan will be assigned this status.
* Transaction price;
* Transaction name.

{% hint style="info" %}
Slippage tolerance set to 1 USD.
{% 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:

```
GET https://cpay-2.gitbook.io/cpay-coinprice-api-documentation/guides/plan-and-billing/billing-history.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.