> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/billing/pending-charges.md).
# Pending Charges
**Pending Charges** can be found under the **Billing** section. This will provide you with a list of users who have pending charges that need to be reviewed by an admin. The list will contain the user name, email, rental date, amount, and current status. You can also export this list to a .csv file when you click the **Export** button.
The admin has the power to update the status of the charge whether it will be approved or rejected.
Example of Pending Charges
When you click **Update**, this pop-up window will appear and you have to **select an action**:
* Approve full amount
* Approve custom amount
* Decline
Clicking on the **Approve custom amount** will prompt you to enter the specific charge you want. You also have the option to leave a note for internal reference and the user.
Example of Approve Customer Amount
{% hint style="info" %}
When a pending charge is **approved**, the charge will go through on the user's card on file and will be displayed on the transaction information under the user's rental.
{% endhint %}
Example of approved pending charge
{% hint style="warning" %}
When a Pending charge is **Declined**, the charge is **canceled** on the user's account and will not go through.
{% endhint %}
Example of a declined pending charge
---
# 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://documentation.movatic.co/admin-site/billing/pending-charges.md?ask=&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.
