> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/preferences/payouts-and-billing/billing.md).
# Billing
**The Billing tab is where you manage the payment method Alternative Payments charges and review your subscription and collections activity.**
***
### Where to find your billing settings
From the sidebar of your Partner Dashboard, go to **Team preferences** then **Payouts & billing**, and open the **Billing** tab.
***
### Payment Method
The **Payment Method** card shows the account used for any payments you make to Alternative Payments. Use the **…** menu beside the account to manage it.
***
### Subscriptions
The Subscriptions view has two sections:
* **Active subscriptions** lists your current plan and any add-ons, showing the type, billing frequency, next billing date, and amount.
* **Subscription payments history** lists your past subscription charges, showing the date, frequency, type, status, fees, and amount. Select **Download** to save a receipt for a charge.
**Love our platform?** Rate us on [Channel Program](https://channelprogram.com/v/alternativepayments) and check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!
---
# 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://help.alternativepayments.io/preferences/payouts-and-billing/billing.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.
