> 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/system/billing-and-licensing/no-payment.md). # No payment This section describes a situation in which the account does not have an active subscription. Here you will find information about choosing a plan and reactivating the service. ## Non-payment. What happens then? If the subscription fee cannot be collected (e.g. the card has expired, the details have changed, or there are insufficient funds), the system continues to operate normally for **14 days** from the due date. During this time: * the system remains active * Stripe sends **4 payment reminders to the email address** * up to **8 attempts to collect the payment within 30 days** from the due date If payment is still not made after this time, the license in the system is given the status **unpaid**. After 14 days from the due date, if the payment remains unsettled, as the manufacturer we reserve the right to restrict access to the full version of the system. In practice, this means switching to the free version, without the features available under the previously active subscription. If the payment problem is due to technical reasons or the situation requires clarification, we encourage you to contact us: * with your account manager * through standard contact channels * or directly: **** {% hint style="warning" %} Simply disconnecting the payment card or having insufficient funds in the account does not cancel the subscription. If the subscription is not canceled before the start of the next billing period, the customer remains obligated to pay for the next period in accordance with the issued invoice, because access to the system and the license is still active. {% 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/system/billing-and-licensing/no-payment.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.