> For the complete documentation index, see [llms.txt](https://tn-modifications.gitbook.io/tn-modifications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tn-modifications.gitbook.io/tn-modifications/tn_banking/configuration.md).

# Configuration

Configuration examples, supported options and setup checks.

Edit `config.lua`. Keep the existing tables and append entries where shown.

## Framework and providers

```lua
Config.Framework = 'auto' -- auto, esx, qbcore, qbox
Config.Locale = 'en'
Config.Integrations.Inventory = 'auto'
Config.Integrations.Target = 'auto'
Config.Integrations.Notify = 'auto'
Config.Integrations.TextUI = 'auto'
```

Target: ox\_target, qb-target, qtarget, sleepless\_interact, interact, custom or none. Inventory supports the providers listed in `Config.Integrations`; card metadata is required on ESX/Qbox.

## Add a branch

```lua
Config.Branches.locations[#Config.Branches.locations + 1] = {
    label = 'Custom Branch', coords = vector3(149.46, -1042.09, 29.37)
}
```

Replace the example coordinates with the actual counter. Without a target script, branches use **E**.

## Add a card tier

```lua
Config.CardTiers.tiers[#Config.CardTiers.tiers + 1] = {
    id = 'business', label = 'Fleeca Business', design = 'gold',
    minBalance = 150000, upgradePrice = 1500, feeDiscount = 40,
    limits = { withdraw = 15000, transfer = 75000 }
}
```

Use a unique ID. Built-in designs are `classic`, `silver`, `gold`, `platinum`. Fees/discounts use percentages, not fractions.

| Setting                     | Controls                                                     |
| --------------------------- | ------------------------------------------------------------ |
| `Config.Fees`               | Replacement card, receipt and ATM fees.                      |
| `Config.Security`           | PIN attempts and lock duration in seconds.                   |
| `Config.Credit`             | Loan limits, income/score checks, interest and installments. |
| `Config.Ownership`          | Branch/ATM prices, maintenance and owner fee limits.         |
| `Config.PD.jobs`            | Minimum lookup grade per police job.                         |
| `Config.BalanceSyncSeconds` | External balance polling interval.                           |

## Commands and checks

`/pdbank` requires the correct job/grade and PD position. `/fleecareset` shows a confirmation code; `/fleecareset <code>` deletes all Fleeca accounts while keeping framework bank money and ownership. Its access/settings are in `Config.Reset`; treat it as a destructive administration command.

Test account creation, card use, deposit/withdrawal, transfer, receipt use and police lookup after setup.


---

# 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://tn-modifications.gitbook.io/tn-modifications/tn_banking/configuration.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.
