> For the complete documentation index, see [llms.txt](https://help.fixfolio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fixfolio.ai/en/billing.md). # Payment - [Overview](https://help.fixfolio.ai/en/billing/overview.md): FIXFOLIO can be used through a subscription plan or by topping up credits. You can choose the payment method that suits your purpose and usage style. - [Plan Guide](https://help.fixfolio.ai/en/billing/pricing.md): FIXFOLIO offers personal subscription plans and enterprise plans depending on usage scale and operating method. Please choose the plan that best fits your required credit volume and team operating scope. - [Subscribe](https://help.fixfolio.ai/en/billing/subscription.md): With the monthly subscription plan, a certain amount of credits is automatically provided each month, making it convenient to use the service when you continuously need to create banners. - [Top Up Credits](https://help.fixfolio.ai/en/billing/credit.md): Credit top-up is a method where you purchase and use only the amount of credits you need. It is suitable when subscription credits are insufficient or when you want to create only as needed without a regular subscription. - [Request a Refund](https://help.fixfolio.ai/en/billing/refund.md): Products purchased from FIXFOLIO can be refunded according to the refund policy below. --- # 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.fixfolio.ai/en/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.