> For the complete documentation index, see [llms.txt](https://wiki.qfdevelopers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.qfdevelopers.com/scripts/banking-v2.md).
# Banking \[V2]
This category is for our Banking \[V2]
**Banks your players run. And sometimes rob.** Banking V2 turns every bank in the city into a business. Players open accounts, carry cards with a PIN, transfer money, save, take loans and pay their bills, while other players buy the banks, hire the staff, set the offer and keep the vaults full of cash.
**Everything is set in game.** Branches, ATMs, offices, the bank exchange, the economy, items and permissions are placed and edited in the admin panel (`/bankadmin`). The config file only starts the resource, and the database is created and repaired by itself on every start.
**Drop-in replacement for V1.** The resource provides `qf_banking` and `qf_billing`, so every script written for our Banking V1 or Billing System keeps working, and their data is imported with one console command.
---
# 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://wiki.qfdevelopers.com/scripts/banking-v2.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.
