> 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/getting-started/funds-delivery-times.md).

# Funds Delivery Times

Your organization may receive gifts from two sources: [DAFpay](/dafpay/editor.md) and [Disbursements](/disbursements/for-grantmakers.md). The delivery method and timing of these gifts depend on your organization’s account status and whether you’ve completed Chariot Deposit Account (CDA) verification.

Below is a breakdown of when to expect your first gifts based on your setup:

### ✅ If Your Chariot Account Is Claimed

**DAFpay Gifts** are delivered according to the DAF provider’s timeline—typically within 1–2 weeks after initiation, though it may vary depending on the provider's internal processing time. See DAFpay [Flow of Funds](/dafpay/flow-of-funds.md)

**Grantmaker partner gifts** will be sent electronically within minutes of approval and funds release. See [For Nonprofits](/disbursements/for-nonprofits.md)

***

### 🚫 If Your Chariot Account Is Not Claimed

**DAFpay Gifts** will be held by the DAFpay Network for 60 days. If the account remains unclaimed, a check will be mailed to your IRS-registered address after that period. See DAFpay [Flow of Funds](/dafpay/flow-of-funds.md)

**Grantmaker partner gifts** will be sent by check after 7 days of gift initiation if the account is still unclaimed.

{% hint style="info" %}
**Tip:** To receive all gifts electronically and without delay, we recommend completing your Chariot Deposit Account setup as soon as possible.
{% endhint %}

If you have any questions about your first gifts or CDA status, feel free to contact us at <contact@givechariot.com>.


---

# 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/getting-started/funds-delivery-times.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.