Connect your server
Bring GTA Capital to your community. Connect your own FiveM hosting, framework and authorized player sessions.
Join your community’s workspace.
Choose a server, then use its operator-issued player token or the browser link from the in-game /capital terminal.
Your server. GTA Capital interface.
Keep your existing host and framework. Install the connector, provision a separate tenant, then let players open their authenticated Capital workspace from the in-game terminal.
Operator handoff
- Download the resource and give the installation guide to your server operator.
- The API operator configures durable MySQL, migrations and unique tenant credentials. A public server listing does not provide this access.
- Install the resource and SQL snapshot table. Run
capital_statusin the server console, then/capitalwith a loaded character. - Use the terminal’s browser link to sign in. The signed session determines the financial tenant, never a directory selection.
Capital accounts and framework bank balances remain separate. Framework money settlement is not enabled by installing this connector.
Generate server configuration
# GTA Capital operator configuration
# Configure the API database, tenant and unique server credential first.
# In gta_capital/config.lua, set Config.Framework to 'qbox'.
set gta_capital_api_url "https://gta-capital.vercel.app"
set gta_capital_api_key "REPLACE_WITH_PRIVATE_TENANT_SERVER_KEY"
ensure oxmysql
ensure qbx_core
ensure gta_capital
add_ace group.admin gta_capital.admin allow
No secret is entered or stored here. Replace the key placeholder privately on the game server. The default API origin still requires database provisioning.
Let a provider run the infrastructure
Choose an existing community’s operator or a Cfx-listed hosting provider. Hosting, account setup and installation are handled by that provider; GTA Capital remains the financial interface.
Integration reference
Banking, lending, markets and business modules share tenant-scoped APIs. Keep your server credentials private and configure the backend for your deployment.