Yourbank

A banking platform for any country. Customers and businesses use one app; the owner runs everything from an administrator console. Every rule is enforced on the server.

The same files work on a domain, a subdomain or a folder. The installer starts by itself the first time you open the address.

Choose where it lives

• Domain or subdomain (best). Point the domain or a subdomain such as bank.yourdomain.com at the public folder, then open the address.
• Subfolder (yourdomain.com/bank). Upload the whole folder next to your site and make https://yourdomain.com/bank serve the public folder (a symlink or an alias). Open /bank/install; the app detects the folder by itself.
• cPanel without access to the document root. Upload the project above public_html (for example /home/user/bank), put the contents of public into public_html/bank, and edit the two paths in public_html/bank/index.php so they point to ../../bank/vendor/autoload.php and ../../bank/bootstrap/app.php.

Run the installer

1. Upload and extract

   In cPanel File Manager, upload the zip and press Extract.

2. Set the PHP version

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

3. Make folders writable

   Give storage and bootstrap/cache write permission.

4. Open the address

   The installer checks the server, then asks for the database, bank name, country, brand colour and the administrator login. It writes .env for you, including APP_KEY and a separate SECRETS_KEY that encrypts provider keys.

5. Add the cron job

   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/bank/artisan schedule:run >> /dev/null 2>&1

6. Sign in

   Sign in with the administrator you just created.

BANK_COUNTRY in .env selects a country pack: NG, GH, KE, ZA, GB, US or DE (euro area). It sets the base currency, account number format, bills catalogue, identity levels and provider shortlist. Add your own pack by copying one in config/countries.php. Customers can also hold wallets in other currencies.

Every part works by itself in test mode. For real money, connect providers under Administrator, Integrations.

Keys are stored encrypted and never shown again. Customers never see which provider you use.

Switch in Settings, Go live when your provider keys are live and your company details are filled in. You can switch back at any time and existing data is never touched. Test API keys work only in test mode, live keys only in live mode; they can never mix.

• Company details and support email filled in
• Payment, payout, identity and email providers connected and tested in their sandboxes
• A test transfer, a test card payment through the gateway and a webhook delivered
• Cron job running
• APP_KEY, SECRETS_KEY and the database backed up
• HTTPS on the domain

A business creates a checkout, sends the customer to the hosted page, and is told by a signed webhook when it is paid. Money lands in the business account at once, minus the gateway fee you set. Keys are created in Developers, API keys; writes need an Idempotency-Key; webhooks are HMAC-SHA256 signed and retried with back-off. The full reference ships with the script in docs/gateway-api.md, and the partner API for fintechs in docs/partner-api.md.

• Bank name, country and brand colour are set during installation. The app runs in light or dark mode.
• Fees and pricing rules are in the administrator console; the gateway fee is under Settings, Payments and fees.
• Identity review is manual by default; connect Smile ID or Sumsub to automate it.
• Need a matching public website, extra providers or new products? Request a quote.

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

The scheduler retries webhooks, collects loan instalments, matures deposits and runs the nightly integrity check.

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, the .env file and your APP_KEY and SECRETS_KEY regularly. Keep a copy of the storage folder as well. To update, upload the new files over the old ones, then run php artisan migrate --force.

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.

No software is 100% secure. What is built in, and what you must still do, is written out in docs/security.md.

• Every movement is one balanced, immutable double-entry journal entry. Amounts are whole numbers in minor units.
• Payments, refunds, loan repayments and transfers are idempotent: a webhook delivered twice never moves money twice.
• Provider keys are encrypted at rest and removed from logs. Webhooks are signature-checked and re-checked with the provider before money is credited.
• Two-step sign-in (TOTP), per-account lockout, login history, and a strict Content-Security-Policy.

You are never on your own with a Biply script.