> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/subscriptions/your-subscription/refund.md). # Refund Learn how to request a refund in the BTWB app. This step-by-step guide walks you through contacting support, providing the right details, and ensuring your refund is processed quickly. ### Overview If you’ve been incorrectly charged or need to request a refund for another reason, the BTWB support team can help. To make the process smooth, follow the steps below and include all the necessary details. *** ### Step 1: Contact BTWB Support * Open your email app. * Send a message to ****. *** ### Step 2: Provide Detailed Information In your email, be sure to include: * A **clear explanation** of why you’re requesting a refund. * The **specific subscription or payment** involved. * Your **account name and email address** (the one linked to BTWB). * Any **supporting screenshots** (such as billing records). *** ### Step 3: Wait for Confirmation * The support team will review your request within **1–3 business days**. * If approved, a **refund will be issued** back to your original payment method. * Depending on your bank, it may take **5–10 business days** for the funds to appear. *** ### Tips & Notes * **Double-check pending charges**: Sometimes what looks like a charge is a temporary authorization that clears automatically. * **Use the correct account email**: This ensures the support team can quickly locate your records. * **Bank follow-up**: If you don’t see the refund after 10 business days, contact your bank to confirm the reversal. *** ✅ By following these steps, BTWB users can quickly and efficiently request refunds while minimizing delays. *** --- # 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://btwb.gitbook.io/btwb/subscriptions/your-subscription/refund.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.