Before starting, you must log in to the CFX portal to download the asset. You will be able to download it as many times as you want on the official CFX page. Just as you download it the first time, you will also download it multiple times in the future to get updates.
1
Logging in to the CFX Portal
First, log in to the official CFX portal by clicking here.
2
Finding Your Assets
Once logged in, navigate to the Granted Assets section to access your purchased assets. You can download them by clicking the "Download" button.
Remember, if you encounter any issues or errors when starting the asset, you can check here to see if the problem is related.
Dependencies vary depending on whether you use QBCore or ESX, and are completely optional as you can disable the partnership system.
The dependencies for this asset are mandatory, so please follow the dependency guide completely and use all required files.
When downloading a dependency, ensure the file is properly unzipped and does not include "-main" at the end of its name. If it does, please remove it.
1
ESX
2
QBCore
Update artifacts and gamebuild
Updating to the latest artifacts and gamebuild is essential to avoid common server issues. Here's how to do it properly:
1
Update Artifacts
Completely replace your current artifacts with the latest version. Download the appropriate artifacts for your operating system from the official links:
This asset must always be started below your framework and inventory. Failure to do so may result in functionality issues or critical errors. To ensure smooth operation and proper initialization, it is recommended to start the entire download folder using "ensure [banking]" in your server.cfg.
Database Installation
For this step, we highly recommend using HeidiSQL to avoid issues, as it provides an updated version of MariaDB. We have a guide that explains step-by-step how to use HeidiSQL. If you choose to use phpMyAdmin, we will not be responsible for any errors that may occur in your database.
Select the framework you are using and then execute the SQL in your HeidiSQL. If you encounter errors, ensure you are using the most current version of MariaDB. You can refer to our guide above or search online.
Database for esx
DROP TABLE IF EXISTS `bank_process`;
CREATE TABLE `bank_process` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`owner` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`type` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`icon` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`text` TEXT NOT NULL COLLATE 'utf8mb4_unicode_ci',
`created` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_unicode_ci' ENGINE = InnoDB AUTO_INCREMENT = 1;
DROP TABLE IF EXISTS `bank_cards`;
CREATE TABLE `bank_cards` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`identifier` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`cardNumber` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`ownerName` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`valid` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`cardType` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`active` INT(11) NOT NULL DEFAULT '0',
`passCode` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_general_ci' ENGINE = InnoDB AUTO_INCREMENT = 1;
DROP TABLE IF EXISTS `bank_history`;
CREATE TABLE `bank_history` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`identifier` VARCHAR(50) NULL DEFAULT '' COLLATE 'utf8mb4_general_ci',
`amount` INT(11) NOT NULL DEFAULT '0',
`type` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb4_general_ci',
`date` TIMESTAMP NOT NULL DEFAULT current_timestamp(),
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_general_ci' ENGINE = InnoDB;
Database for qbcore
DROP TABLE IF EXISTS `bank_process`;
CREATE TABLE `bank_process` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`owner` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`type` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`icon` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
`text` TEXT NOT NULL COLLATE 'utf8mb4_unicode_ci',
`created` VARCHAR(50) NOT NULL DEFAULT '' COLLATE 'utf8mb4_unicode_ci',
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_unicode_ci' ENGINE = InnoDB AUTO_INCREMENT = 1;
DROP TABLE IF EXISTS `bank_cards`;
CREATE TABLE `bank_cards` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`identifier` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`cardNumber` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`ownerName` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`valid` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`cardType` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
`active` INT(11) NOT NULL DEFAULT '0',
`passCode` VARCHAR(50) NOT NULL DEFAULT '0' COLLATE 'utf8mb4_general_ci',
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_general_ci' ENGINE = InnoDB AUTO_INCREMENT = 1;
DROP TABLE IF EXISTS `bank_history`;
CREATE TABLE `bank_history` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`identifier` VARCHAR(50) NULL DEFAULT '' COLLATE 'utf8mb4_general_ci',
`amount` INT(11) NOT NULL DEFAULT '0',
`type` VARCHAR(50) NULL DEFAULT NULL COLLATE 'utf8mb4_general_ci',
`date` TIMESTAMP NOT NULL DEFAULT current_timestamp(),
PRIMARY KEY (`id`) USING BTREE
) COLLATE = 'utf8mb4_general_ci' ENGINE = InnoDB;
DROP TABLE IF EXISTS `bank_accounts`;
CREATE TABLE IF NOT EXISTS `bank_accounts` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`citizenid` varchar(11) DEFAULT NULL,
`account_name` varchar(50) DEFAULT NULL,
`account_balance` int(11) NOT NULL DEFAULT 0,
`account_type` enum('shared','job','gang') NOT NULL,
`users` longtext DEFAULT '[]',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE KEY `account_name` (`account_name`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
DROP TABLE IF EXISTS `bank_statements`;
CREATE TABLE IF NOT EXISTS `bank_statements` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`citizenid` varchar(11) DEFAULT NULL,
`account_name` varchar(50) DEFAULT 'checking',
`amount` int(11) DEFAULT NULL,
`reason` varchar(50) DEFAULT NULL,
`statement_type` enum('deposit','withdraw') DEFAULT NULL,
`date` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(),
PRIMARY KEY (`id`) USING BTREE,
KEY `citizenid` (`citizenid`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Society Configuration
Quasar Banking includes a Society system to manage jobs and organizations, compatible with both ESX and QBCore frameworks. Follow these steps to configure and use it effectively:
1
Enabling the Society System
To enable societies, set Config.EnableSociety to true in the configuration file.
2
ESX Framework
If you are using ESX, the asset will integrate directly with esx_society. No additional configuration is required, as societies will function seamlessly with the default ESX society system.
3
QBCore Framework
If you are using QBCore, you must remove qb-management from your server, as qs-banking replaces its functionality.
Quasar Banking provides all necessary events and exports that were originally handled by qb-management, ensuring a smooth transition.
4
Key Notes
Make sure to only enable the society system for the framework you are using.
Properly test the integration to avoid conflicts with leftover resources or configurations from removed assets like qb-management.
This setup ensures a seamless and optimized experience for managing societies across your server.
