> 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.md).

# Dsync-Banking

## Dsync-Banking

**Dsync-Banking** is a complete, database-backed banking system for FiveM servers running **QBCore**, **QBX**, or **ESX** (the active framework is auto-detected — no manual switch needed).

It replaces a server's default money system with a full banking suite: real bank cards and ATMs, society (job/gang) treasuries, shared accounts, loans with automatic installment collection, interest-bearing savings, bills/fines/invoices, peer-to-peer transfers with scheduling, and a credit-score system — all fronted by a polished React NUI and backed by a fully audited transaction ledger.

{% hint style="warning" %}
**Every amount in every export, callback, and database column is stored in CENTS.** `$10.00` is `1000`. Divide by 100 to display a value; multiply by 100 before passing a dollar amount in.
{% endhint %}

### Feature overview

| Module                      | What it does                                                                                                   |
| --------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Personal banking**        | Deposit / withdraw / transfer, backed by the framework's real money (never a stale mirror)                     |
| **Bank cards & ATMs**       | Virtual or physical (ox\_inventory) cards, PIN auth, freeze/unfreeze, per-card daily spending limits           |
| **Society accounts**        | Job/gang treasuries with grade-based permissions, configurable allowlist, withdrawal caps                      |
| **Shared accounts**         | Player-owned pooled accounts with per-member deposit/withdraw/log permissions                                  |
| **Loans**                   | Credit-score-tiered APR, automatic installment auto-deduction, missed-payment bounce charges, default handling |
| **Savings**                 | Interest-bearing sub-accounts with configurable rate and compounding interval                                  |
| **Bills, fines & invoices** | Issue from any resource (police, mechanic, city) via exports; players pay from the Bills tab                   |
| **Transfers**               | Beneficiaries, money requests, and recurring scheduled payments                                                |
| **Credit scores**           | FICO-style 300–850 score that reacts to on-time/missed loan payments                                           |
| **Audit logging**           | Every action ships to Datadog or Discord webhooks with a filterable category                                   |

### Support

This resource is maintained under the **Dsync** organization. For bugs or feature requests, reach out through your usual Dsync support channel.


---

# 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.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.