> For the complete documentation index, see [llms.txt](https://help.maearth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.maearth.com/resources-for-donors/questions-about-donations/multiple-donations.md).

# Multiple Donations

What happens when I donate to multiple projects in a funding round?

**You can support as many projects as you'd like during a funding round.**

You can combine up to 25 donations in one cart with a single checkout, but each is processed as a separate transaction. If you contribute to five projects, you'll see five charges on your bank statement and may receive a separate notification from your bank for each.

This is normal. Donations flow directly to organizations' (or hosts partners') Stripe accounts, so each contribution must be processed individually. Note that Stripe receipts will display the recipient organization or host partner organization's name related to each donation, as receipts are not issued by Ma Earth. You will also receive a donation summary directly from Ma Earth.

**Important: When you verify your email, each donation you make will** [**unlock matching funds**](/resources-for-donors/unlocking-matching-funds.md) **for the projects you have supported.**

Questions about a specific transaction? [Contact us](https://maearth.com/contact).


---

# 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.maearth.com/resources-for-donors/questions-about-donations/multiple-donations.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.