> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/masterstudy-lms/lms-settings/ecommerce/payout.md).

# Payout

{% embed url="<https://youtu.be/Lp-5KRA2nnk?si=-1OCyTTYwHwKh60N>" %}

This section of the MasterStudy eCommerce is a part of the [**Statistics and Payout**](/masterstudy-lms/lms-pro-addons/statistics-and-payouts.md) add-on, and it works only when that add-on is active. It enables you to send payouts to instructors for the courses they are associated with.

<figure><img src="https://691205473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MDTL6WUldKvxQaP8jzz%2Fuploads%2FCiFoYPs8zeAteg1xP6xy%2Fimage.png?alt=media&amp;token=18efcab9-d0e2-4c50-9af5-214b15a33df0" alt=""><figcaption></figcaption></figure>

* **Admin Commission (%) -** set the percentage of the course price that will be allocated to the admin. This amount **includes any payment gateway fees** and is calculated from the full course price. The remaining percentage will go to the instructor.
* **Instructor Earnings (%) -** set the percentage of the course price that instructors will receive. The total of instructor earnings and admin commission will always be equal to 100.

{% hint style="warning" %}
**NOTE:** Payouts are integrated with [PayPal Payouts API](https://developer.paypal.com/docs/api/payments.payouts-batch/v1/) and require a [PayPal Business](https://www.paypal.com/us/webapps/mpp/referral/paypal-business-account2) account for admins.
{% endhint %}

Follow the link below to correctly set up the Payout system on your website:

{% content-ref url="/pages/-MjT2RxtXIiIvsfRJurE" %}
[PayPal Payouts Setup](/masterstudy-lms/paypal-payouts-setup/general-settings.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stylemixthemes.com/masterstudy-lms/lms-settings/ecommerce/payout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.