> For the complete documentation index, see [llms.txt](https://docs.dsyncstudios.store/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dsyncstudios.store/products/dsync-banking/getting-started/quick-start-checklist.md).

# Quick Start Checklist

## Quick Start Checklist

Use this as a first-boot checklist after installation.

* [ ] Resource folder is named exactly `Dsync-Banking`.
* [ ] `ensure Dsync-Banking` appears **after** oxmysql, ox\_lib, ox\_target, and your framework in `server.cfg`.
* [ ] Console shows `Framework detected: <YOUR_FRAMEWORK>` and `v3.0 loaded successfully` with no `Schema statement failed` lines.
* [ ] Walk up to an ATM in-game — you should be prompted to open the bank UI.
* [ ] If `Config.cards.mode = 'item'`, add the bank card item to ox\_inventory **before** testing ATMs, or card-based auth will have nothing to check against.
* [ ] Decide your **loan auto-deduction** cadence (`Config.loans.deductionGap`, in days) and make sure `Config.loans.debugMode = false` — this flag is for testing only and switches the unit to minutes.
* [ ] Decide whether **Savings** and **Shared Accounts** should be enabled for your server (`Config.savings.enabled`, `Config.shared.enabled`) — both default to `true` and can be turned off with zero side effects on existing data.
* [ ] Pick a **society allowlist** strategy: leave `Config.society.jobs` / `.gangs` empty to give every job/gang a treasury, or populate them to restrict society accounts to specific jobs/gangs only.
* [ ] Wire up audit logging — Datadog if you already have it (same pipeline as most ox-based logging), or a Discord webhook.
* [ ] Test a **deposit**, a **withdrawal**, and a **transfer** end-to-end from the UI before opening the server to players.

Once these are checked, jump to the [Configuration Reference](/products/dsync-banking/configuration-reference.md) to tune every module in depth.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.dsyncstudios.store/products/dsync-banking/getting-started/quick-start-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
