> 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/security/payment-security.md).

# Payment Security

Payment security is important for every ZXAI purchase.

Users should only use the official Zerax AI dashboard for Wallet Connect Buy and Manual Pay.

{% hint style="danger" %}
Never send funds to addresses shared through private messages, fake support accounts or unofficial links.
{% endhint %}

***

### Safe Purchase Methods

| Method                 | Security Point                                           |
| ---------------------- | -------------------------------------------------------- |
| **Wallet Connect Buy** | Confirm transactions only from the official dashboard.   |
| **Manual Pay**         | Copy payment addresses only from the official dashboard. |

***

### Before Paying

Always check:

* Website URL
* Network
* Payment amount
* Payment address
* Wallet confirmation details
* Transaction hash

***

### Manual Pay Safety

For Manual Pay, make sure:

* You selected the correct coin
* You used the correct network
* You sent the correct amount
* You copied the official payment address
* You saved the transaction hash

{% hint style="warning" %}
Wrong network or wrong address may cause permanent loss.
{% endhint %}

***

### Summary

Use only official Zerax AI payment flows.

If something looks suspicious, do not send funds.


---

# 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/security/payment-security.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.
