> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/coaches/manage-coach-tiers/coach-payments-and-payouts.md). # Coach Payments & Payouts ### Overview There are two options available within PodPlay, Clubs can either: 1. Allow for Coach payouts through the system ([*not available for international Clubs*](https://podplay.gitbook.io/docs/coaches/manage-coach-tiers/coach-payments-and-payouts#payment-process#international-clubs)) 2. Not allow for Coach payouts through the system Coaches will receive money through PodPlay by completing Stripe onboarding from their Profile. **Without a finished Stripe account, a Coach cannot be paid through the system** for Reservations or Events. If a Coach does not have a Stripe account completed or the Club does not allow for Coach payouts through the system, all revenue from Lessons and Clinics (or any Event) is sent to the Club's bank, and then the Club can pay the Coach outside the system. ### Stripe Onboarding When a Coach sets up their Profile, a blue `Start Onboarding` button appears under the [Payments drawer](https://podplay.gitbook.io/docs/coaches/coach-setup-and-profile/how-does-a-coach-set-up-their-profile#payments). This button routes the Coach to Stripe to create the account that receives their payouts. Without finishing the Stripe account, the Coach cannot be paid through PodPlay. If the Coach has not completed Stripe onboarding, staff will see an error message ([reference](https://podplay.gitbook.io/docs/coaches/manage-coaches/coach-payments-and-payouts/no-payment-received#coach-doesnt-set-up-payments)) in the Coach Profile when clicking the Payments drawer. Once the Coach completes Stripe onboarding, they start receiving income for their work at the Club. ### Enable Coach Payments {% hint style="danger" %} **If your Club has elected not to pay Coaches through the system, anyone with the Owner role can turn OFF the Coach Payments toggle.** {% endhint %} Turn OFF the Enable coach payments toggle to take all Coaching lesson revenue and send it to the Club's Stripe account. Turning this toggle ON to allow the Coach to set up a Stripe ID. The Coach MUST also (as a second step) set up their Stripe ID in their Coach Profile to enable Stripe-based payouts, calculated as the Lesson's list price minus any fees configured to be sent to the Club (see Coach Tiers for more information).
### International Clubs Coaches at Clubs located outside the U.S. are not paid through PodPlay. Paying a Coach through the system would require a cross-border transfer and currency exchange, reducing the amount of money captured. Thus, the system does not support international Coach payments. For all international Clubs, you should still: * Add Coaches to all Events as normal * Allow for Customers to book private Lessons from the App Then, your Club pays the Coach outside the system. To manage Coach payments outside the system, when Coaches be added to Events normally and Customers book private Lessons from the App, anyone with the Owner role can use the `Export` button on the Coach page of the Dashboard. Using the `Export` button on the Coach page in the Dashboard to generate a CSV summary of Coach compensation. The CSV includes: * A list of all private lessons, clinics, and other activities each Coach taught * The Coach's rate for each Lesson, Clinic, or Event ### Payout Schedule Coaches set up their public Profile, availability, rates, and Stripe payout account inside PodPlay from within the Coach Settings. Once Stripe is connected, payouts run on this schedule: * Weekly payouts * Thursday - Wednesday pay period * Payouts arrive on Fridays ### How Coaches Earn Money There are two ways a Coach earns money through PodPlay: 1. Private Lessons (Reservations) 2. Events (Clinics, Private Events, Parties) #### Private Lessons (Reservations) A Customer reserves a court and adds a Coach to the Reservation. The flow of money is: * `Customer booking payment` :arrow-right: split between `Coach` and `Club` To learn more, read about [Coach + court rates](https://podplay.gitbook.io/docs/coaches/manage-coach-tiers/coach-payments-and-payouts/coach-plus-court-rate). When a Coaching lesson is on the Dashboard, the Coach is sent an email and must accept the Lesson invitation. If the Coach does not accept the invitation, the status of the Coach on the Lesson will be `Pending`. To learn more, read about [Private Lessons](https://podplay.gitbook.io/docs/coaches/private-lessons).
#### Events (Clinics, Private Events, Parties) When a Coach is added to an Event, staff will set the Coach's rate during that process. The flow of money is: * `Customer signup payment` :arrow-right: sent to `Club` * `Club payment` :arrow-right: `Coach` The money movement in these bullets are separate and do not rely on each other at all. To learn more, read about [Coach on Events](https://podplay.gitbook.io/docs/coaches/how-does-the-coach-club-split-work-for-an-event). When a Coach is added to an Event, staff should verify the Coach has an `Accepted` status flag next to their name.
### Coach in a Series A Series is several Events connected together. To learn more, read [Create a Series](https://podplay.gitbook.io/docs/events/create-a-series). When a Customer signs up for a Series, they sign up for all Event sessions in that Series. For example: * Series is across 4-weeks, with 1 Event per week, or * Series is across 12-weeks, with 2 Events per week You may want to add a Coach to every Event in a Series (for a Clinic) or to only one Event in a Series (for a Beginners League where the Coach demonstrates how to play and score matches). For a Coach to be paid across a Series, **the Coach must be added to each Event** in the Series. When a Coach is added to an Event within a Series, the Coach is paid the rate set for that single Event. In an example: * 4-week Clinic Series where the Coach's total rate is $200 * Add the Coach to each of the 4 Events at $50 each The Coach is not paid for the entire Series at once, even if the Customer pays for the full Series up front. Paying the Coach per Event in a Series reduces the chances of misrouted payments to a Coach who gets sick or calls out for one Event in the Series. ### Paying a Coach in Cash If the `Payment toggle` is turned OFF for a [Coach Tier](https://podplay.gitbook.io/docs/coaches/manage-coach-tiers), then any Coach in that Tier will not be paid through the system, nor will the Club receive revenue from the Customer when the private Lesson is booked. When the `Payment toggle` is OFF, the Customer will have a notice on the Order Summary page of the booking flow (last page) which states "**Note that you will have to pay the Coach directly.**"
{% hint style="info" %} Coaches at Clubs located outside the U.S. are not paid through PodPlay. Paying a Coach through the system would require a cross-border transfer and currency exchange, reducing the amount of money captured. Thus, the system does not support international Coach payments. {% endhint %} --- # 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.podplay.app/coaches/manage-coach-tiers/coach-payments-and-payouts.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.