# Welcome to DashPay

**DashPay** is a decentralized payment system designed for the realities of a machine-native, privacy-focused, and intermittently connected world. It enables secure, verifiable, and private payments across humans, autonomous agents, and devices — even in environments without internet access or conventional infrastructure.

DashPay introduces a new model for digital value exchange:

* No accounts, apps, or public wallet addresses
* No need for constant connectivity or centralized intermediaries
* No personal data exposed or stored
* Just cryptographically verified value, exchanged peer-to-peer

Payments are initiated offline through ephemeral, zero-knowledge proofs and finalized later using the **x402 settlement layer** — a web-native standard for synchronizing payments with on-chain consensus. DashPay’s architecture enables not only user-friendly mobile payments, but also **autonomous transactions** between APIs, bots, and IoT systems.

Where most payment systems are built for websites or wallets, DashPay is built for the **economic edge**:

* Remote regions with low connectivity
* Devices acting on behalf of users or services
* AI agents consuming and paying for compute, data, or access
* Merchants seeking private, instant settlement without exposing customer identity

DashPay is not a protocol or a platform — it’s a foundation for a new type of economic activity: fast, private, programmable payments that exist beyond the browser.


---

# Agent Instructions: 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:

```
GET https://dashpay.gitbook.io/docs/dashpay-documentation/welcome-to-dashpay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
