> 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/functions/settings/subscription/purchase-plan/payment-window.md).
# Payment window
Filling in billing details and choosing a payment method.
### Order summary
On the left side of the payment window is a summary of the selected plan.
The user can check:
* the name of the selected plan;
* billing period;
* subscription price;
* additional items included in the billing;
* VAT amount;
* the total amount to pay.
Additional items may include, among other things, extra pages or users exceeding the limit of the basic plan. If such items apply to the order, they are shown as separate line items in the summary.
### Billing details
On the right side of the payment window are the details required to complete the purchase and issue billing documents.
If the company details were previously entered in the system, the form may be filled in automatically. Before confirming payment, check that all information is correct.
The form may include, among others:
* email address;
* company name;
* country;
* street and number;
* postal code;
* city;
* tax identification number.
{% hint style="warning" %}
**Important:** Incorrect details may be used when issuing the invoice, so they should be verified before making the purchase.
{% endhint %}
### Payment method
The subscription can be paid by credit card. The form requires:
* card number;
* expiration date;
* CVC code.
Additional payment methods may also be visible in the form, such as Apple Pay or Link. The availability of these options depends on the payment provider's settings and the device and browser being used.
The payment method can later be managed in the portal available after selecting the button **Manage subscription**.
### Promo code
If the user has a discount code, they can apply it before completing the purchase.
Click **Add promo code**, enter the received code, and then confirm it in the form.
After the code is applied correctly, the system will automatically recalculate the order value, and the updated amount will be shown in the summary.
The code may only be valid for specific plans, currencies, or billing periods.
Order summary and the option to apply a promo code.
### Completing the purchase
After filling in the billing and payment details, check the order summary and then confirm the payment.
After the transaction is completed successfully, the subscription will be activated on the account. The user will be able to use the system according to the limits and features of the selected plan.
The invoice and payment confirmation will be sent to the email address used for billing. The documents will also be available in the section **Settings >** [**Payments**.](/en/functions/settings/payments.md)
### Failed payment
If the payment is declined, the form will display a message informing you of the issue.
Check:
* the correctness of the card details;
* its expiration date;
* available funds;
* the ability to make online payments;
* limits set by the bank.
After correcting the details, you can try to complete the payment again. If the problem persists, contact your bank or go to the section [**Technical Support**.](/en/system/technical-support.md)
---
# 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://bluurdoc.bluur.ai/en/functions/settings/subscription/purchase-plan/payment-window.md?ask=&goal=
```
`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.