Foreign exchange & Multi-Asset Buying and selling for Bicrypto
A leveraged dealing desk, constructed into your Bicrypto set up. Clients open a buying and selling account, fund it from their platform pockets, and commerce foreign exchange pairs, gold and silver, crude oil, index ETFs, US equities and a small set of crypto CFDs from one terminal — with actual streaming costs, actual margin, server-side cease loss and take revenue, trailing stops, in a single day swap costs and session calendars.
Please learn first: that is an add-on
Foreign exchange & Multi-Asset Buying and selling is an extension for Bicrypto, a separate product bought individually on CodeCanyon. It doesn’t run by itself. It has no standalone installer, no interface of its personal outdoors the Bicrypto admin panel and no database of its personal — it makes use of core’s customers, KYC, wallets, transactions, notification templates, permissions and cron runner. A working, licensed Bicrypto set up is a tough prerequisite.
No different add-on is required. Particularly it does not want the Ecosystem add-on and it does not use ScyllaDB — in contrast to Ecosystem and Futures, all the things right here lives in MySQL. It additionally has no relationship with the older Foreign exchange Funding add-on: that product sells managed funding plans and by no means executes an order, this one is the buying and selling engine. They set up aspect by aspect.
Please learn: it’s essential to deliver a market-data account, and it’s not included
A market-data supplier account with a streaming (WebSocket) entitlement is required. The terminal quotes from a WebSocket and from nothing else — there is no such thing as a REST polling fallback wherever on this add-on. With out one, credentials confirm, costs render as soon as, and each single order is refused with “Pricing is quickly unavailable for this instrument”.
You purchase that account from the seller at their revealed worth and so they invoice you immediately; nothing is metered by way of this merchandise. 4 distributors are supported, and the admin Suppliers display states which plans truly stream, what every prices, and lets a key be examined — together with the stream — earlier than you decide to it. Not one of the distributors’ revealed costs features a redistribution licence, which is a query value placing to them first.
Optionally, for those who would slightly hedge than carry the danger, the A-book layer wants an OANDA or MetaTrader dealer account. Additionally yours to acquire, additionally billed by them, and off till you flip it on. The MetaApi route moreover wants your dealer’s written approval for datacenter logins.
Please learn: operating a dealing desk is a licensed exercise
This add-on offers you the equipment. It doesn’t offer you permission. Providing leveraged contracts for distinction to retail purchasers requires authorisation within the EU, the UK, Australia, Japan, Singapore and lots of different jurisdictions, and is successfully closed to offshore operators in america and Canada — which is why the geo-block listing ships with US, CA already populated.
Establishing that you could be lawfully supply this product, to whom, and on what phrases, is your accountability earlier than you’re taking a single order. Nothing right here is authorized recommendation.
How a commerce truly works
- A worth arrives. One market-data supplier is lively at a time. Its WebSocket streams bid/ask ticks into the tick engine, which stamps every image
QUOTING,QUOTING_HALTED(the feed went stale) orSESSION_CLOSED(the trading-hours calendar says the market is shut). - The desk widens it. The instrument’s image group carries a ramification markup in pips. Half is added to the ask and half subtracted from the bid, so a buyer shopping for pays your worth, not the feed’s. That distinction is your income on each fill.
- The order is checked. Instrument lifecycle, session state, quoting state, delayed-data coverage, minimal and most dimension, stops distance, and — for market orders — a hedge-aware free-margin calculation folding within the account tier’s leverage cap and any margin already reserved.
- It fills immediately. Buys on the marked-up ask, sells on the marked-up bid. A place row is created and an immutable deal is written to the ledger.
By default you’re the counterparty — that’s the B-book mannequin and it’s what the add-on ships as. When a buyer income, that cash leaves your steadiness sheet. The optionally available A-book layer helps you to push some or all of that threat out to an actual dealer as an alternative.
What you get
- An actual buying and selling terminal — markets rail with dwell bid, ask and day change; candle chart; order ticket with market, restrict, cease and stop-limit; a positions and orders dock with account totals. Plus a cell workspace, a guided tutorial and a apply account funded with paper cash.
- Margin and leverage — per-tier leverage caps, hedged margin charges, margin name and stop-out ranges, adverse steadiness safety.
- Server-side threat orders — cease loss, take revenue and trailing stops enforced by the engine, not the browser.
- Devices and image teams — foreign exchange, metals, power, indices, equities and crypto CFDs, every with contract dimension, pip and level dimension, digits, stops stage, quantity and value limits, unfold markup, fee per lot, swap lengthy/quick and a swap-free choice.
- Session calendars — weekly schedules with breaks, holidays and early closes, per image group.
- An operator threat desk — dwell internet publicity per instrument break up by inside versus hedged, e book protection, operator floating P&L, accounts close to stop-out, and unresolved execution alerts.
- A-book execution — routing guidelines by instrument, group, account, aspect and dimension; an in-flight panel; a watchdog; and a foundation/income view of what hedging truly price.
- Account tiers and IB rebates — tiered leverage and circumstances, and introducing-broker rebates paid from unfold income.
- Financial calendar and market information, funding out and in of the platform pockets, full deal ledger, and admin screens for each considered one of them.
Technical necessities
All of that is what Bicrypto core already requires. The add-on itself introduces no new npm dependency — the market-data and dealer adapters are plain fetch and WebSocket purchasers, not vendor SDKs — so putting in it doesn’t change the dependency tree of your set up.
Platform
- Bicrypto core, put in, licensed and operating. No different add-on required.
- Linux. Ubuntu 24.04 LTS or newer, or one other distribution transport glibc 2.38+ (Debian 13+, RHEL / Rocky / Alma 10+). Ubuntu 22.04 won’t run the platform. x86-64 or ARM64, glibc — not Alpine or musl.
- Not shared PHP internet hosting. A operating set up is long-lived Node.js processes behind a reverse proxy.
Runtime
- Node.js 22, 24 or 26. No different main model boots — the platform’s HTTP server is a prebuilt native binary and ships these three ABIs solely.
- pnpm — the platform pins
[email protected]. npm and yarn can’t resolve the workspace. - 4 GB RAM minimal, 8 GB to construct the frontend reliably. 2+ CPU cores. Shell entry, and the flexibility to restart the backend.
- The platform’s cron course of have to be operating — swaps, session rollovers and the execution watchdog are scheduled jobs.
Database and companies
- MySQL 8.0+ or MariaDB 10.6+, reachable, with the
mysqlshopper obtainable on the appliance server. The add-on’s tables are created by the platform’s replace command; no current schema is modified. - Redis, reachable and answering
PING— a tough dependency of Bicrypto, not a cache. - ScyllaDB will not be used. No search server and no message dealer are required both.
API dependencies
- Required: a market-data supplier account on a plan with a streaming WebSocket entitlement, and outbound WebSocket plus HTTPS out of your server to it. That is the one third-party service the product can’t run with out, and it’s purchased from and billed by that vendor. See the part above.
- Optionally available: a dealer account at OANDA or a MetaTrader dealer, provided that you allow A-book execution. Its credential is the one setting variable the add-on reads —
APP_OANDA_API_KEYorAPP_METAAPI_TOKEN— and each are documented within the.env.instanceshipped within the package deal. - Market-data credentials are not setting variables: they’re entered and stream-tested on the admin Suppliers display.
What’s within the obtain
- Full supply code. The backend as TypeScript (146 information, together with an operator runbook) and the terminal plus the operator desk as TypeScript and React (92 information). No compiled-only code and no obfuscation.
- Documentation — 26 pages of offline HTML masking set up, market-data suppliers, devices and periods, the terminal, operating the desk, A-book execution, account tiers, IB rebates, deployment topology, each setting, the API reference and troubleshooting, plus three customer-facing assist pages. Open
documentation/index.htmlin any browser. - A commented
.env.instancemasking each optionally available dealer credentials and explaining the place the market-data key truly goes. - A mission manifest, a changelog masking all seven releases, a licence file, and a small script that compiles the shipped supply right into a manufacturing set up.
Assist
- Documentation: mashdiv.com/docs/forex-multi-asset-trading
- Assist: mashdiv.com/support

