> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/recruit-participants/working-with-participants/paying-participants/how-are-partner-panels-participants-paid.md).

# How are Partner Panels participants paid?

When you recruit from Dscout's Partner Panels, you pay participants through Dscout just as you would for any other participants. Dscout then sends each payment to the third-party partner who sourced the participant, and the partner pays them. When and how payments are issued depends on your study type.

### Payment rules for Partner Panels participants

Because payments are processed by our partners, these rules apply in every study type:

* Each participant can only be invited to one study and paid once.
* Payments can't be lower than the incentive listed on your Partner Panels screener or study.
* Incentives must be monetary.

{% hint style="warning" %}
**Warning:** Your study’s incentive must be equal to or higher than your Partner Panels screener’s incentive, and you can’t change a screener’s incentive after launch. Usability tests and AI moderated studies allow up to $200, and media surveys up to $100. If your screener’s incentive is higher, you’ll only be able to add those participants to a diary or interview study.
{% endhint %}

### Usability tests, media surveys, and AI moderated studies

Dscout pays participants automatically through the partner. This applies whether you auto-recruit from Partner Panels or add participants from a Partner Panels screener.

Partner Panels aren't available for intercept studies.

{% hint style="info" %}
**Note:** Incentives and activity credits are billed to your account. Speak with your Dscout Account Manager to learn how your account manages them.
{% endhint %}

#### When participants are paid

Once a participant's submission finishes processing, a seven-day review period begins. Use this time to review the submission for quality. When the review period ends, Dscout sends the participant's incentive to the partner, who pays the participant.

#### Report or refund a participant

If you spot a quality issue during the review period, you can report the submission. Reporting a submission or excluding it from your dataset doesn't stop the participant from being paid. To withhold their incentive, select **Request refund** when you report the issue. Refunds can only be requested within seven days of a participant's submission.

**Request refund and recruit additional participant** isn't available for Partner Panels participants. For more information, see [Requesting refunds and backfilling data](https://help.dscout.com/study-basics/analyze-studies/reporting-excluding-and-re-including-data.md#requesting-refunds-and-backfilling-data).

#### Incentive and participant limits

When you auto-recruit from Partner Panels, the incentive and participant limits you can set depend on your study type:

| Study type           | Incentive per participant | Participant limit |
| -------------------- | ------------------------- | ----------------- |
| Usability tests      | $5–200                    | 1–200             |
| Media surveys        | $5–25                     | 1–500             |
| AI moderated studies | $2–200                    | 1–200             |

Partner Panels screeners accept an incentive of $5–1,000 and up to 500 participants.

{% hint style="success" %}
**Tip:** Partner Panels participants often have hard-to-find expertise, so plan to offer a higher incentive. For advice, see [Recommended study incentives](https://help.dscout.com/study-basics/design-a-study/recommended-study-incentives.md).
{% endhint %}

### Diary and interview studies

In diary and interview studies, you recruit Partner Panels participants with a Partner Panels screener, then add them to your study. Once a participant has completed your study, request their payment from the **Manage** tab, just as you would for any other participant. The payment rules above apply, so you can't request a second payment for a participant or a payment lower than the screener's incentive.

For step-by-step instructions, see [Request payments in a diary study](https://help.dscout.com/diary-studies/manage-a-diary-study/request-payments-in-a-diary-study.md) or [Request payments in an interview study](https://help.dscout.com/interview-studies/manage-an-interview-study/request-payments-in-an-interview-study.md).

For more information on Partner Panels, see:

* [Partner Panels](https://help.dscout.com/recruit-participants/partner-panels.md)
* [Auto-recruit from Partner Panels](https://help.dscout.com/recruit-participants/partner-panels/auto-recruit-from-partner-panels.md)
* [Recruit from Partner Panels using a screener](https://help.dscout.com/recruit-participants/partner-panels/recruit-from-partner-panels-using-a-screener.md)


---

# 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://help.dscout.com/recruit-participants/working-with-participants/paying-participants/how-are-partner-panels-participants-paid.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.
