> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/account-and-billing/billing-faq/payments-and-invoices.md).

# Payments and invoices

### Which payment methods does GitBook accept?

GitBook supports the most common payment methods globally. You can view the options supported in your region in the checkout flow when you upgrade. Credit cards (Visa, Amex, Mastercard) are supported across all regions.

Payment by invoice is available on the Enterprise plan. All other plans are paid by credit card or the localized payment methods available in your region.

### Where can I find my invoices and update billing details?

GitBook uses Stripe for billing. To access your invoices:

1. Go back to your organization **Home** and click **Settings**.
2. Click **Billing** under the **Organization** group, then click **Manage Billing** to open the Stripe billing portal.
3. Open **Invoice History** and click the arrow next to any payment to download it.

To update billing information, click **Update Information** in the billing portal. You can add additional email addresses — for example, your finance department — that receive invoices without having GitBook access.

{% hint style="info" %}
Update billing details before making a payment. GitBook cannot change company information on invoices that have already been paid.
{% endhint %}

### Why was I charged for an unexpected plan upgrade?

Plan upgrades always require confirmation through a modal that shows the plan details and pricing before processing payment. Certain actions can trigger these upgrade prompts:

* Publishing a site with Premium or Ultimate features enabled
* Adding custom domains or advanced customizations

If you believe you were charged in error, contact support with your receipt number. To avoid unexpected charges, review any upgrade prompts before confirming.

### I paid for a yearly plan. Why did I receive another invoice?

This can happen if you add members after starting an annual plan. Each member counts as a paid seat, so added seats create prorated annual-plan adjustments. Depending on the amount due and the timing of the change, GitBook might include those charges in a true-up or send an additional invoice straight away. See the [Billing policy](/docs/account-and-billing/plans/billing-policy.md) for the current rules.

### Why don’t add-on flat fees appear on my bill immediately?

GitBook bills the Advanced AI Assistant and Translations add-ons at the end of the billing period, so usage charges can be included alongside the flat fees. These add-ons don’t appear on your bill until they’re used for the first time.

Each add-on includes a monthly allowance — a set number of successfully answered questions for the Advanced AI Assistant, and a set number of translated words for Translations. If you go over, GitBook keeps the feature running and bills the extra usage on your next invoice. See [our pricing page](https://www.gitbook.com/pricing) for the current limits.

### Do you offer discounts?

You get two months free by subscribing to an annual plan. Beyond that — and the free [Community plan](/docs/account-and-billing/plans/community.md) for non-profits and open-source projects — GitBook doesn’t offer other discounts at this time.

### Can I get a refund?

As set out in our [Terms of service](https://gitbook.com/docs/policies/terms), GitBook doesn’t offer refunds. Any unused fees are credited to your account for future use. If you think you’ve been charged incorrectly, contact support.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.com/docs/account-and-billing/billing-faq/payments-and-invoices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.