> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/account-and-subscription/past-due-invoice.md).

# Past due invoice

### How to clear a past due invoice?

If your invoice payment has failed, your subscription will be marked as past due. Payments are processed automatically, so a past due status usually means there is an issue with your saved payment method.

#### Steps to follow

**Step 1: Go to billing**

* Log in to your AppMySite account.
* Click on Profile from the top menu.
* Select Billing from the side menu.

**Step 2: Open subscriptions**

* The Subscriptions screen will appear.
* Locate your active subscription.

**Step 3: Resolve payment issue**

* If your payment method is outdated or invalid, update it.
* Click on Upgrade to retry the payment once your method is updated.

**Step 4: Complete payment**

* Once the payment method is corrected, the invoice will be charged automatically.
* Your subscription will return to active status once the payment clears.

{% hint style="danger" %}
If you are unable to resolve the issue, submit a support ticket here: [**Contact Support**](https://app.appmysite.com/email-support)**.**
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/frequently-asked-questions/account-and-subscription/past-due-invoice.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.
