> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/ecosystem-components/sweepay.md). # SweePay ### Overview of SweePay SweePay is a **crypto-native payment system** designed to enable seamless financial interactions across both digital platforms and real-world use cases. Developed within the Sweep ecosystem, SweePay functions as a **unified payment infrastructure**, allowing users to send, receive, and utilize digital assets in a flexible and accessible manner. SweePay combines both **physical and digital payment solutions**, creating a comprehensive financial experience. The system includes: * **Physical card usage** — enabling everyday payments through cards supported by Mastercard and Visa infrastructure * **Digital payments** — allowing users to pay directly with crypto assets * **Transfers** — supporting instant peer-to-peer value exchange Unlike traditional payment systems that rely on centralized control, SweePay is built on a **user-centric and blockchain-compatible architecture**, where transactions are executed through secure and transparent systems. This structure transforms digital assets from passive holdings into **actively usable financial tools**. Users can engage with their assets across multiple contexts through a single, unified system. By reducing reliance on intermediaries and aligning with blockchain infrastructure, SweePay simplifies transaction processes while increasing transparency and accessibility. The result is a more efficient and globally adaptable payment experience. In essence, SweePay provides a financial layer where crypto assets can be seamlessly integrated into everyday usage, bridging the gap between digital value and real-world transactions. --- # 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.sweep.finance/ecosystem-components/sweepay.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.