Finstek News

Product updates, release notes, and company announcements, all in one place.

Two screens. One case. Funding and exposure in Risk Manager: a deposit row and the exposure spike it precedes, joined as one case

12 October 2026productrisk-manager

Unusual funding and unusual trading are the same investigation

Deposit and withdrawal monitoring sits beside exposure in Risk Manager, so a funding pattern and a trading pattern can be read as one investigation.

Seven conditions. Four actions. Routing inside The Edge: a routing rule with its conditions, its actions and a configurable delay range

9 September 2026productthe-edge

Execution routing that lives inside the trading platform

Seven conditions, four actions and a configurable execution delay, built into The Edge. Routing control without necessarily adding a separate bridge.

Paid there. Pending here. A status job per provider, in the Back Office and CRM: a deposit pending here marked paid by the status job

2 September 2026productback-office

Sixty-five payment providers is not the number that matters

Sixty-five providers integrated directly, per-country control of what each market sees, and a status-checking job per provider so states reconcile.

Before your client tells you. 77 operational alerts in the Liquidity Bridge: a feed delay alert firing, with the trading day and out-of-hours schedule

26 August 2026productliquidity-bridge

The bridge should tell you before your client tells you

Feed and trade disconnections, failover switchover, price spikes, feed delay and dozens more, each schedulable so out-of-hours differs from the trading day.

Four servers. One number. The Real-Time Vault in Risk Manager: four trading servers summed into one net exposure row

19 August 2026productrisk-manager

One exposure screen for a book that sits on four servers

Net and gross exposure, profit and loss and open positions from every connected trading server, aggregated into one screen a dealing desk can act on.

Who was supposed to be watching? Document expiry monitoring in the Back Office and CRM: a client document at its expiry date, with the notice going to the client and the compliance officer

13 August 2026productback-officecompliance

An expired client document is an operations problem first

Expired client documents surface at the worst moment. How automated expiry monitoring notifies both the client and the compliance officer before the deadline.