> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/payments/viewing-transactions.md).

# Viewing transactions

The Transactions page gives you a complete view of every payment processed through Vendor Space. Use it to track revenue, verify vendor payments, and export records for your bookkeeping.

***

## How to access transactions

Click **Transactions** in the sidebar to open the full transaction list.

***

## What each transaction shows

Every transaction record includes:

| Field               | Description                                     |
| ------------------- | ----------------------------------------------- |
| **Company name**    | The vendor's business name                      |
| **Event**           | The event the payment is associated with        |
| **Items purchased** | The booth type and any add-on products included |
| **Total amount**    | The full amount the vendor paid                 |
| **Status**          | The current state of the payment                |
| **Date**            | When the transaction was created                |

***

## Transaction statuses

| Status      | Meaning                                                   |
| ----------- | --------------------------------------------------------- |
| **Pending** | Payment has been initiated but not yet completed          |
| **Paid**    | Payment was successfully processed                        |
| **Failed**  | Payment did not go through (card declined, expired, etc.) |

> **Tip:** If a transaction shows "Failed," reach out to the vendor and generate a new payment link so they can try again.

***

## Filtering and searching

Use the filter bar at the top of the Transactions page to narrow down your results:

* **Event** -- Show transactions for a specific event only.
* **Status** -- Filter by Pending, Paid, or Failed.
* **Date range** -- View transactions within a specific time window.

You can combine filters to get exactly the view you need. For example, filter by a single event and "Paid" status to see all confirmed revenue for that event.

***

## Exporting transactions

To download your transaction data:

1. Apply any filters you want (optional).
2. Click the **Export CSV** button.
3. A CSV file downloads with all visible transactions.

The exported file includes all fields shown in the table and can be opened in Excel, Google Sheets, or any spreadsheet application.

> **Tip:** Export filtered results before an event wraps up to have a clean record of all vendor payments for that event. This is especially helpful for accounting and post-event reporting.

***

## Disputes Tab

The Transactions page also includes a **Disputes** tab where you can monitor any chargebacks filed by vendors. See [Disputes and chargebacks](/docs/payments/disputes.md) for full details on how dispute tracking works.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/payments/viewing-transactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.