> 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/failed-charge.md).

# Failed Charge

In cases where a charge fails, a specific sequence of actions occurs to manage the situation effectively:

1. Charge Failure: When a payment charge fails for a user's rental, their account transitions into a delinquent state. This status restricts their ability to initiate any new rentals until the payment issue is resolved.
2. Rental Restriction: While in the delinquent state, the user is unable to make new rental transactions. This helps ensure that rentals are not carried out without successful payment.
3. Adding a New Payment Method: To regain full access to the rental service, the user needs to add a new, valid payment method to their account. This ensures that future rentals can be successfully charged.
4. Retry Failed Charges: Once a new payment method is added, any pending failed charges associated with the user's account are retried. This process aims to facilitate successful payment collection for previously attempted rentals.

<br>


---

# 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/failed-charge.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.