> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/finance/management-and-reporting/commitments/failed-commitments.md).

# Failed Commitments

Find recurring gifts that failed to charge in Finance > Commitments, help the donor update their payment method, and learn how Anedot retries a declined charge.

When a scheduled recurring gift is declined, its commitment shows **Retrying** in **Finance > Commitments** and Anedot retries the charge. This article covers how retries work, how to find failed commitments, and how to help the donor update their payment method.

## Before You Begin

* **Permissions:** Your role needs **Commitments: View permissions** to find failed commitments, and **Commitments: Edit permissions** to update a payment method, send a payment update link, or activate a commitment. See [Permission Sets](/settings/access/permission-sets.md).

## How Retries Work

When a scheduled charge is declined, Anedot retries it 3 times: 3, 7, and 14 days after the scheduled charge date.

* **Status:** The commitment shows **Retrying** until a charge succeeds or the retries run out.
* **Retry schedule:** The commitment's details show **Retry schedule**, with each upcoming retry date, only while the commitment is **Retrying**.
* **Payment method:** Each retry uses the commitment's current payment method. If the payment method is updated during retries, the next retry uses the new one.
* **Donor emails:** The donor gets an email for each declined charge, such as "We were unable to process your donation", "Re: We were unable to process your donation", "We were unable to charge your \[payment method] on file", and "Final Attempt: We were unable to process your donation".

### Example

A monthly gift is scheduled for March 1 and is declined. Anedot retries it on March 4, March 8, and March 15. If the donor updates their card on March 5, the March 8 retry uses the new card.

## Find Failed Commitments

To find commitments that are retrying:

1. Go to **Finance > Commitments**.
2. Click **Filters**.
3. Under **Status**, choose **Retrying**.
4. (Optional) Filter by the donor's name or email.
5. Click **Apply filters**.

To find commitments that were deactivated, choose **Inactive** under **Status** instead. Hover over the info icon next to the status to see why.

{% hint style="info" %}
For a list you can work from, click **Export CSV**. For retrying commitments, the CSV includes **Retries Remaining**, **Next Retry On**, **Last Retried**, and **Last Failure Reason**.
{% endhint %}

## Help the Donor Update Their Payment Method

You don't need to wait for the retries to finish. Update the payment method as soon as you see **Retrying**, and the next retry uses the new method.

To send the donor a payment update link:

1. Go to **Finance > Commitments**.
2. Click the eye icon (**View**) on the commitment's row.
3. Click **Send payment update link**.

You'll see "Payment method update email sent." and the donor gets an email with a link to update their payment method. Donors can also update it in the Donor Portal. See [My Recurring Gift Failed, Update Payment](/donor-support/faq/my-recurring-gift-failed-update-payment.md).

To update the payment method for the donor:

1. Open the commitment.
2. Click the pencil icon next to **Payment method**.
3. Enter the donor's new card or bank account details.
4. Click **Save payment method**.

You'll see "Payment method updated." Saving doesn't charge the donor now. See [Commitments](/finance/management-and-reporting/commitments.md).

## Reactivate a Commitment

To restart a commitment after the payment method is updated:

1. Update the payment method, or confirm the donor updated it.
2. Open the commitment.
3. Check the **Next charge** date.
4. Click **Activate**.

You'll see "Commitment activated." and the status changes to **Active**.

{% hint style="warning" %}
If the **Next charge** date has already passed, the donor may be charged on the next daily run.
{% endhint %}

## Troubleshooting

* **The commitment was deactivated after one decline.**\
  The payment processor reported that the card or bank account can't be used again. Ask the donor for a new payment method, update it, then click **Activate**.
* **Send payment update link is unavailable.**\
  The commitment has no donor email. Add one in **Edit commitment**, or update the payment method for the donor.
* **The card keeps getting declined after the donor updated it.**\
  Ask the donor to contact their bank or card issuer to find out why the charge was declined.

If the issue continues, contact our Support team.

## Frequently Asked Questions

* **How many times does Anedot retry a failed recurring gift?**\
  3 times, 3, 7, and 14 days after the scheduled charge date.
* **Does the donor know their gift failed?**\
  Yes. The donor gets an email for each declined charge.
* **Do I need to wait for the retries to finish?**\
  No. Update the payment method or send a payment update link as soon as you see **Retrying**.
* **Are ACH returns and chargebacks the same as a failed commitment?**\
  No. See [Refunds and Voids](/finance/management-and-reporting/transactions/refunds-and-voids.md).

## Related Articles

* [Commitments](/finance/management-and-reporting/commitments.md)
* [Notifications](/get-started/security/notifications.md)
* [Manage Recurring Gifts](/donor-support/manage-giving/manage-recurring-gifts.md)
* [My Recurring Gift Failed, Update Payment](/donor-support/faq/my-recurring-gift-failed-update-payment.md)


---

# 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://docs.anedot.com/finance/management-and-reporting/commitments/failed-commitments.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.