> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/features/settings/payments.md).
# Payments
The Payments tab is used to manage billing data and invoices associated with the account in the Bluur system.
### Payment settings
In the **Payment settings** is visible **billing email address**.
This address can be used for communication related to payments, invoices, and subscription management.
### Invoices
Section **Invoices** contains a list of billing documents assigned to the account.
The invoice table contains information such as:
* invoice number or name,
* amount,
* payment status,
* creation date,
* option to download the invoice.
To download an invoice, use the option available in the column **Download**.
### Invoice language
The user can choose the language in which invoices will be generated. Two options are available: **Polish** and **English**.
The selected language will be used when issuing subsequent sales documents.
{% hint style="info" %}
**Important:** If no invoice language is selected, the system will default to English and generate the document in that language.
{% 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://bluurdoc.bluur.ai/en/features/settings/payments.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.
