Student payments belong to the studio relationship. A membership purchase, workshop booking, pass, or drop-in is not the same thing as Sangha's SaaS billing, a dana contribution, or a work-study exchange. When those flows are blurred, owners lose clarity about what was collected and why.
Sangha is built to support Stripe Connect for student-to-studio payments. Each studio can have its own connected payment setup, while Sangha's platform billing remains a separate concern. That keeps the financial roles easier to understand.
Clean payment architecture matters for reporting, reconciliation, and trust. Owners should be able to see paid bookings, pass purchases, workshop revenue, platform costs, and community exchange without decoding one giant mixed stream. The more specific the flow, the easier it is to explain.
Stripe Connect readiness also fits Sangha's broader integration posture. Stripe should do payment infrastructure well, while Sangha handles the studio-specific meaning around offerings, access, policies, teacher pay, and community exchange.
The result is less financial confusion. Student-to-studio money can move through the right rails, SaaS billing can remain separate, and dana or service can keep its own meaning instead of being forced into the paid revenue ledger.
