> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/subscription-and-billing/paychat/accept-order/reports-and-transaction.md).
# Reports & Transaction
## View **Transaction List**
The **Transaction List** page allows merchants to view, monitor, and manage all customer orders generated from a specific Accept Order event.\
Merchants can track order details, payment status, export transaction data, and access a unique event link or QR code for customer payments.
Follow these steps to view all transactions from an Accept Order event:
1. **Open the DOKU Dashboard**\
Log in to your merchant account through the DOKU Dashboard.
2. **Go to the Accept Order Menu**\
On the left sidebar, navigate to **Accept Payments** → **PayChat** → **Accept Order**.
3. **Select the Event You Want to View**\
From the event list, click on the event you want to review.
4. **Access the Transaction List**\
After opening the event, you will see the **Transaction List** page displayed as shown above.
***
## **Transaction Details**
### **1. Event Information**
This section displays the main details of the selected event.
| Field | Description |
| ---------------- | ---------------------------------------------------------------------------------- |
| **Event Name** | Name of the event created by the merchant. |
| **Event Code** | Unique code automatically generated for the event. |
| **Event Type** | Type of Accept Order event (e.g., Custom Purchase). |
| **Price Set by** | Indicates who sets the price (Merchant). |
| **Price** | Price for the purchase (if applicable). |
| **Inquiry URL** | URL used by customers to access the event. |
| **Status** | Current event status: *Ongoing*, *Upcoming*, *Completed*, *Canceled*, or *Closed*. |
| **Update Event** | Button that allows the merchant to modify the event details. |
***
### **2. Event Summary**
This card shows a recap of all transactions in the event.
| Field | Description |
| --------------------------- | ------------------------------------------------ |
| **Total Transaction Order** | Total number of orders created under this event. |
| **Total Amount** | Total nominal value from all orders combined. |
Merchants may expand or collapse this section to view detailed transaction summaries.
***
### **3. Event QR Code & Link**
This section provides:
* A **unique QR Code** for the event.
* A **unique event URL** that customers can access to make a payment.
Customers may scan the QR code using their smartphones to directly initiate a payment transaction.
***
### **4. Order Information**
This section displays and manages all customer orders.
#### **Search Filters**
| Field | Description |
| ----------------- | -------------------------------------------------------------------- |
| **Customer Name** | Search orders by the customer’s name. |
| **Date Range** | Filter orders by date range. |
| **Status** | Filter based on: *Not Yet Paid*, *Paid*, *Waiting for Payment*, etc. |
| **Reset** | Clear all filters. |
| **Search** | Apply the selected filters. |
#### **Bulk Actions & Export**
* **Export to Excel** – Download all order details in Excel format.
* **Select All** – Select all orders in the list.
* **Bulk Action** – Perform bulk actions on selected orders (if applicable).
***
### **5. Order List Table**
This table displays all transaction details from customers.
| Column | Description |
| -------------------------------- | ------------------------------------------------------ |
| **Order ID** | Unique ID for each order. |
| **Order Date** | Date and time when the order was created. |
| **Phone Number** | Customer’s phone number. |
| **Customer Name** | Name of the customer. |
| **Invoice Number** | Unique invoice ID. |
| **Custom FIeld (Green Section)** | Customer input field (if event uses custom input). |
| **Product Title** | Product name or event item title. |
| **Product Description** | Description of the selected product (if any). |
| **Payment Date** | Payment completion date (if paid). |
| **Payment Method** | Method used by the customer to pay. |
| **Quantity** | Total quantity ordered. |
| **Process Status** | Order status (e.g., Waiting for Payment). |
| **Action** | Actions available for each order (e.g., view details). |
Merchants can adjust how many rows are displayed per page (e.g., 10 items per page).
***
### **Notes**
* Click the values in each column to sort the transactions.
* Payment status tags (e.g., *Not yet paid*, *Waiting for Payment*) help merchants quickly identify pending orders.
---
# 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://docs.doku.com/subscription-and-billing/paychat/accept-order/reports-and-transaction.md?ask=&goal=
```
`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.