> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/partners/partner-dashboard/receipts.md).

# Receipts

Receipt settings are set for the merchant and can be overridden per location.

1. Open **Management** > **Receipts** and check the merchant and location at the top of the page.
2. Choose a tab: **Payment Receipt**, **Refund Receipt** or **Email Notification**.
3. The page shows the current source, for example "Merchant defaults", and whether the merchant receipt is enabled.
4. To use different settings for this location, select **Override merchant payment receipt configuration** (or the matching option on the other tabs). The fields become editable once this configuration is enabled.
5. Choose which fields to show and save.

The fields are grouped as: **Header**, **Transaction info**, **Payment methods**, **Billing**, **Products and line items**, **Products totals**, **Summary** and **Footer**. The **Live Preview** on the right shows a sample receipt with the current settings.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2Fz3ZEQH7Ne2c16mQrpoIw%2Fp-receipts.png?alt=media" alt="Receipts page with Live Preview"><figcaption><p>Receipts page with Live Preview</p></figcaption></figure>


---

# 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.sensepass.com/sensepay/partners/partner-dashboard/receipts.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.
