> 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/how-sweepay-works.md). # How SweePay Works SweePay operates as a **crypto-native payment infrastructure** that connects user actions with transaction execution across both blockchain systems and traditional payment networks. The system is designed to create a seamless flow between user intent, asset movement, and final settlement. ### **User Interaction Layer** The process begins with a user-initiated action, such as: * Making a payment * Sending funds to another user * Using a card for a physical transaction Each action is translated into a structured request within the SweePay system. ### **Transaction Processing** Once initiated, the request is processed through SweePay’s transaction logic: * The system validates transaction parameters * The required digital assets are prepared for execution * The transaction is routed through the appropriate channel For digital payments, transactions are executed via blockchain-compatible mechanisms.\ For physical card usage, transactions are processed through integrated payment networks such as Mastercard and Visa. ### **Execution & Settlement** After processing, the transaction is executed and finalized: * Blockchain transactions are confirmed on-chain * Card-based transactions are settled through payment networks * The user receives confirmation of the completed action This ensures that all interactions result in a clear and verifiable outcome. ### **Unified Asset Flow** SweePay maintains a unified structure for asset movement: * Users interact with their assets through a single interface * Different payment methods are abstracted into a consistent experience * Asset usage remains seamless across digital and real-world interactions This allows users to move between different transaction types without friction. ### **Integration with Sweep Ecosystem** SweePay is designed to operate in alignment with the Sweep ecosystem, enabling consistent financial interactions across different system components. * Payment interactions follow a standardized structure * Asset usage remains consistent across different interaction types * Financial flows are processed through a unified logic This ensures a cohesive experience where users interact with a structured financial framework regardless of the specific system they engage with. ### **System Design Principles** SweePay is built around a set of core operational principles: * **Automation** — transactions are executed without manual intervention * **Consistency** — all interactions follow the same processing logic * **Transparency** — transaction outcomes are observable and verifiable * **Efficiency** — processes are optimized for speed and usability --- # 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/how-sweepay-works.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.