> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aps-store.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Database

> The database tables aps_banking creates on start, what each one stores, and why balances should not be edited by hand.

aps\_banking creates all its tables on start. Names can be changed in `Config.DB`.

| Table | Contents |
| - | - |
| `aps_bank_accounts` | Every account: IBAN, type, balance, frozen state, interest progress |
| `aps_bank_members` | Members of shared accounts |
| `aps_bank_transactions` | History. Both sides of a transfer share a `pair_id` |
| `aps_bank_cards` | Cards with salted PIN hash, limit and attempts |
| `aps_bank_loans` | Loans and their progress |
| `aps_bank_loan_payments` | One row per payment |
| `aps_bank_credit` | Credit score per character |
| `aps_bank_credit_log` | Every score change |
| `aps_bank_receipts` | Printed statements |
| `aps_bank_scheduler` | Last run of daily jobs |
| `aps_bank_migrated` | What the importers already handled |

> [!CAUTION]
>
> Don't change balances in these tables by hand while the server runs. On personal accounts `balance` is unused: that money is in the framework. Use the exports.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.