> For the complete documentation index, see [llms.txt](https://bolten.gitbook.io/bolten-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bolten.gitbook.io/bolten-docs/en/platform-user-manual/revenue-sharing-billing-model.md). # Revenue-sharing billing model Hey, partner! This page is for you who are on the **Pass-through model** — the one in which Bolten charges you directly for using the tools, and you charge your clients however you prefer. Here we explain, in a simple way, how your subscription payment works: from registering the payment method to what happens when you add a client, change a product, or deactivate a project. The entire financial side is handled by the **Stripe**, our billing partner, in an automated flow that you control yourself. 🚀 #### Registering your payment method When you access your Partner Area, a **banner at the top of the home page** appears inviting you to register the payment method for your subscription. It's your starting point. When you click the banner, you're taken to the registration screen, where you choose between two options: * **Credit card** * **Bank slip** The chosen method will be used for **all subscription charges** — both the monthly fee and any extra charges. {% hint style="info" %} **Our recommendation: use a credit card.** Both the card and the bank slip work normally, but the bank slip takes longer to clear and may cause access delays. With a card, billing is automatic and instant, with no headaches. {% endhint %} **Do you already have active projects?** If you already have active clients at the time of registration, the amount corresponding to them is charged right after that first registration. That way, your subscription starts up to date. #### Your subscription dashboard Inside the platform, you find a **link to the Stripe dashboard** (the Customer Portal). It's your self-service hub: anything involving the subscription you handle there, on the spot, without needing to talk to anyone. In the dashboard, you can: * **Review the subscription items** — the subscription is organized by **product and quantity** (adding up everything in use across your projects), and not client by client. For example: if you have two clients, each with two users in the CRM, it appears **CRM x4**; and if only one of them uses the AI Chatbot, it appears **Chatbot x1**. Each line shows the product, the quantity, and the corresponding amount. * **View and update the payment method** — switch cards, update details, or change from card to bank slip (and vice versa). * **Cancel the subscription** — whenever you want, directly in the dashboard.
#### Adding and removing clients and products As your operation grows, you'll add clients, users, and products to the projects. Each of these changes can trigger a charge — and below we explain exactly when that happens. * **New client (new project):** the charge is made automatically **after the 7-day trial period**. * **New user in an already active CRM:** since the project is already running, the charge is **immediate** (there is no new trial period). * **New product for an existing client:** the charge is made automatically **after that product's 7-day trial period**. {% hint style="info" %} **You don't get charged with every click.** To avoid multiple charges in a row, we group all changes made within a **2-hour window** into a single charge. In other words: adjust everything you need—add users, activate products—and in the end only one charge for the total will be generated. {% endhint %} **Why is the extra amount usually prorated? (proportional billing)** When you add something in the middle of the month, it wouldn't make sense to pay for the whole month for something you'll only use for a few days. That's why additional charges are **proportional** (what Stripe calls *pro rata*): you pay only for the portion of the period that remains until your next renewal. Your subscription **renews every month on the date you signed up**. The extra amount for any addition made along the way is calculated based on the days remaining until that next renewal. **An example to make it easier:** Imagine your subscription renews **on the 10th of every month**. * On **the 25th**, you add **1 CRM user**, which costs **R$ 20.00 per month**. * Until the next renewal (the 10th of the following month), there are **about 15 days left** — that is, roughly **half the month**. * So now you only pay **half**: about **R$ 10.00** for that user. * Starting on the next 10th, it is included in your subscription at the **full price of R$ 20.00 per month**. That way, you always pay fairly: only for the actual usage time until the period closes. 😉 #### Deactivating and reactivating a project **When deactivating a project**
Deactivation takes effect **immediately**: access to that project is cut off right away. Since you had already paid for the current period, the amount corresponding to the remaining days **is not lost**: it becomes a **credit** in your account. This credit is stored and is **automatically deducted from your next charges**. **When reactivating a project** Reactivation is also **immediate**: you regain access to the project instantly. Along with that, a **immediate charge** (respecting the same 2-hour window to group changes). On that reactivation, **all products and users in the project are charged again**, proportionally to the time remaining until the next renewal — following the same proportional billing logic explained above. {% hint style="info" %} Do you have any credit accumulated from a previous deactivation? It is normally included in this calculation and helps reduce the reactivation amount. {% 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://bolten.gitbook.io/bolten-docs/en/platform-user-manual/revenue-sharing-billing-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.