> For the complete documentation index, see [llms.txt](https://help.donary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.donary.com/usage-and-examples/glossary.md).

# Glossary

<table><thead><tr><th width="253">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Campaigns</strong></td><td>The cause and purpose of the donation. Every donation is directed towards a specific cause AKA campaign.</td></tr><tr><td><strong>Collectors</strong></td><td>AKA fundraisers. Individuals that actually collect the money and donations.</td></tr><tr><td><strong>Donation page</strong></td><td>A dedicated online page, accessible via a unique URL, where donors can make donations to the organization (We call it our Webgive page).</td></tr><tr><td><strong>Donors</strong></td><td>Individuals who have donated or are committed to donating money in the future.</td></tr><tr><td><strong>Locations</strong></td><td>Where the donation was made.</td></tr><tr><td><strong>Minyanim</strong></td><td>This feature works in conjunction with the Pocket Processor. Its purpose is to inform the collector of the specific locations associated with the different minyanim.</td></tr><tr><td><strong>Payment</strong></td><td>In terms of a donation, a payment is the money or contribution given by a donor.</td></tr><tr><td><strong>Pledges</strong></td><td>A promise to donate money in the forseeable future.</td></tr><tr><td><strong>Reasons</strong></td><td>A team in a charity drive (Donate +). Each team has an online page with a fundraising goal.</td></tr><tr><td><strong>Schedules - Payment</strong></td><td>A scheduled payment is a payment set to be processed automatically on a specific date or at regular intervals, such as weekly or monthly. On each scheduled date, the donor’s card is automatically charged.</td></tr><tr><td><strong>Schedules - Pledge</strong></td><td>A scheduled pledge is a planned, recurring pledge commitment.<br>Each occurrence creates an open pledge (invoice) that the donor is responsible for paying.</td></tr><tr><td><strong>Sources</strong></td><td>This refers to all endpoints where transactions are processed and captured, including all devices, links, phone extensions, and more.</td></tr><tr><td><strong>Tokens</strong></td><td>A token is a value provided by the processing company. It represents the credit card that the donor has saved with the processor.</td></tr><tr><td><strong>Transaction</strong></td><td>The actual transaction, which can be a scheduled payment, a pledge or a payment.</td></tr><tr><td><strong>Webgive page</strong></td><td>A dedicated online page, accessible via a unique URL, where donors can make donations to the organization (also known as a Donation page).</td></tr><tr><td><strong>נדרים ונדבות</strong></td><td>These are promises to donate money - promises made when one is עולה לתורה.</td></tr></tbody></table>


---

# 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.donary.com/usage-and-examples/glossary.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.