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

# DAFpay Overview

DAFpay makes it easy for donors to give from their Donor Advised Funds directly from any nonprofit donation form.

Instead of leaving your site, logging into a DAF portal, and navigating a separate process, donors can complete a DAF gift in just a few clicks — right where they are inspired to give.

DAFpay is embedded directly into donation forms through our [Fundraising Platforms](/dafpay/fundraising-platforms.md) integrations, giving nonprofits access to a wide network of DAF providers without needing separate relationships or workflows.

{% embed url="<https://www.loom.com/share/bc3ae720e0e14fadbd8e766341327445?sid=997b9d71-2978-4dd1-94b5-083031782d3c>" %}

### For Donors

{% stepper %}
{% step %}

#### Select

Choose from +1,000 unique Donor Advised Fund providers
{% endstep %}

{% step %}

#### Login

Securely authenticate into your Donor Advised Fund account<br>
{% endstep %}

{% step %}

#### Submit

Submit your grant request
{% endstep %}
{% endstepper %}

<a href="https://secure.dafpay.com/demo" class="button primary">Try it now</a>

***

### DAFpay & Your Chariot Account

Having a Chariot account is not the same as DAFpay — DAFpay is one of Chariot’s product offerings.

To enable DAFpay on your donation form, your [Fundraising Platforms](/dafpay/fundraising-platforms.md) may require you to claim a Chariot account. Once your account is set up, you can enable DAFpay across supported platforms.&#x20;

{% hint style="info" %}
Additional features — such as expanded DAFpay access or APIs are only available on an upgraded plan. See [Subscription Features](/dafpay/subscription-features.md).
{% endhint %}

#### Delivery Of Funds

DAFpay handles donation initiation, **not** payment delivery. When a donor submits a gift through DAFpay:

* Donor and gift data are shared with your organization in real time
* The [Key Concepts](/getting-started/key-concepts.md#donation-payment-statuses) will show as 'Incoming' in your Chariot dashboard

At this stage, the donor has *recommended* the gift — but the **DAF provider is responsible for the flow of funds**, not Chariot or DAFpay.

<table><thead><tr><th width="332.765625">DAF Provider (Used By DAFpay Donor)</th><th width="225.99609375">Payment Source</th><th width="188.6953125">Delivery Of Funds</th></tr></thead><tbody><tr><td>Dallas Jewish Community Foundation</td><td><strong><code>Connected</code></strong></td><td><strong><code>In Chariot</code></strong></td></tr><tr><td>BNY Mellon Charitable</td><td><strong><code>Not Connected</code></strong></td><td><strong><code>Outside Chariot</code></strong></td></tr></tbody></table>

Whether DAFpay funds arrive electronically in your Chariot account depends on the DAF provider and your [Sources](/getting-started/sources.md#connected-sources):

* If the DAF provider on DAFpay is one of your connected sources, the funds will be delivered into your Chariot account
* If the DAF provider on DAFpay is not a connected source, the funds will be delivered outside of Chariot. See [Using Chariot](/getting-started/using-chariot.md#received-outside-of-chariot)

{% hint style="info" %}
The DAFpay Network is only used when a donation is initiated through DAFpay and the nonprofit **has not yet claimed their Chariot Deposit Account.** See [DAFpay Network](/dafpay/dafpay-network.md)
{% endhint %}


---

# 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.givechariot.com/dafpay/editor.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.
