> For the complete documentation index, see [llms.txt](https://dashpay.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dashpay.gitbook.io/docs/dashpay-documentation/why-dashpay-exists.md). # Why DashPay Exists Today’s payment systems — both traditional and Web3 — rely heavily on connectivity, infrastructure, and identity. They assume that users are online, that addresses can be shared, and that every transaction must pass through either a centralized processor or a public ledger in real time. But the world is more fragmented than that. Payments happen at the edges of networks.\ In places without signal.\ Between machines without dashboards.\ Between humans who don’t want to be tracked.\ In systems where agents — not people — hold the wallet. DashPay exists to solve for this future. It enables **private, peer-to-peer, and offline-first payments** that finalize securely without requiring users to reveal who they are, where they are, or even that they paid. Transactions can be initiated between devices, agents, or individuals using **ephemeral zero-knowledge proofs**, and confirmed later via the **x402 payment sync layer** — a standard for deferred, on-chain finality. DashPay isn’t a wallet. It’s not an app.\ It’s an answer to a simple question: > *“What if payments could happen without the internet, without identity, and without exposure — but still with trust?”* We believe they can — and that they must — if Web3 is going to reach beyond screens and into the real world. --- # 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://dashpay.gitbook.io/docs/dashpay-documentation/why-dashpay-exists.md?ask=&goal= ``` `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.