> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/billing.md). # Billing & Plans Manage your Mailtrap subscription, billing, and account settings Manage your Mailtrap subscription, understand pricing plans, and handle billing-related tasks. Find information about payment methods, invoices, and special programs. ## Billing Management


Billing Setup	Complete guide to setting up your billing information, payment methods, and subscription management.	Billing Setup
Payment Issues	Troubleshoot and resolve common payment problems including failed charges, expired cards, and payment disputes.	Payment Issues
Payment and Billing FAQs	Quick answers to frequently asked questions about billing, payments, plans, and pricing.	Payment and Billing FAQs

## Special Programs


Non-Profit and Open-Source	Learn about special pricing and support for non-profit organizations and open-source projects.	Non-Profit and Open-Source

## Account Status


Suspensions and Bans	Understand account suspension policies, common reasons for suspension, and how to resolve account issues.	Suspensions and Bans

--- # 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://docs.mailtrap.io/account-and-organization/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.