> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/plans-billing/billing-and-payments.md). # Billing & Payments **Bill your customers and get paid.** Create invoices, collect payment in person or online, and manage everything that happens after you hit send — from resending and refunds to receipts. **What you'll find here** * **Invoicing Essentials** — build an invoice and choose how to collect: in person vs. send * **Managing Your Invoices** — statuses, and how to edit, resend, void, or request payment * **Refunds & Voiding an Invoice** — return money or cancel an invoice, done right * **Getting Paid Online** — what your customer sees on the payment page (card, bank, tips, receipt) * *Coming soon:* Setting Up BluePay, Invoice Settings & Templates, Tax, Recurring & Subscriptions, QuickBooks > 💡 **Key idea:** An **invoice** is the bill; a **payment link** lets customers pay by card or bank from their phone. To accept card payments, set up **BluePay** first. --- # 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.bluepro.ai/plans-billing/billing-and-payments.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.