> 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 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.