> 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/email-and-communication/email-settings/payment-received-emails.md).

# Payment Emails

Customize automatic emails for received, processing, failed, and refunded payments.

PaintScout automatically emails customers as their payment status changes. Customize each template in Account Settings.

## Available payment emails

* **Payment Received** — Sends to the customer when a payment is successfully applied to an estimate or invoice. Use this email to thank them or add helpful next steps.
* **ACH Processing** — Sends when an ACH payment is processing. Canadian accounts may see EFT instead. This can be helpful to inform the customer of the pending status of a transfer.
* **Payment Failed** — Sends to the customer when a payment processor declines a card, ACH, or EFT payment. This email can request that users try again or contact you directly.
* **Payment Refunded** — Sends when a payment is refunded. Use this email to inform the customer that a payment has been fully or partially refunded.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2FyTGvApHIvI0Sbn3mmQif%2FScreenshot%202026-07-15%20at%204.13.35%E2%80%AFPM.png?alt=media&amp;token=e1403d7d-95b3-4104-8df7-f99eff96187a" alt="" width="563"><figcaption></figcaption></figure>

## Customize payment emails

1. Select the person icon in the upper-right corner.
2. Go to **Account Settings** → **Communications** → **Email Templates**.
3. In **Emails Sent Automatically**, select the payment email you want to edit.
4. Update the subject line and message, then save your changes.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2FfI84zsLnGwLHTVhL3KSQ%2FScreenshot%202026-07-15%20at%204.06.50%E2%80%AFPM.png?alt=media&amp;token=81bac69a-384b-4695-a73e-9cf40f83d1fb" alt="Account Settings navigation to Communications, Email Templates, and Emails Sent Automatically"><figcaption></figcaption></figure>

The following video shows how to customize the **Payment Received** email. Use the same steps for the other payment email templates.

{% embed url="<https://www.youtube.com/watch?v=S69zi404VSI>" %}

&#x20;&#x20;

## Related articles

* [Payments Table Overview](/support/invoicing-and-payments/invoices/payments-table-overview.md) — Track and manage payment statuses.
* [Automatic Emails](/support/email-and-communication/email-settings/automatic-emails.md) — Manage other automated customer emails.

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Automatic Thank You Emails</strong></td><td>Configure automatic thank you emails to be sent when customers accept or decline estimates, with customizable subject lines and body content.</td><td><a href="/support/email-and-communication/email-settings/automatic-thank-you-emails.md">Automatic Thank You Emails</a></td></tr><tr><td><strong>Automatic Emails</strong></td><td>Customize automatic email templates that send when estimates are accepted, declined, payments received, or events are booked or cancelled.</td><td><a href="/support/email-and-communication/email-settings/automatic-emails.md">Automatic Emails</a></td></tr></tbody></table>


---

# 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/email-and-communication/email-settings/payment-received-emails.md?ask=<question>&goal=<user_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.
