> 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/how-to-mark-a-payment-request-as-paid.md).

# Mark a Payment Request as Successful

In PaintScout, online payments update automatically. For cash, check, or other offline methods, you can mark a payment request as **Successful** manually.

## How to mark a payment request as successful

1. Click the three dots to the right of the payment request.

   <figure><img src="/files/ODw8qJ1TDrrNoxIN9J78" alt="Screenshot showing the three-dot menu button on a pending payment request"><figcaption></figcaption></figure>
2. Choose **Mark as Successful**. Some older screens may show **Mark as Paid**.

   <figure><img src="/files/HuKXEla7ajaDpwsnWIkG" alt="Screenshot showing the Mark as Paid option in the payment request context menu"><figcaption></figcaption></figure>
3. Choose whether to take a card payment on-site or record an offline payment such as cash, check, or e-transfer.

   <figure><img src="/files/dKNMWacLO2AMvJeWo70A" alt="Screenshot showing the payment method options to process a credit card or record an alternative payment"><figcaption></figcaption></figure>
4. Once the payment is logged, the request is marked as **Successful**. Some older screens may show **Paid**.

   <figure><img src="/files/Urzq08aov8K6OndrbsNi" alt="Screenshot showing the payment request updated to Paid status"><figcaption></figcaption></figure>

## Related articles

* [Manually Add a Payment](/support/invoicing-and-payments/recording-payments/how-to-manually-add-a-payment.md) — Record cash, check, or transfer payments on invoices
* [How Customers Pay](/support/invoicing-and-payments/recording-payments/how-customers-make-a-payment.md) — See the customer payment flow from email to checkout


---

# 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/how-to-mark-a-payment-request-as-paid.md?ask=<question>&goal=<endgoal>
```

`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.