> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/miscellaneous/how-do-i-update-my-billing-information-e.g.-credit-card-on-file.md).

# How do I update my billing information (e.g. credit card on file)?

Most accounts can use [www.perkville.com/billing](https://www.perkville.com/billing) to update the credit card on file.

## Who can update billing?

Perkville assigns one **billing-responsible user** to each business account. This designation is separate from a staff member's role and location permissions.

Being an **Admin** does not automatically make someone the billing-responsible user, even if that Admin can access all locations. For multi-location programs, billing responsibility applies at the business-account level rather than being granted separately by location.

You can review or change the billing-responsible user from **Settings → Staff members**. See [Staff members](https://docs.perkville.com/features/settings/staff-members.md) for more information.

If you cannot access the billing page, or the self-service billing page does not apply to your account, contact **<support@perkville.com>** and we will send an authorized user a secure link to update the billing information.


---

# 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.perkville.com/faqs/miscellaneous/how-do-i-update-my-billing-information-e.g.-credit-card-on-file.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.
