> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/transactions-overview/view-member-transactions.md).

# How to View a Member's Transactions

### Before you begin (Prerequisites)

* **Permissions**: Administrator, Supervisor, Support, or Waitstaff. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).

### Instructions

**From the CRM member profile (recommended for one specific member):**

1. Navigate to [**CRM > View People**](https://control.peoplevine.com/customers) and open the member's profile.
2. Scroll to the **TRANSACTIONS** section on the profile.
3. Click **VIEW ALL TRANSACTIONS** to open the View Transactions dashboard pre-filtered to this customer.

**From the Transactions page (when grouping or scanning across people):**

1. Navigate to [**SELL > View Transactions**](https://control.peoplevine.com/transactions).

> **Note (Pro Dash):** Navigate to **SELL > Transactions > View Transactions**.

2. Use the **Sort by** dropdown and select **Person** to group results by customer.
3. To filter to one specific member, use the CRM profile path above — the Transactions page does not have a member search filter.

### About the CRM profile Transactions section

On a member's CRM profile, the **TRANSACTIONS** section shows the 10 most recent transactions of the member's total to-date. Two buttons sit at the top of the section:

* **VIEW ALL TRANSACTIONS** — opens the View Transactions dashboard pre-filtered to this customer number, where you can apply any of the standard filters (date range, payment type, status, etc.). See: [How to Navigate the View Transactions Dashboard](/products/control-panel-overview/transactions-overview/navigate-transactions-dashboard.md).
* **CHARGE PERSON** — start a new charge against the member.

Columns in the section:

| Column          | What It Shows                                                                                         |
| --------------- | ----------------------------------------------------------------------------------------------------- |
| **Charged**     | Date and time of the charge, plus the payment method used                                             |
| **Amount**      | Charge amount                                                                                         |
| **Payment For** | Transaction number, linked order number (if any), and the type (e.g., dues, event, dining, gift card) |
| **Status**      | Status badge — `processed`, `invoiced`, `invoice payment`, `Invoice Paid`, `refunded`                 |
| **View**        | Blue list icon — opens the transaction detail page                                                    |

Some rows show a green **TAKE PAYMENT** button (for invoiced transactions). Stripe payment IDs (`pi_3T...`) appear inline on Peoplevine-processed rows.

For details on filters, statistics, status tags, and date field behaviour available across the dashboard, see [How to Navigate the View Transactions Dashboard](/products/control-panel-overview/transactions-overview/navigate-transactions-dashboard.md).

### What Happens Next

* **Next step**: [How to See the Payment Method Used on a Transaction](/products/control-panel-overview/transactions-overview/view-transaction-payment-method.md)

*Last updated: 2026-05-24*


---

# 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://help.peoplevine.com/products/control-panel-overview/transactions-overview/view-member-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.