> 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/overview/lists/donors/donor-card/new-transaction/new-pledge.md).

# New Pledge

## Create a Pledge

A **pledge** is a promise to donate a specific amount of money in the foreseeable future.

To create a new pledge[^1], follow the steps below:

When adding a new transaction **via the donors card**, the donor information will be **prefilled,** and you can skip directly to [Step 2: Amount](#step-2-amount).

### Step 1: Donor Info

There are several ways to add the donor information:

* You can search for an existing donor using a **phone number** or **name** (Hebrew, English or Yiddish).
* You can use the [**Global List**](https://help.donary.com/overview/lists/donors/add-a-donor.md#donor-info-tab) by toggling the G button and clicking Search.
* Alternatively, you can **add a new donor** directly by entering the donor’s name and clicking the **+Add New Donor button** in the pop-up.
* You may also choose to enter a **display name only**. This creates a transaction with a display name but **does not create a donor record**.
* Click **Next**

{% hint style="warning" %}
**Important:** Pledges require a donor. If you skip donor selection and later choose **Pledge** as the payment type, you will be returned to this step to select or create a donor.
{% endhint %}

***

### Step 2: Amount

* Select a **preset amount** or **manually enter** a custom amount.

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2F1Ct1dhNLUI3wd9gBW5fh%2Famount%20snip.png?alt=media&amp;token=d4592a74-86dd-4f1c-bd39-9e02ea6a8a9d" alt=""><figcaption></figcaption></figure>

* Choose the **currency**.

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FceJw0HhstVk9QY5LNExp%2Fcurrency.png?alt=media&amp;token=850c4d64-9595-41c1-9f54-d73a203f038e" alt=""><figcaption></figcaption></figure>

* Click **Next**

{% hint style="info" %}
The **default** currency is defined when your account is set up.&#x20;

Currencies that are enabled via [API keys](https://help.donary.com/cloud-drm/getting-started/setup-and-configuration/api-keys/setting-up-api-keys.md#currency) (e.g., USD, CAD) will be available.
{% endhint %}

***

### Step 3: Payment Type

Payment type indicates how the donation is made. Choose Pledge <img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FW7t93NcOkUWSCNd0yjlz%2Fimage.png?alt=media&amp;token=50c1bb49-0760-4f21-9108-634d1e840e30" alt="" data-size="line">

* For a pledge[^1], you must select a **campaign** and set a pledge **date**.&#x20;

  These can be updated in the Options shown on the right side of the New Transaction card.
* Add an internal and an external pledge note. **Internal notes** are visible only to DRM users, while **external notes** appear on the donor’s pledge bill.&#x20;

***

### Step 4: Options

On the right side of the New Transaction card, you will find the **options**.

After selecting a donor, you can configure additional transaction details:

* **Reason**
* **Campaign**
* **Location**
* **Collector**
* **Record Date**

This associates the transaction with the selected entries.

#### Record Date vs. Created Date

* **Created Date**: When the transaction is created.
* **Record Date (Payment date)**: Used for reporting purposes. This allows you to reflect on when the pledge was actually pledged.\
  *For example:* if a pledge was pledged yesterday but is only being entered into the system today, you can set the Record Date to yesterday to ensure accurate reporting.
* Changing the record date **does not schedule or delay the pledge**.

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FxnmQhvTY7cYOrKowzSfY%2Fpledge%20options.png?alt=media&amp;token=f165ed5c-b0ea-4d34-b017-14455d75d78a" alt="" width="547"><figcaption></figcaption></figure>

{% hint style="warning" %}
You can save default values for **reason, campaign, location or collector** to be prefilled in future transactions by clicking the star by **Save settings as a default**.
{% endhint %}

***

### Step 5: Notifications | Email and SMS

At the bottom of the New Transaction card, you will find the option to set the **notification** type:

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FULdCiQX1yFDVyvmWHpYb%2Fnotifications.png?alt=media&amp;token=edded20b-ab00-4cfa-b8db-8697e9ee66f3" alt=""><figcaption></figcaption></figure>

#### **Email Receipts**

* If enabled in [Settings](https://help.donary.com/cloud-drm/getting-started/setup-and-configuration/settings.md#send-automatic-email), email receipts are selected by default.
* You can edit the recipient email or add a new one.

#### **SMS Receipts**

* SMS notifications must be selected **manually** each time.
* You must choose or add the phone number for SMS delivery.
* There is no default setting to automatically send SMS receipts.

Click **Process** to complete the **Pledge**.&#x20;

***

## After Transaction Completion

Once a transaction is completed, a window will come up showing if transaction was successful or not.

There will be an **indicator** on the email and text receipts showing if they were sent successfully, based on what we set in the [notifications](https://help.donary.com/overview/lists/donors/donor-card/new-transaction/new-payment.md#step-5-notifications-or-email-and-sms).

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FBJX9lPq10oFwFwhEpNcQ%2FPledge%20success%20message.png?alt=media&amp;token=4456db32-11df-436a-84ff-a8fd1d2fca4a" alt=""><figcaption></figcaption></figure>

* Click the **pledge number** to open the pledge card.

<div align="center"><figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FWgBHo3Ig2euyuAS6x16S%2Fpledge%20number.png?alt=media&amp;token=5b16c268-4c9a-4b91-bc49-807f36930beb" alt=""><figcaption></figcaption></figure></div>

* Use **the options below to quickly**:
  * Print and download Bills
  * Resend Email or Text
  * Mail Bill
  * Void the Pledge
  * Start a new transaction

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2F0VOaFMqTjRzTslX22HR4%2Fpledge%20success%20options.png?alt=media&amp;token=48e4e803-7746-481b-9be9-286eecd7c69f" alt=""><figcaption></figcaption></figure>

[^1]: A promise to donate money in the forseeable future.


---

# 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/overview/lists/donors/donor-card/new-transaction/new-pledge.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.
