> 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/merchants/merchant-dashboard/transactions.md).

# Transactions

The **Transactions** screen lists all your transactions, newest first.

1. In the menu, click **Transactions**.
2. To find a transaction, type in the **Search** box or use the **Filters**: Start Date, End Date, Currency, Type, Location, Device, Provider, Payment Method, Status and Source Type.
3. To clear all filters, click **Reset Filters**. To reload the list, click the refresh icon.
4. To download the list, click **Export** and choose an option.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FIzyHYzkCRUnEEmzi0yei%2Fm-transactions.png?alt=media" alt="Transactions: Filters, Export and an open row"><figcaption><p>Transactions: Filters, Export and an open row</p></figcaption></figure>

Each row shows the Created Date, Payment Date, Amount, Type (for example Payment, Authorize or Tokenize), Status (for example Approved, Pending, Time-Out or Canceled), Provider, Payment Method, Location, Device \ Type and Reason.

**See the details of a transaction**

1. Click the arrow at the start of a row. The row opens and shows the Transaction Number (with a copy icon), Confirmation, Point Of Sale, Installments Limit and the payments made for the transaction: Status, Date & Time, Type, Amount, Card Type, 4 Digits, Provider, Payment Method, Provider ID, SensePass ID and Authorization Number.
2. To open the full details, click the **More details** icon in the open row. The details page has these parts:

| Part                    | What it shows                                                                                                                 |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Summary and Transaction | Date, Timeout At, Source Type, Type, Payment Commit, Status, Transaction Number, Business, Location, Device and Point Of Sale |
| Payment                 | Amount, Confirmation, Installments Limit, Provider and the software that sent the transaction                                 |
| Payments                | Each payment and refund for the transaction                                                                                   |
| Products                | The products in the transaction, with quantity, amount, discount, VAT and total                                               |
| Timeline                | Each step of the transaction with its time, for example New Transaction and Payment Committed                                 |

The details page also has **Send Reminder** and **Cancel** for a pending payment request, and **Refund** for an approved payment. To go back to the list, click the back arrow.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FY0mErvC1MNVRllbO1CzS%2Fm-tx-details.png?alt=media" alt="Transaction details (pending payment request)"><figcaption><p>Transaction details (pending payment request)</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/merchants/merchant-dashboard/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.
