> 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/diary-studies/manage-a-diary-study/request-payments-in-a-diary-study.md).

# Request payments in a diary study

You'll see a Payment Status column on the far right of the **Manage** table of your diary study studies. Before any participants have payments requested, approved, or sent, there will not be any status listed for each participant:

![](/files/21dc749c722142f61f76b87ceeb7f266cfd38e08)

## Request payments in bulk

Requesting payments in bulk helps Dscout pay participants more efficiently. Once your mission has concluded, use the methods outlined below to select all of the participants you would like to pay, then click **Request Payment** from the bulk action toolbar.

Use the checkboxes on the left side of the Manage table to select all of the participants you would like to pay:

![](/files/bccdcded1e903464de036141b5911da180f65302)

Once you click **Request Payment**, a modal will open that will contain a list of selected participants and the incentive amount to be paid. This incentive amount is pre-populated with the incentive that you entered during the mission setup. However, you’re welcome to adjust the incentive for participants in bulk for everyone listed in the modal, or for individual participants.

![](/files/8521dd7ab2dd4f9e29ae2f50c5f1c0f26f27cb2c)

Once you click the **Review Payments** button at the bottom of the modal, another modal will open that will contain a summary of the payments being requested along with the total.

Once you click the **Request Payments** button at the bottom of the modal, a request will be sent to the Research Advisor working with you on your project, notifying that payments have been requested and are ready for review and approval.

Be sure to review the requested payments in this modal carefully as once you request payments, there will only be a short window of time to make adjustments before your Research Advisor approves payments and they become uneditable.

Your page will refresh and you’ll be brought to the **Payments** tab on the **Manage** page. Keep an eye out for the confirmation banner at the top of the page:

![](/files/a2d5551b8052a5601ea165df22d406c6a3312320)

The Payments tab will now be updated with the following information:

* Total incentives for listed participants will be in the upper right corner.
* Newly requested payments will have a Payment Status of **Requested**.
* Amount of incentive requested.
* Date Requested.
* Date Sent \[when applicable].

![](/files/3a4028f8a2a989d983553995a9eeade7e5092c9f)

Nice job, you have just requested payments for participants!

<details>

<summary>How do I edit or delete payments for participants?</summary>

If you have requested a payment for a participant incorrectly, you have a limited amount of time to make edits to your request. Please note, once the Research Advisor working with you on your project approves these payments, they will be locked for editing.

To edit an individual requested payment, select the pencil icon on the far right of the Payments table and select **Edit Amount** or **Delete Payment**:

![](/files/3cfcf8b3e0b03c4566d1bea6e64ba102b0ee0920)

To bulk edit several requested payments, use the checkboxes on the left side of the Payments table to select all of the participants you would like to edit, then from the bulk action toolbar select **Edit Payment** or **Delete Payment**:

![](/files/f32d458a1a941dcd670b485f685a3c2148e5ecee)

</details>

<details>

<summary>How do I check on payments for participants?</summary>

Once payments have been requested in a mission, Payment Status will update based on what step of the payment process the participant is in:

![](/files/254b9386af9e807d6afbdf5fae7478f0ba5c18ad)

**Requested** indicates that an individual with a [researcher](/getting-started/dscout-quickstart-guide/user-roles-and-permissions.md) seat has requested payments for participants. An email has been sent to a Research Advisor to review and approve. Once a payment has this status, it is still available to edit or delete.

![](/files/d80260d5897bc3879492ea750b722261b2df2ead)

**Approved** indicates that a Research Advisor has reviewed payments and approved them, kicking off the payment process. Once a payment has this status, it has been locked for editing.

![](/files/8922c5187c08d9358ed24924bdfe655d379df1b2)

**Sent** indicates that the payment has been issued to the participant via PayPal.

</details>

## When are participants paid?

Once a payment is requested for a participant, they can expect payment to hit their PayPal account in 7–10 business days. If participants are having trouble or have payment questions, please refer them to **<payments@dscout.com>**.


---

# 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://help.dscout.com/diary-studies/manage-a-diary-study/request-payments-in-a-diary-study.md?ask=<question>&goal=<endgoal>
```

`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.
