> 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/gift-processing/custom-payment-sources.md).

# Custom Payment Sources

### Overview

Most nonprofits receive gifts from hundreds of different grantmakers, foundations, workplace giving platforms, and other third-party payers.

While Chariot supports a growing network of [Payment Sources](/getting-started/payment-sources.md), not every payer is already connected in Chariot.

<figure><img src="/files/RTUHnhXas4VQzUPL3ZnN" alt=""><figcaption></figcaption></figure>

Custom Payment Source allows you to connect virtually any payer to Chariot, helping your organization centralize funds and donation data in a single workflow.

***

### Before You Start

Before creating a custom Payment Source, there are a few important differences to understand:

#### 1. The payer must already support ACH payments

Custom Payment Sources only work with payers that can send funds electronically via ACH.

{% hint style="info" %}
If a payer only sends paper checks, you will not be able to provide them with ACH payment instructions. Instead, we recommend using Chariot's [Digital Mailbox](/gift-processing/digital-mailbox.md).
{% endhint %}

#### 2. Your team provides the donation data

Unlike [Payment Sources](/getting-started/payment-sources.md#type-2-additional-sources), custom Payment Sources only automate the movement of funds.

When a deposit arrives, your team is responsible for uploading the supporting donation files, grant letters, or other documentation associated with the payment.

Chariot will automatically extract the donation information, create donation records, and link them to the corresponding deposit so they can be processed using your normal Chariot workflows.

***

### Create a Payment Source

1. Navigate to **Sources** and click **Create Source**
2. Search for the payer you want to add
3. If the payer doesn't exist, create it by providing a name and logo
4. Click **Create Source**

<div><figure><img src="/files/p50adpjDPHOLgoatOHZ9" alt=""><figcaption></figcaption></figure> <figure><img src="/files/segGSRZJnuwmF8r5LOE7" alt=""><figcaption></figcaption></figure></div>

Chariot will generate:

* A unique account number
* A unique routing number
* A bank verification letter

Provide these payment instructions to the payer to begin receiving funds electronically.

{% hint style="danger" %}
**Important:** When you create a Payment Source, you must provide that payer with the specific payment instructions generated for that Source. Using the wrong account and routing number will prevent payments from being associated with the correct Payment Source.
{% endhint %}

***

### Add Donation Data

When funds arrive from a Custom Payment Source, the deposit will appear in Chariot with an **Action Required** status.

<div><figure><img src="/files/tjqUGzP2RwSZVDHZTMJc" alt=""><figcaption></figcaption></figure> <figure><img src="/files/zupbFrZD6w6SmFrRuvZI" alt=""><figcaption></figcaption></figure></div>

To create donation records:

1. Open the Deposit
2. Click **Add Donations**
3. Upload donation files (i.e., PDFs, CSVs, spreadsheets, or grant letters)
4. Review the extracted donation information
5. Confirm the donation records

<div><figure><img src="/files/3g9oWuOqRcDGQ8aI8pDq" alt=""><figcaption></figcaption></figure> <figure><img src="/files/nS5n6JUc6MJZd3BwjL2z" alt=""><figcaption></figcaption></figure></div>

Chariot will automatically create donation line items and link them to the corresponding deposit.

***

### What Happens Next?

Once created, these donations behave just like donations received from any other connected Payment Source.

You can:

* Run Policies
* Apply Properties
* Organize them with Views and Filters
* Export them with Export Templates


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.givechariot.com/gift-processing/custom-payment-sources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.