White Label Bank

A multi-tenant banking back end and web app. Customers and administrators use one interface; every rule is enforced on the server.

The installer starts by itself the first time you open your domain.

1. Upload and extract

   In cPanel File Manager, upload the signed zip to the folder of your domain (public_html) and press Extract. Nothing needs to be moved afterwards.

2. Set the PHP version

   cPanel, MultiPHP Manager: choose PHP 8.3 or newer for the domain. Then Select PHP Version and enable the extensions listed above.

3. Create the database

   cPanel, MySQL Databases: create an empty database and a user, then add the user to the database with All Privileges.

4. Open your domain

   For example https://yourbank.com. The installer checks the server, then asks for the bank name, brand colour, contact email, demo or production mode, the database details and the administrator login. Press Install the bank.

5. Add the cron job

   cPanel, Cron Jobs, every minute. The installer shows the exact line; use the ea-php83 path if your host requires it.

   BASH Copy

   /usr/local/bin/php /home/CPANEL-USER/public_html/artisan schedule:run >> /dev/null 2>&1

6. Sign in

   Open /app and sign in with the administrator you just created.

Do these in order before you invite anyone.

• Integrations, Email: connect your mail provider so customers receive messages, then send a test email.
• Integrations, Crypto: set your default wallet addresses.
• Company profile: add your licence and contact details.
• Website content: edit the public website text (see below).
• Partner API: onboard any partner, such as a crypto front end, that will connect to your bank.
• Tenant and go-live: stay in demo mode until the go-live checks pass.

Most of the look and wording is a setting, not a code change.

Brand and identity

Set the bank name and brand colour during installation, and change them any time under Tenant and go-live. Check the identity details that appear on documents: UID, LEI, BIC, clearing number, registered office, regulator and licence categories (Website content, Contact details). IBANs issued through the partner API use the clearing number and BIC you set there.

Public website text

Under Website content you can edit any text on the public website. Leave a field empty to restore the original text. Changes appear straight away.

Pricing and rules

• Under Pricing and compliance: transfer and crypto pricing, quotes, tax rules, maker-checker approvals, fund-origin records, settlements and fee requests.
• Bank transfers are free to Switzerland and 1% international by default; the percentage is tenant-configurable.
• Transfers at or above the review threshold are held for an administrator to approve or reject. A rejection refunds everything, fee included.
• Time deposits run 30 to 365 days with tiered rates.

Email centre

Send messages, newsletters and promotions using the bank template or your own pasted HTML.

One cron job drives everything. If it stops, deposits stop maturing and webhooks stop retrying.

The scheduler matures time deposits, retries partner webhooks, credits crypto deposits, runs the nightly integrity check and renews the licence pass. In production also run a queue worker.

php artisan schedule:run          # what the cron job calls every minute
php artisan bank:integrity         # prove every entry balances and nobody is overdrawn
php artisan bank:process-deposits  # mature due time deposits (also hourly)
php artisan license:report         # refresh the licence pass

1. Copy your key

   Sign in to Biply Market, open My licences and copy the key for this domain.

2. Enter it

   In the bank admin open Vendor and licence, Licence and paste the key.

3. Check the domain

   The key works only on the domain in APP_URL, including the address people use to open your site.

On activation and once a day the script sends the key, your domain and the script version. If a licence is revoked the script locks within the hour and unlocks within the hour of reinstatement. If the marketplace cannot be reached the script keeps running on its current pass and only locks when the pass expires.

Two habits keep a live site safe: backups before every change, and updates from your own dashboard only.

What to back up

Back up the database and the .env file regularly. The .env file holds your application key and settings. Also keep a copy of the storage folder if you accept uploads.

Installing a new version

1. Back up first

   Copy the files and database as described above. Keep the copy somewhere other than the server.

2. Download the new release

   Sign in to Biply Market, open My licences and download the latest signed zip. Releases are only available to licence holders.

3. Upload and overwrite

   Extract the zip over your existing files. Do not delete your data folder or .env file: they hold your settings and customers.

4. Check the release notes

   Each release says whether the database changes. If you have no terminal access, email [email protected] and we will apply it for you.

5. Open the site and test

   Sign in as an administrator and check one normal action before you tell customers.

• APP_ENV=production and APP_DEBUG=false (the installer writes both)
• HTTPS on the domain, detected automatically from the address you open
• Email provider connected and a test email delivered
• Bank identity details checked: UID, LEI, BIC, clearing number, regulator
• Demo bindings for FX, crypto custody, stocks and cards replaced by real providers
• Switched to Production under Tenant and go-live only when ready for real customers
• Database and .env backed up

You are never on your own with a Biply script.