> 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/support-uk/ux700/how-tos/how-to-search-transactions.md).

# How To Search Transactions

Search for transactions using simple or advanced search on the UX700 terminal.

{% hint style="info" %}
**Use this when** you need to find a specific transaction on a UX700 terminal using the Order History search.
{% endhint %}

This page explains how to use simple search and advanced search to find transactions.

## Use simple search

{% stepper %}
{% step %}

### Enter digits to search

Enter 4 digits to search for transactions where the last 4 digits of the card number match. Enter 5 or more digits to search for an Order ID or Transaction ID that contains the digits entered.
{% endstep %}
{% endstepper %}

## Use advanced search

{% stepper %}
{% step %}

### Open Advanced Search

Press the **Advanced Search** button in the Order History List Search view.
{% endstep %}

{% step %}

### Enter search criteria

Enter one or more of the following search options. When multiple options are entered, the result matches all the specified criteria:

1. **Exact amount** — finds orders with an order amount exactly matching the entered value.
2. **Approximate amount** — finds orders with an order amount within 20% of the entered value.
3. **STAN** — finds transactions with a transaction ID containing the entered sequence.
4. **RRN Number** — finds transactions with an RRN Number containing the entered sequence.
5. **Invoice Number** — finds transactions with an invoice ID containing the entered sequence.
6. **Card Number** — finds transactions with a card number containing the entered sequence.
7. **Date** — finds transactions within the entered date range.
8. **Transaction type** — finds transactions of the selected transaction type.
9. **Only pending offline** — finds pending offline transactions (performed offline, not yet confirmed online).
10. **Declined transactions** — finds declined transactions.
    {% endstep %}

{% step %}

### Clear criteria (if needed)

Press the bin icon to clear a selected search criterion.
{% endstep %}
{% endstepper %}

## Guidelines

* Simple search with 4 digits matches the last 4 digits of the card number; 5 or more digits matches the Order ID or Transaction ID instead.
* Advanced search results must match all the criteria you've entered, not just one.

## FAQ

<details>

<summary>What's the difference between simple and advanced search?</summary>

Simple search matches card number digits, Order ID, or Transaction ID directly. Advanced search lets you combine multiple criteria — amount, STAN, RRN, invoice number, card number, date, transaction type, pending offline, or declined.

</details>

<details>

<summary>How do I clear a search criterion?</summary>

Press the bin icon next to it.

</details>

<details>

<summary>Keywords</summary>

Also called: transaction search, order search, advanced search. Search terms: simple search, advanced search, STAN, RRN, invoice number, UX700.

</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.verifone.com/support-uk/ux700/how-tos/how-to-search-transactions.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.
