> 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/non-custodial-payment-architecture.md).

# Non-Custodial Payment Architecture

SweePay is designed around a **non-custodial architecture**, ensuring that users retain control over their digital assets at all times. The system does not take ownership of user funds, but instead facilitates transactions through user-authorized interactions.

### **User Ownership of Assets**

Within SweePay, asset control remains entirely with the user:

* Funds are held in user-controlled wallets
* Private keys are never accessed or stored by the system
* Transactions require user authorization

This structure eliminates reliance on centralized custody and reduces counterparty risk.

### **Transaction Authorization**

All transactions are initiated and approved by the user:

* Payments and transfers require explicit user consent
* Authorization is executed through wallet-based signing or approved payment methods
* No transaction can be executed without user confirmation

This ensures that users maintain full control over all financial actions.

### **Separation of Execution and Custody**

SweePay separates transaction execution from asset custody:

* The system processes and routes transactions
* Users retain control of their assets throughout the process
* No centralized entity holds or manages user balances

This design enhances both security and transparency.

### **Risk Reduction**

By eliminating centralized fund storage, SweePay reduces key risks associated with traditional systems:

* No single point of failure for user funds
* Lower exposure to custodial breaches
* Reduced dependency on platform-level trust

### **Transparent Interaction Model**

All interactions follow predefined and observable logic:

* Transactions are executed through consistent system rules
* Outcomes are not subject to manual intervention
* Activity can be verified through system records and blockchain data where applicable