Accounts
Personal caps, first-account balance, shared account membership, and default account behavior.
A roleplay-first banking system for FiveM servers: modular accounts, cards, invoices, transfers, ATM cash, recurring payments, and Gov ID protection from a single tRPC-backed resource.
This public preview mirrors the new server-owner config model. The production resource fails closed when a module is disabled; the app hides the matching entry points, exports stop partial behavior, and recurring jobs only start when enabled.
Bank now exposes its main parts as modules. Owners can ship a complete economy surface or keep the resource lean by disabling cards, invoices, recurring transfers, ATM cash, or phone transfers.
The Bank resource is built around a stable module layout. Each module owns a visible user surface, server procedures, exports, and runtime behavior.
Personal caps, first-account balance, shared account membership, and default account behavior.
Own-account transfers, phone transfers, fees, and fail-closed transfer routes.
Cash deposit, withdraw, preset amounts, fees, and card-withdraw integration.
Player-to-player requests with open, paid, and cancelled states.
Virtual cards, PIN hashing, reveal grants, lockouts, blocking, and business-card support.
Daily, weekly, or monthly standing orders with no backfill after missed cycles.
The resource is past the tRPC migration and production hardening pass. The remaining formal release work is operator-side: final manual native-boundary notes and release packaging process.
The web app calls one tRPC NUI callback and the server routes stable Bank procedure paths through the resource-local router.
Disabled modules are guarded before protected handlers run, and the UI adapts to public config.
Protected reads and actions use Gov ID grants, and public preview data is limited to availability, balance, and currency.
Bank package tests, Bank web tests, app builds, packaged smoke, migration smoke, and the fast release gate have passed in this workspace.