Payments: who gets paid and who buys
What the seller of a course sees, what the buyer sees, and who manages an academy's payments.
Tested on 28/09/2026 · version 5d7d821a1e
Every payment has two sides: who pays and who gets paid. Transactions, subscriptions, receipts and invoices are seen only by these two sides, each from its own context (personal profile or academy).
Who manages an academy's payments
| Role in the academy | The academy's payments |
|---|---|
| Owner | sees and manages everything: transactions, subscriptions, payouts, bank accounts, cards |
| Admin | same as the Owner |
| Billing (add-on role) | same as the Owner, as far as payments go |
| Member | no access: 403 error |
The academy's payment notifications go only to the Owner and to people with the Billing role.
The seller (who gets paid)
- Sees the transactions and subscriptions where they get paid, and the payouts to their own accounts.
- Sees the buyers of their own course. Asking for the buyers of someone else's course returns an empty list.
- A payout goes only to a bank account of the same context.
- The search of sold courses shows only the courses of the active context; other people's private courses do not appear.
The buyer (who pays)
- Sees their own transactions and subscriptions, can retry a failed payment and download their own invoices.
- Manages only their own cards: a card is set as default, saved or deleted only if it belongs to their own payment profile.
- A payment session (checkout) is read or closed only by whoever opened it.
What someone unrelated sees
A transaction, a subscription, a payout, a bank account or a payment session of another context, for whoever asks, does not exist: the answer is 404 (for payment sessions Checkout session not found) and nothing is changed on Stripe. This holds even for the Owner of another academy.
No images for now
The app's Billing pages still show sample data: this guide will get its images when the real page exists. The behaviour described here is verified by the API tests.