> For the complete documentation index, see [llms.txt](https://docs.ushahidi.com/platform-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ushahidi.com/platform-user-manual/legacy/7.-managing-your-donations.md).

# 7. Managing your Donations

## **Web Monetization**

{% hint style="info" %}
This data source is not yet available in the stable versions of Platform. You may not find it in your settings.
{% endhint %}

Web monetization is a feature that will help deployers receive donations based on the number of traffic to/on their deployments.

Donations will only be possible when using the Puma browser for mobile or a Coil browser extension for desktop enabled and the users will only be able to donate if they have a Coil account.\
For the deployers to receive money, they will need to have an account on uphold.com. They can either choose to create an account as an organization or an individual. 

Nb: This will be discussed 

[Donations](https://docs.ushahidi.com/ushahidi-platform-user-manual/7.-managing-your-donations/7.1-donations)


---

# 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://docs.ushahidi.com/platform-user-manual/legacy/7.-managing-your-donations.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.