> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/billing/issuing-cards/fund-balance.md).

# Fund Balance

Each account has an issuing balance that is shown on the admin site, this is the balance that will fund the credit cards, so it needs to contain the amount available to be spent by the cards. <br>

<figure><img src="https://3693766063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxId4PbGGTlBib03KztrO%2Fuploads%2FwwfPN9KzMSMRBotVWjfl%2Fimage.png?alt=media&amp;token=2005ee14-6d21-44ef-a9a2-a9dd85856637" alt=""><figcaption></figcaption></figure>

### Requirements

Before adding funds to the issuing balance the default bank account specified in Stripe needs to be verified. To do this the Stripe dashboard needs to be accessed. You will need to escalate this to our Customer Support to assist in validating the bank account, the validation will consist of 2 micro deposits (less than $1.00 each) and then you will need to provide the value of these deposits to our agent. \
\
Once your bank account has been verified, visit the admin site issuing cards section, in the "Issuing Balance" section click on the right button "+Add" and submit the amount.&#x20;


---

# 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://documentation.movatic.co/admin-site/billing/issuing-cards/fund-balance.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.
