> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/transactions.md).

# Transactions

The **Transactions** tab provides a detailed record of all purchase and return transactions made by the member. This view helps you track the member’s economic activity, verify values used in campaigns or achievements, and resolve potential discrepancies.

<figure><img src="https://content.gitbook.com/content/Z4Fuoa1PTF0DrNTgjzJu/blobs/xhk8QLTMSm03i0ziMqkR/image.png" alt=""><figcaption></figcaption></figure>

***

### Key elements

* **Transaction list**\
  Each record includes:
  * **Document number**
  * **Document type** (**Purchase** or **Return**)
  * **Document date**
  * **Transaction gross value** and
  * **Channel** (if provided)
  * **Points earned**

***

From the actions menu, you can **view details** of each transaction.

* **Linked data**\
  Transactions may also display:
  * **Assigned units** – loyalty points or cashback added as part of the transaction.
  * **Campaign triggers** – campaigns initiated by the transaction.
* **Returns**\
  Returned transactions are displayed separately and treated as independent records.
  * Campaign rewards earned from purchases are **not linked** to returns.
  * Units can be deducted when conditions are met, but technically, each return acts as a separate campaign trigger.

***

To find out more about the transactions module, please refer to this section of the User Guide:

{% content-ref url="/pages/-MYHFAw70zZruMhxcxC7" %}
[Transactions](/implementation-guide/members-and-activity/transactions.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/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 `build a script that syncs our docs to a CMS` 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.