> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/utilities/processed-payment-logs/processed-payment-logs-fields.md).

# Processed Payment Logs Fields

The Processed Payment Logs module displays detailed information of the transactions processed within the system, offering comprehensive tracking and documentation of transactions.

{% hint style="info" %}
To access the Processed Payment Logs, go to *Menu > Utilities > Processed Payment Logs*
{% endhint %}

### Process Payment Logs Fields

<table><thead><tr><th width="223">Field</th><th>Description</th></tr></thead><tbody><tr><td>Customer</td><td>This field shows the name or identifier of the customer associated with the payment transaction.</td></tr><tr><td>Payment Method Type</td><td>Specifies the method used for payment, such as credit card and direct debit.</td></tr><tr><td>Transaction Type</td><td>Defines the nature of the transaction, e.g., sale, refund, or payment received.</td></tr><tr><td>Ref No</td><td>This field displays the unique reference number assigned to the transaction.</td></tr><tr><td>Source Ref No</td><td>This field captures the reference number or identifier associated with the source or origin of the payment, such as an order ID or invoice number.</td></tr><tr><td>Status</td><td>This field shows the status of the payment, such as "Success" or "Failed", indicating whether the payment was processed successfully or not.</td></tr><tr><td>Type</td><td>This field indicates the type of payment ("Payment" or "Refund").</td></tr><tr><td>Platform Status</td><td>This field indicates the status of the payment transaction within the processing platform, such as "Processed", "Paid out" or "Pending customer approval".</td></tr><tr><td>Payment Ref</td><td>This field captured the reference number associated with the payment, such as the credit card number.</td></tr><tr><td>Message</td><td>This field shows any messages or notes related to the transaction, including errors or status updates.</td></tr><tr><td>Create Datetime</td><td>This field indicates the date and time when the transaction was created.</td></tr><tr><td>Created By</td><td>This field indicates the user responsible for creating or initiating the payment transaction record.</td></tr></tbody></table>

### Processed Payment Logs Header Level Icons

* **Refresh:** This allows you to refresh the search results after changing the search criterion.
* **Save:** This option enables you to preserve any updated user interface (UI) settings (for example, if you have hidden or added any columns for viewing), ensuring a personalized and consistent experience during future interactions with the module.
* **Advance Search:** The advance search option enables you to further extend the search criteria. You can delve into a nuanced search by specifying criteria such as Column Name, Operator, and Value, facilitating precise and tailored searches.
* **Columns (Bento Menu):** All the columns available for the module are listed under this icon. You can use this option to hide or add the columns and tailor the module view as per your requirements.
* **Download:** This versatile feature allows users to export and download data in various file formats, providing a summarized overview for quick reference. Options include CSV, TXT, MS-Word, MS-Excel, PDF, and MS-Excel(.xlsx), catering to diverse user preferences and use cases.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xorosoft.com/xoroerp-1/utilities/processed-payment-logs/processed-payment-logs-fields.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 `automate deployments from our CI pipeline` 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.