> 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 mission 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 mission closes.** You can refer to the "mission close" date by navigating to your ["Closed" missions tab](/diary-studies/diary-troubleshooting/accessing-closed-missions.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 mission leader approves your entries and gives us the green light.

This message will look like following:

![R1.png](/files/f518c6f04cc72045bec5dca3df84a57a1eef7352)

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