> For the complete documentation index, see [llms.txt](https://guide.givewise.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.givewise.ca/for-donors-getting-started-with-givewise/making-a-contribution/contribution-payment-methods/bank-transfers.md).

# Bank Transfers

## Frequently Asked Questions

* **Does GiveWise store any banking information**? No, GiveWise does not store any banking information. GiveWise uses a banking platform called Zum Rails which allows you to contribute to your fund directly from your linked bank accounts.<br>
* **Why are my contributions showing in “Pending” state?** When you make a contribution directly from your linked bank account, you are beginning the transfer of funds. Banks will take some time to verify these transactions. When the transaction is verified by the bank, it will be marked as “Cleared” or “Cancelled” / “Failed” if the transaction could not be verified.<br>
* **Can I use funds that are in the “Pending” state?** No. Once the contribution is marked in the “Cleared” state, the funds will be available in your Giving Wallet, will appear on the Tax Receipt, and will be available to gift to charities.<br>
* **How long will my contribution take to clear the bank?** Your contribution will take up to 2 business days.


---

# 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://guide.givewise.ca/for-donors-getting-started-with-givewise/making-a-contribution/contribution-payment-methods/bank-transfers.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.
