# Installation

To deploy the system, you must import the database schema and complete the baseline configurations.

## 1. Database Setup (SQL)

The integrated loan and ATM structures in `src-bank` require specific database tables to function. Run the `install.sql` file using an interface like HeidiSQL or phpMyAdmin.

### Table Structure:

* `src_bank_accounts`: Stores the credit score, active PIN code, and IBAN data.
* `src_bank_transactions`: Contains transaction logs for all deposits, withdrawals, and transfers.
* `src_bank_atms`: Keeps track of purchased or placed ATM owner IDs, 3D coordinates, and profit fees.
* `src_bank_loans` & `src_bank_loan_blacklist`: Holds loan limits, maturity cycles, current overdues, debt amounts, and blacklist records.

## 2. Resource Integration

1. Place the downloaded `src-bank` package into your server's `resources` directory (or a relevant subfolder).
2. Add the following to your `server.cfg`:

```bash
ensure qbx_core # or qb-core / es_extended (Your core framework)
ensure ox_lib   # Dependency
ensure src-bank # Banking system
```

## 3. Additional Dependencies (Optional / Required)

* **UI Notifications:** Most of the UI components and notifications rely on `ox_lib`.
* **Inventory Receipts:** If you wish to give players a physical receipt item after their transactions, ensure you add the `receipt` item possessing metadata support to your inventory system. You can disable this feature in the config if not needed.
* **Targeting System:** Integration is supported via `qbx_core`, `qb-core`, `ox_target`, or `qb-target`. If you prefer not to use targeting, you can switch to `text` mode in the Config.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sourcedev.pro/advanced-banking-system/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.