Install and enable

• A working Bicrypto install — see Core install
• Shell access to the app server — pnpm updator runs there, credentials go in .env, and the backend has to be restarted to read them
• A market-data provider account whose plan includes WebSocket streaming
• Decided which countries you will refuse — the geo-block list defaults to US, CA and applies the moment the extension is live

1. Open the Extension Manager. Admin → System → Extension Manager (/admin/system/extension), heading Add-ons & Integrations. On the Extensions tab, or by searching for Forex, find the Forex & Multi-Asset Trading card — product ID 62000000 — and click it. Searching for Forex also turns up Forex Broker & Investments, the card beside it; that is a different product. Until its licence is activated the switch on the card is disabled and reads Activate license first.

   1. The Forex & Multi-Asset Trading card — click it to open the product page
   2. Its switch stays disabled until the licence is activated

2. Activate the licence. On the product page press Activate License. Paste the purchase code from your MashDiv dashboard, optionally an email address for update notifications, and press Activate License. The screen confirms License Activated! and returns you to the product page a couple of seconds later. If the server has no outbound access, the License File tab on the same screen takes the licence certificate downloaded from your MashDiv dashboard instead.

   1. Paste the purchase code here
   2. Activate License — then wait for the redirect back to the product page
   3. The offline route, for a server with no outbound HTTPS

3. Install the release. Back on the product page, now licensed, the Overview tab has a release panel. If it offers Install v…, press it; if it says Up to date on a product you have only just licensed, press Check for Updates once, then install whatever it offers. The Releases tab holds the notes for the version you are being offered — read them first.

   Install downloads the release, verifies it and extracts it over the project root. It runs no migrations, builds nothing and restarts nothing, so finish it from a shell on the server:

   pnpm updator

   That is the finalise chain — stop, dependencies, schema, seed data, frontend build, start — and it is what makes the addon's tables exist. If the panel still says Up to date after the check there is nothing to download; go straight to the next step.

   1. Check for Updates, then Install v… when it is offered
   2. Releases — the notes for the version you are about to install
   3. The Enabled switch — step 4, not yet

4. Switch it on. Turn the Enabled switch on — in the product page heading, or on the card in the Extension Manager, which is usable now that the licence is verified. This is what makes Forex Trading appear under Admin → Extensions, puts the customer terminal at /forex-trading/trade, and registers the six forex_trading scheduled jobs of step 8; none of that needs a restart. The desk itself is different: the tick engine, the risk engine and the reconciler are started when the backend boots and finds the addon on, so the restart step 2 asks for after the market-data key goes into .env is the one that brings them up.

fx_provider              market-data vendors (one active at a time)
fx_execution_provider    A-book hedge venues (many may be enabled)
fx_instrument            the tradable catalog
fx_symbol_group          dealing-desk config per group of symbols
fx_session_calendar      trading-hours calendars
fx_account_group         account tiers (margin call, stop out, NBP)
fx_account               customer trading accounts
fx_order                 orders, market and pending
fx_position              open and closed positions
fx_deal                  the immutable money ledger
fx_routing_rule          A-book placement-time routing overrides
fx_execution_alert       the operator alert inbox
fx_economic_event        economic calendar
fx_market_news           terminal news feed

Every screen is permission-gated on keys of the form view.forex_trading.*, edit.forex_trading.* and so on. Roles ship with no grants at all, so an Admin-role user will get a 403 on every page until you assign them under Users → Roles & Permissions. The full list is in the settings reference.

The A-book execution keys are pre-listed in .env.example. The market-data keys are not — you add them by hand. If you copy the file expecting to find APP_TWELVEDATA_API_KEY and it is absent, that is normal.

APP_TWELVEDATA_API_KEY=
APP_FINNHUB_API_KEY=
APP_TRADERMADE_API_KEY=
APP_POLYGON_API_KEY=

1. Press Import Instrument Catalog

1. Press Import Instrument Catalog

1. Status column — everything starts INACTIVE

1. Leverage — the group's cap
2. Spread markup in pips — your revenue on every fill
3. Commission per lot

1. Trading — the master switch and delayed-instrument policy
2. fxTradingEnabled — turn this on last
3. Risk & Data — quote staleness thresholds
4. Accounts — which account currencies customers may pick
5. Compliance — geo-block list and the risk disclosure

The tick engine, the risk engine, the external execution engine and the reconciler are all single-owner and are arbitrated by a Redis lease named forex-trading. In a clustered or multi-process deployment only the lease holder streams quotes and evaluates stop-out. Other processes serve forex data from the database only. If the leader dies, an operator has to restart the loser — there is no automatic promotion, because tearing down the quote stream on a still-serving process would make it refuse every open and close.

1. Open the terminal as an ordinary user at /forex-trading/trade. A demo account is provisioned automatically on first visit with 10,000 units of paper money in the first configured account currency.

2. Check the markets rail. Instruments should show live prices that move. A symbol showing a badge other than a live price is telling you its quoting state — see Troubleshooting.

3. Place a market buy of the minimum size on EUR/USD. It should fill instantly. Confirm the fill price is worse than the mid — that is your spread markup arriving.

4. Attach a stop loss and a take profit, then move them. Both are validated against the instrument's stops level, so a level too close to the market is refused with the exact distance required.

5. Close the position and open Admin → Forex Trading → Finance → Deals Ledger. You should see an OPEN deal and a CLOSE deal, each carrying the executed price, the raw feed bid and ask, and the balance the account was left with.

6. Leave a position open past 17:00 New York and confirm a SWAP deal appears within the hour. If it does not, the swap cron is not running or a currency conversion leg is missing.

• Provider activated and the stream probe reported success
• Catalog imported; strandedActive empty
• Only the instruments you intend to support are ACTIVE
• Symbol groups reviewed — spread markup, leverage, commission, swap policy
• At least one account group exists, with a defaultForType for LIVE
• Geo-block list saved deliberately (an empty saved list blocks nobody; a deleted row resurrects the US, CA default)
• Risk disclosure decision made
• All six cron jobs green
• fxTradingDelayedStocksTradable left off unless your plan genuinely streams real-time equities
• Notification templates reviewed under Admin → System → Notifications: FxTradingDepositConfirmation, FxTradingWithdrawalStatus, FxTradingMarginCall, FxTradingStopOut
• A Super Admin user exists with a working email — every execution alert fans out to Super Admin holders only
• Then, and only then, fxTradingEnabled on