# Billing & Payments We like to keep things simple and transparent. Here’s everything you need to know about how billing works at PluginPulse. ### Billing Cycle PluginPulse uses **monthly billing based on your signup date**.\ Your billing period begins the day you subscribe and renews on the same day each month (e.g. if you signed up on the 12th, your billing cycle runs from the 12th of one month to the 11th of the next). ### What You’re Charged For PluginPulse pricing is based on two parts: **1. Base Plan** * $24/month * Includes access to PluginPulse and 1 plugin * Billed monthly, at the start of the cycle. **2. Additional Plugins** * If you add more plugins, we charge a small fee per plugin based on how many you connected during your billing cycle. * These fees are billed monthly, at the start of the next cycle. * Check the [Pricing page ](https://plugin-pulse.gitbook.io/docs/pricing)for details on per-plugin rates. ### How We Count Plugins We count the **maximum number of unique Plugin IDs** you had connected to your PluginPulse dashboard at any point during your 30-day billing period.\ For example: if you connected 2 plugins, removed 1, and added a different one later - that’s 3 unique plugins in total, so you’ll be billed for 2 extra plugins on top of your base plan. ### Payments * All payments are securely processed via Stripe. * You’ll receive an invoice by email each month for your records. ### Cancellations * You can **cancel** at any time during the month, but to avoid charges for the next month, make sure to cancel at least **14 days before** the end of the current billing cycle. ### Need Help? If anything’s unclear or you have questions about your charges, feel free to reach out at - we’re happy to help. --- # Agent Instructions: 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://plugin-pulse.gitbook.io/docs/pricing-and-payments/billing-and-payments.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.