> For the complete documentation index, see [llms.txt](https://participanthelp.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://participanthelp.dscout.com/getting-paid/payment-basics/when-to-expect-your-reward.md).

# When to expect your reward

Typically, so long as you've followed all of the study instructions by the communicated deadlines and provided honest and thoughtful responses, **you can expect to see your reward within 10 business days of the day your study closes.** You can refer to the "study close" date by navigating to your ["Closed" studies tab](/diary-studies/diary-troubleshooting/accessing-closed-studies.md).

We’ll message you in the Dscout mobile app (you’ll receive this message via email, too) to let you know the **exact date** you can expect your reward as soon as the study leader approves your entries and gives us the green light.

This message will look like following:

![R1.png](https://content.gitbook.com/content/WDOo5BT5iAW9nWsfYLgS/blobs/b0nokmZ2GLHHG0BDkzGh/35730680059028)

We try our best here at Dscout to pay you as quickly as possible for your hard work, but the review process and closing a project can sometimes take longer than expected. Study leaders might be finishing up some last-minute tasks before submitting the project for payment. Rest assured, however, that we'll let you know the exact date you can expect your hard-earned reward as soon as we can!

If you don’t receive your payment by **end of day (5pm, Central Time)** on the specified pay date, please check out our [troubleshooting section](/getting-paid/troubleshooting-a-failed-study-payout.md) or feel free to reach out to at <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 by asking a question.

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

```
GET https://participanthelp.dscout.com/getting-paid/payment-basics/when-to-expect-your-reward.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.