> For the complete documentation index, see [llms.txt](https://docs.zeraxai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeraxai.com/dashboard/transaction-history.md).

# Transaction History

The Transaction History section helps users track their ZXAI purchase and payment activity.

It may include Wallet Connect Buy transactions, Manual Pay submissions and status updates.

{% hint style="info" %}
Use this section to follow the status of your purchases and payment records.
{% endhint %}

***

### What You Can Track

| Item                 | Description                                  |
| -------------------- | -------------------------------------------- |
| **Payment Method**   | Wallet Connect Buy or Manual Pay.            |
| **Payment Amount**   | The amount paid by the user.                 |
| **Token Amount**     | The ZXAI amount linked to the purchase.      |
| **Transaction Hash** | Blockchain transaction proof, if available.  |
| **Status**           | Pending, Completed, Rejected or Failed.      |
| **Date**             | When the transaction was created or updated. |

***

### Wallet Connect Transactions

Wallet Connect transactions are confirmed on-chain.

If the transaction is successful, it may appear as completed after blockchain confirmation.

{% hint style="success" %}
Wallet Connect purchases can also be checked through the blockchain transaction hash.
{% endhint %}

***

### Manual Pay Transactions

Manual Pay transactions require review.

A submitted Manual Pay record may stay pending until the payment details are verified.

| Status        | Meaning                        |
| ------------- | ------------------------------ |
| **Pending**   | Waiting for review.            |
| **Completed** | Payment approved.              |
| **Rejected**  | Payment could not be verified. |

***

### Important Notes

* Always keep your transaction hash.
* Make sure the payment network is correct.
* Manual Pay approvals may take time.
* Rejected payments may require checking the submitted details.

{% hint style="warning" %}
Incorrect payment details may delay or reject Manual Pay transactions.
{% endhint %}


---

# 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.zeraxai.com/dashboard/transaction-history.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.
