> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/groups/subscription-management/updating-billing-information.md).

# Updating billing information

Keeping your billing information up-to-date ensures uninterrupted access to your Overleaf subscription. You can easily update your payment details or billing information through your account settings.

## How to update your billing information

1. **Sign in to your Overleaf account**\
   Go to [Overleaf](https://www.overleaf.com) and log in to your account.
2. **Navigate to the Subscription page**\
   Visit your [Subscription page](https://www.overleaf.com/user/subscription) to view and manage your subscription details.
3. **Edit payment information**
   * If you’re paying via credit/debit card or PayPal:
     * Click on the **Update your billing details** button.
     * Enter your new payment details and save your changes.
   * For manually billed accounts (such as Purchase Orders), please contact the [Overleaf Support Team](https://www.overleaf.com/contact) to update your billing details.
4. **Verify your changes**\
   After updating your information, check that your subscription status is active and the next billing date is correctly listed on your [Subscription page](https://www.overleaf.com/user/subscription).


---

# 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.overleaf.com/groups/subscription-management/updating-billing-information.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.
