> 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/purchased-tokens.md).

# Purchased Tokens

The Purchased Tokens section shows the ZXAI amount linked to your presale activity.

This area helps users track how much ZXAI they have purchased or received through approved presale participation.

{% hint style="info" %}
Purchased token amounts may come from Wallet Connect Buy or approved Manual Pay records.
{% endhint %}

***

### What You Can See

| Item                 | Meaning                                     |
| -------------------- | ------------------------------------------- |
| **Purchased ZXAI**   | Total ZXAI linked to completed purchases.   |
| **Payment Method**   | Wallet Connect Buy or Manual Pay.           |
| **Status**           | Pending, Completed, Rejected or Failed.     |
| **Transaction Hash** | Blockchain transaction proof, if available. |
| **Date**             | When the purchase or request was created.   |

***

### Wallet Connect Purchases

Wallet Connect purchases are processed through smart contracts.

After confirmation, the purchase may appear in your dashboard history.

{% hint style="success" %}
Wallet Connect Buy is confirmed through the blockchain.
{% endhint %}

***

### Manual Pay Purchases

Manual Pay purchases appear after you submit payment details.

They may stay as **Pending** until reviewed.

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

***

### Important Note

If your purchase does not appear immediately, wait for confirmation or review.

For Manual Pay, make sure your transaction hash and payment details are correct.

{% hint style="warning" %}
Incorrect Manual Pay details may delay or reject your purchase.
{% 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/purchased-tokens.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.
