# Transactions

The Transactions file contains information about transactions associated with members. 

A sample file is provided below:

{% file src="<https://123136216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIv2CyIIYf7vRfuhMKQ6%2Fuploads%2FpzHBuPLr89FOxipaM0V9%2Ftransactions_all_until_2025_09_16.csv?alt=media&token=dc21bab1-e573-497a-a847-a6dbdd246d0d>" %}

**Available Data:**

* **transactionId**: Unique ID for the transaction generated in Open Loyalty
* **memberId**: Unique ID for the member generated in Open Loyalty
* **channelId**: ID of the channel where the transaction occurred
* **channelName**: Name of the channel
* **memberData**: Information about the member who made the transaction
* **items**: List of items purchased in the transaction
* **tenantId**: ID of the tenant where the transaction was created
* **header**: Transaction header information (e.g. document number, document date, purchase location, etc.)
* **assignedToMemberAt**: Time when the transaction was matched with the member
* **matched**: Status indicating whether the transaction has been matched
* **grossValue**: Total gross value of the transaction
* **currency**: Currency used in the transaction
* **pointsEarned**: Number of units earned from the transaction
* **unitsDeducted**: Number of units deducted from the transaction
* **createdAt**: Date when the transaction was created
* **updatedAt**: Date when the transaction was last updated


---

# Agent Instructions: 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:

```
GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/transactions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.