> For the complete documentation index, see [llms.txt](https://whitepaper.vozdexai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.vozdexai.com/3.-introducing-vozdex-ai/3.2-private-x402-payments.md).

# 3.2 Private x402 Payments

Peer-to-peer payments often require users to manually exchange wallet addresses, verify destination accounts, and manage transaction parameters across different applications.

Vozdex AI integrates conversational x402 payment flows that simplify this process while preserving cryptographic security.

Instead of copying addresses or manually constructing transfers, users simply describe the payment.

The AI execution engine:

●        Resolves recipient information

●        Validates payment parameters

●        Constructs transaction payloads

●        Performs execution checks

●        Presents a verifiable payment summary

Every transfer remains non-custodial and requires wallet signature prior to execution.

The result is a payment experience that combines conversational simplicity with blockchain-level verifiability.


---

# 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://whitepaper.vozdexai.com/3.-introducing-vozdex-ai/3.2-private-x402-payments.md?ask=<question>&goal=<endgoal>
```

`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.