> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/functional-specification/add_reference.md).
# Merchant Reference and Customer Reference
Allows a merchant to optionally add a \_merchant [reference\_](#system-message-1), a \_customer [reference\_](#system-message-2), or both to each transaction. Either reference string can be used as a search criteria when searching the transaction history on the terminal.
| Merchant Reference | Customer Reference | Merchant and Customer Reference |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|  |  |  |
## Advanced Search option
{% columns %}
{% column width="33%" %}
{% endcolumn %}
{% column %}
Displays list of transactions which match the searched merchant or customer reference.
\*\*Description\*\*
All transactions that match the merchant or customer reference partially or in full, regardless of case when searching for any reference through the Advanced Search option.
\
\*\*Merchant action\*\*
Enter a merchant or customer reference to search.
{% endcolumn %}
{% endcolumns %}
***
## Order History screen
The order history screen showing a transaction with merchant reference.
{% columns %}
{% column width="33%" %}
{% endcolumn %}
{% column %}
The merchant reference: “\[cofee\@17thstreet]\(mailto:cofee%4017thstreet)”
{% endcolumn %}
{% endcolumns %}
\---
### Configuration Parameters
* `Merchant.EnableReference` - Enables addition of the merchant reference (1: Enabled , 0: Disabled)
* `Merchant.EnableCustomerReference` - Enables the addition of the customer reference (1: Enabled , 0: Disabled)
* `Merchant.ReferencePromptMaxLength` - Maximum allowed length of merchant or customer reference values
---
# 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.verifone.com/functional-specification/add_reference.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.