MMashDiv

Forex Investment

The managed forex investment addon — plans, durations, MetaTrader accounts, signals and automated settlement. What it is, what it needs, how the money moves, and which product it is not.

6 min readUpdated 6 August 2026forex, investment, plans, metatrader, settlement

Forex Investment sells managed investment plans. A customer funds a forex account from their platform wallet, picks a plan and a duration, and collects a return when the term ends. They never place an order, never see a spread and never hold a position. You configure what the plan pays, and the platform pays it on schedule.

Two separate products carry the word forex, and they do completely different things.

  • Forex Investment (this one, store slug forex, backend extension forex) — capital in, yield out. Plans, durations, settlement.
  • Forex & Multi-Asset Trading (slug forex-multi-asset-trading, extension forex_trading) — a live dealing desk with streaming prices, margin, stop loss and take profit.

They share no tables, no routes and no admin screens. Installing one does not give you the other, and configuring the wrong one is the single most common support ticket on either. If your customers should be placing orders, you want the other product.

What it requires

    • Bicrypto core, installed and running — see Installing Bicrypto
    • The forex extension activated and enabled at /admin/system/extension
    • The platform cron running, so processForexInvestments can settle
    • At least one FIAT or SPOT currency your customers already hold in a wallet

Nothing else. This addon does not need Ecosystem, does not need ScyllaDB, and does not need an exchange connection — although a plan denominated in a SPOT currency reads its percentage fee from your exchange currency table.

How the money actually moves

Four balances are involved, and only one of them is the customer's ordinary wallet. Getting the order of these right is the whole product:

  1. Wallet → forex account. The customer deposits. This settles immediately — there is no approval step. The wallet gives up the amount plus the fee, the forex account is credited the amount, and the fee goes to the platform.

  2. Forex account → investment. The customer picks a plan and a duration. The principal leaves the forex account the moment the investment is created.

  3. Investment → forex account. When the end date passes, the hourly settlement cron pays the result back into the same forex account the principal came from. A win returns principal plus profit; a loss returns principal minus the loss; a draw returns the principal.

  4. Forex account → wallet. The customer withdraws. This is the only way money leaves the product, and it requires an admin decision. The forex account is debited at submission and the wallet is credited only when you approve.

Submitting a withdrawal debits the customer's forex account straight away. The wallet is not credited until an admin approves it, and the forex account is not made whole until an admin rejects it. Until one of those happens the money exists nowhere and a person is waiting for it. Work that queue — /admin/forex/withdraw — daily. The platform scores it against a seven-day target and the admin dashboard shows you the age of the oldest item waiting.

Outcomes are configured, not traded

There is no market feed behind an investment. When the term ends, settlement takes the result from the investment's own result column if an admin set one, and otherwise from the plan's Default Result — WIN, LOSS or DRAW. The size of the movement is the plan's profit percentage applied to the principal.

That means a plan advertised at 15% with a default result of WIN pays every investor 15% of their principal, every time, forever, out of your balance sheet. Read Plans and durations before you publish a single plan, and decide deliberately what you are promising.

Every settled investment books the platform's side of the outcome — the payout on a win, the retained principal on a loss — so the addon's real contribution to profit and loss is visible per currency rather than being inferred from deposit and withdrawal fees alone.

What your customers see

The user area lives at /forex and appears in the main navigation under Investments → Forex Investments.

/forex — the public landing page: headline statistics, featured plans, six months of settled performance and the active signals.

/forex/plan — every enabled plan, filterable and sortable by popularity, profit or minimum investment.

/forex/dashboard — their DEMO and LIVE accounts, with Deposit, Withdraw and Trade buttons.

/forex/investment — active and completed investments, each with its plan, duration, end date and result.

/forex/transaction — forex deposits and withdrawals only.

/forex/trade/{id} — the MetaTrader web terminal, embedded with the account's broker server and login.

The Trade screen is worth understanding before you sell it. It embeds the public MetaTrader WebTerminal (trade.mql5.com for an MT5 account, metatraderweb.app otherwise) using the broker name and account ID you stored on the account row, and shows the customer their credentials. The platform does not talk to your broker. It hands over a login. If the account details you entered are wrong, the terminal simply will not connect — see Accounts.

What you administer

The admin area is at /admin/forex, reached from Admin → Extensions → Investment Products → Forex Broker & Investments. It has eight screens: a dashboard, accounts, plans, durations, investments, signals, and the deposit and withdrawal queues. There is no settings screen — everything is configured on the plan, the duration or the account row itself, and the Extensions page is the on/off switch.

Install and enable

Activation, the seven tables, the 36 permission keys, the KYC gates and the settlement cron.

Plans and durations

What each field on a plan does, which two decide what you pay out, and the validation that stops you publishing a dead plan.

Accounts

DEMO and LIVE, the pre-provisioned account pool, MetaTrader credentials, currency binding and withdrawal caps.

Investments

The full lifecycle from creation to settlement, including refunds, cancellation and recovery.

Signals

What a signal is in this product, how it reaches an account, and the one write path that assigns it.

The admin screens

Reading the dashboard, and what each table can and cannot do.

Deposits and withdrawals

The two money queues — approval, rejection, reversal and the guards around deletion.

Pre-provisioning the account pool

The unowned rows customers claim on first visit, why the admin form cannot create one, and what never to seed on it.

Revenue and referral rewards

The three admin-profit entry types, why a customer win is a platform loss, and the affiliate condition settlement fires.

API reference

Every endpoint with its permission, the tables, and the enums.

Emails and notifications

The five templates, the three in-app notifications, which ones never fire, and where they are edited.

If something is not behaving, start at Troubleshooting — most reports come down to four causes, and three of them are configuration.