> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-faqs/payment-automation/why-didnt-the-money-from-a-cancelled-or-failed-payment-come-back-to-our-bank.md).

# Why didn't the money from a cancelled or failed payment come back to our bank?

Payment Automation does not move it back automatically. The funds stay in your business entity's Charted balance until you start a balance transfer.

A balance transfer reaches your bank in 2 business days if started before 4:00 PM Eastern time. Do it before you create a replacement payment, or your account is debited twice.

{% hint style="info" %}
See [Handling failed and cancelled payments](https://docs.charted.com/ap-automation/charted-features/payment-automation/handling-failed-and-cancelled-payments.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://docs.charted.com/ap-automation/charted-faqs/payment-automation/why-didnt-the-money-from-a-cancelled-or-failed-payment-come-back-to-our-bank.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.
