> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/usa/applications/payfacto-gift-datacandy/printing/add-personalized-receipt-footer.md).
# Add Personalized Receipt Footer
## Add Personalized Receipt Footer
You can add a personalized message at the bottom of every printed receipt. Your message can contain up to 4 lines with 44 characters (including spaces) per line.
{% hint style="success" %}
TIP: You should prepare your header information on a piece of paper in advance, to ensure that you have the correct number of characters per line.
{% endhint %}
### **To add a personalized message to your printed receipts:**
1. Touch the **Action** button on the main screen. 
2. Touch **Settings**. 
3. Enter the Admin password and touch **OK**.
4. In the **General** section, touch the **Printer Options**.
5. Scroll down to the **Footer** section, toggle **Footer Printing** to **On** (to the right).
6. Touch **Footer Line 1** and enter the text for the merchant name in the text field that appears and touch **OK**.
7. If necessary, repeat step **6** for **Footer Line 2**, **Footer Line 3**, and **Footer Line 4** as required.
8. Touch the **Back** icon to return to the main screen. 
{% hint style="info" %}
NOTE: The header information appears on all printed receipts, the merchant copy as well as the customer copy.
{% endhint %}
---
# 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.payfacto.com/payfacto-knowledge/usa/applications/payfacto-gift-datacandy/printing/add-personalized-receipt-footer.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.