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

# Welcome to Paypad

**Welcome to Paypad**

* **Core Summary:** Paypad is the first financial settlement layer to bring the native x402 protocol to the BSC ecosystem, providing core infrastructure for the autonomous machine economy (AI, automated services).
* **What We Solve:** We eliminate the fundamental barrier preventing "zero-gas, signature-free" payments on BSC, which arises from the technical incompatibility of mainstream stablecoins.
* **Our Core:** Through the proprietary "Bsc 402" architecture and the native token **$PAY**, we enable a truly seamless payment experience on BSC for the first time.
* **Our Goal:** To establish $PAY as the indispensable, universal settlement standard for all value exchange within BSC's automated economy.

Web: [paypad.xyz](https://paypad.xyz)

X: <https://x.com/paypadxyz>


---

# 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://docs.paypad.xyz/overview/welcome-to-paypad.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.