> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/invoicing-and-payments/payment-requests.md). # Payment Requests Create and manage payment requests for deposits and progress payments. Payment requests let you ask for deposits, progress payments, or the remaining balance on an invoice. Send requests by email or text, let customers pay online when enabled, and track each request from **Requested** to **Successful**. ## In This Section * [Create a Payment Request](/support/invoicing-and-payments/payment-requests/how-to-create-a-payment-request.md) — Send deposit, progress, or full-balance requests and choose payment settings for that invoice * [Resolving Payment Requests](/support/invoicing-and-payments/payment-requests/how-to-mark-a-payment-request-as-paid.md) — Process online payment requests or record payments manually * [Delete a Payment Request](/support/invoicing-and-payments/payment-requests/how-to-delete-a-payment-request.md) — Remove the request and customer payment banner while keeping the invoice available * [Customer Payment Experience](/support/invoicing-and-payments/payment-requests/how-customers-make-a-payment.md) — See how customers open and pay a request --- # 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://help.paintscout.com/support/invoicing-and-payments/payment-requests.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.