> 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/canada-doc-center/applications/secure-payment/application-securepay-module/securepay-application/transaction-management/search-for-a-transaction.md).

# Search for a Transaction

### Search for a Transaction

You can search for transactions on the terminal to view the details about one or more transactions. If you have multiple terminals operating under the same merchant ID (MID), all transactions from all terminals appear in the list with the most recent transaction at the top of the list. You can search for transactions in the current (open) batch as well as from previous batches.

{% hint style="info" %}
NOTE: Because all of a merchant's transactions processed on all terminals are saved immediately to the server, the list of transactions may be quite long.
{% endhint %}

{% hint style="success" %}
TIP: If you find it difficult to locate a specific transaction from an individual terminal, you may choose to restrict the search function to only display transactions performed on each individual terminal.

To restrict the transaction display to only those processed by the terminal, you must contact PayFacto support to request that your merchant profile displays only transactions processed on individual terminals by activating the **Terminal Only Reports** function. This will restrict transaction searching to individual terminals.
{% endhint %}

#### **To search for a transaction:**

1. From the main screen, touch the **Menu** button.\
   ![Menu button](https://documentation.payfacto.com/SecurePayment/SecurePay/UG/CA-EN/assets/images/SecurePay-table/_MVP/SecureTablePay_HomeScreenMenuHighlight.png)
2. Enter the merchant password and touch **Confirm**.
3. In the **Transaction management** section, touch **Transaction History**.\
   ![Settings menu Transaction history](https://documentation.payfacto.com/SecurePayment/SecurePay/UG/CA-EN/assets/images/Pay/SettingsMenu_TransactionHistory.png)
4. Touch the **Search** button.
5. Enter one or more of the following search criteria:
   * An invoice number in the **Invoice number** field
   * An authorization code in the **Authorization code** field
   * Touch the **Time range** field to select a date range for the desired transaction; touch **Save** to search using the selected date range
6. Touch the **Search** button. The terminal returns any transaction that meets the selected search criteria.
7. Touch the desired transaction to display the details.


---

# 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/canada-doc-center/applications/secure-payment/application-securepay-module/securepay-application/transaction-management/search-for-a-transaction.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.