> 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/settings/billing/updating-stripe-bank-information.md).
# Updating Stripe Bank Information
After a bank account has been set up in a system to be used in Stripe it can updated via the admin site. To accomplish this please visit the system **Settings** > **Billing** > **Account Information**.
Below are the steps on how you can update your stripe information.
1. Login to your [Movatic Admin](https://admin.movatic.co/) portal.
2. From the dashboard click **Settings**.
3. Click the **Billing** tab.
4. Scroll down to **Account Information**, then click on **Update** button.\
\
Once you hit Update you will be redirected to your Stripe account where the system's details are presented and you can change your information. The new bank account details should be provided in that page and ensure changes are submitted before leaving Stripe.
{% hint style="info" %}
If you encounter any issue or if you have any questions feel free to reach out to our Support team through our email **.
{% 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://documentation.movatic.co/admin-site/settings/billing/updating-stripe-bank-information.md?ask=&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.
