Forex & Multi-Asset Trading for Bicrypto

A leveraged dealing desk, built into your Bicrypto install. Customers open a trading account, fund it from their platform wallet, and trade forex pairs, gold and silver, crude oil, index ETFs, US equities and a small set of crypto CFDs from one terminal — with real streaming prices, real margin, server-side stop loss and take profit, trailing stops, overnight swap charges and session calendars.

Please read first: this is an add-on

Forex & Multi-Asset Trading is an extension for Bicrypto, a separate product sold separately on CodeCanyon. It does not run on its own. It has no standalone installer, no interface of its own outside the Bicrypto admin panel and no database of its own — it uses core’s users, KYC, wallets, transactions, notification templates, permissions and cron runner. A working, licensed Bicrypto install is a hard prerequisite.

No other add-on is required. In particular it does not need the Ecosystem add-on and it does not use ScyllaDB — unlike Ecosystem and Futures, everything here lives in MySQL. It also has no relationship with the older Forex Investment add-on: that product sells managed investment plans and never executes an order, this one is the trading engine. They install side by side.

Please read: you must bring a market-data account, and it is not included

A market-data provider account with a streaming (WebSocket) entitlement is required. The terminal quotes from a WebSocket and from nothing else — there is no REST polling fallback anywhere in this add-on. Without one, credentials verify, prices render once, and every single order is refused with “Pricing is temporarily unavailable for this instrument”.

You buy that account from the vendor at their published price and they bill you directly; nothing is metered through this item. Four vendors are supported, and the admin Providers screen states which plans actually stream, what each costs, and lets a key be tested — including the stream — before you commit to it. None of the vendors’ published prices includes a redistribution licence, which is a question worth putting to them first.

Optionally, if you would rather hedge than carry the risk, the A-book layer needs an OANDA or MetaTrader broker account. Also yours to obtain, also billed by them, and off until you turn it on. The MetaApi route additionally needs your broker’s written approval for datacenter logins.

Please read: running a dealing desk is a licensed activity

This add-on gives you the machinery. It does not give you permission. Offering leveraged contracts for difference to retail clients requires authorisation in the EU, the UK, Australia, Japan, Singapore and many other jurisdictions, and is effectively closed to offshore operators in the United States and Canada — which is why the geo-block list ships with US, CA already populated.

Establishing that you may lawfully offer this product, to whom, and on what terms, is your responsibility before you take a single order. Nothing here is legal advice.

How a trade actually works

A price arrives. One market-data provider is active at a time. Its WebSocket streams bid/ask ticks into the tick engine, which stamps each symbol QUOTING, QUOTING_HALTED (the feed went stale) or SESSION_CLOSED (the trading-hours calendar says the market is shut).
The desk widens it. The instrument’s symbol group carries a spread markup in pips. Half is added to the ask and half subtracted from the bid, so a customer buying pays your price, not the feed’s. That difference is your revenue on every fill.
The order is checked. Instrument lifecycle, session state, quoting state, delayed-data policy, minimum and maximum size, stops distance, and — for market orders — a hedge-aware free-margin calculation folding in the account tier’s leverage cap and any margin already reserved.
It fills instantly. Buys at the marked-up ask, sells at the marked-up bid. A position row is created and an immutable deal is written to the ledger.

By default you are the counterparty — that is the B-book model and it is what the add-on ships as. When a customer profits, that money leaves your balance sheet. The optional A-book layer lets you push some or all of that risk out to a real broker instead.

What you get

A real trading terminal — markets rail with live bid, ask and day change; candle chart; order ticket with market, limit, stop and stop-limit; a positions and orders dock with account totals. Plus a mobile workspace, a guided tutorial and a practice account funded with paper money.
Margin and leverage — per-tier leverage caps, hedged margin rates, margin call and stop-out levels, negative balance protection.
Server-side risk orders — stop loss, take profit and trailing stops enforced by the engine, not the browser.
Instruments and symbol groups — forex, metals, energy, indices, equities and crypto CFDs, each with contract size, pip and point size, digits, stops level, volume and cost limits, spread markup, commission per lot, swap long/short and a swap-free option.
Session calendars — weekly schedules with breaks, holidays and early closes, per symbol group.
An operator risk desk — live net exposure per instrument split by internal versus hedged, book coverage, operator floating P&L, accounts near stop-out, and unresolved execution alerts.
A-book execution — routing rules by instrument, group, account, side and size; an in-flight panel; a watchdog; and a basis/revenue view of what hedging actually cost.
Account tiers and IB rebates — tiered leverage and conditions, and introducing-broker rebates paid from spread revenue.
Economic calendar and market news, funding in and out of the platform wallet, full deal ledger, and admin screens for every one of them.

Technical requirements

All of this is what Bicrypto core already requires. The add-on itself introduces no new npm dependency — the market-data and broker adapters are plain fetch and WebSocket clients, not vendor SDKs — so installing it does not change the dependency tree of your installation.

Platform

Bicrypto core, installed, licensed and running. No other add-on required.
Linux. Ubuntu 24.04 LTS or newer, or another distribution shipping glibc 2.38+ (Debian 13+, RHEL / Rocky / Alma 10+). Ubuntu 22.04 will not run the platform. x86-64 or ARM64, glibc — not Alpine or musl.
Not shared PHP hosting. A running install is long-lived Node.js processes behind a reverse proxy.

Runtime

Node.js 22, 24 or 26. No other major version boots — the platform’s HTTP server is a prebuilt native binary and ships those three ABIs only.
pnpm — the platform pins pnpm@10.28.0. npm and yarn cannot resolve the workspace.
4 GB RAM minimum, 8 GB to build the frontend reliably. 2+ CPU cores. Shell access, and the ability to restart the backend.
The platform’s cron process must be running — swaps, session rollovers and the execution watchdog are scheduled jobs.

Database and services

MySQL 8.0+ or MariaDB 10.6+, reachable, with the mysql client available on the application server. The add-on’s tables are created by the platform’s update command; no existing schema is modified.
Redis, reachable and answering PING — a hard dependency of Bicrypto, not a cache.
ScyllaDB is not used. No search server and no message broker are required either.

API dependencies

Required: a market-data provider account on a plan with a streaming WebSocket entitlement, and outbound WebSocket plus HTTPS from your server to it. This is the one third-party service the product cannot run without, and it is bought from and billed by that vendor. See the section above.
Optional: a broker account at OANDA or a MetaTrader broker, only if you enable A-book execution. Its credential is the only environment variable the add-on reads — APP_OANDA_API_KEY or APP_METAAPI_TOKEN — and both are documented in the .env.example shipped in the package.
Market-data credentials are not environment variables: they are entered and stream-tested on the admin Providers screen.

What is in the download

Full source code. The backend as TypeScript (146 files, including an operator runbook) and the terminal plus the operator desk as TypeScript and React (92 files). No compiled-only code and no obfuscation.
Documentation — 26 pages of offline HTML covering installation, market-data providers, instruments and sessions, the terminal, running the desk, A-book execution, account tiers, IB rebates, deployment topology, every setting, the API reference and troubleshooting, plus three customer-facing help pages. Open documentation/index.html in any browser.
A commented .env.example covering both optional broker credentials and explaining where the market-data key actually goes.
A project manifest, a changelog covering all seven releases, a licence file, and a small script that compiles the shipped source into a production installation.

Support

Documentation: mashdiv.com/docs/forex-multi-asset-trading
Support: mashdiv.com/support

Forex & Stocks Trading for Bicrypto - Multi-Asset CFD Desk, Leverage & Margin Engine Addon