rMIB — Risk Management Intelligence Bureau — links trading, client, partner and payment signals into scored, explained cases for human review. Brokerage first; gaming is a planned adaptation.
Exposure and trading-pattern analysis across accounts, groups and instruments.
Clusters and timing patterns flagged for review — the kind rule-based alerts tend to miss.
Promotion abuse, partner and affiliate anomalies, payment-risk signals.
Behavioural clustering, anomaly detection and AI risk scoring with reasons a risk officer can act on.
Overnight, new accounts from one affiliate show near-identical trade timing on latency-sensitive instruments.
rMIB links trading events, account profiles and deposits, scores the cluster as probable toxic flow and raises one case with the explanation. The dealing desk reviews it, decides on execution settings for the group, and the decision is logged.
People decide on one explained case instead of reconciling separate alerts; the pattern is kept for review.
Trading events from rMarket or your platform; account data; payment events.
rMIB reads trading, account and payment events and writes scored cases to the people and workflows that act on them. It needs trading events; account and payment data sharpen the scoring.
Trading activity and execution history — native.
Client and player profiles, KYC and lifecycle state.
Payment events for payment-risk signals — native.
Trading, account and payment data through API or import.
The demo is rMIB Brokerage on your signal sources: connect trading and account data, set thresholds and routing, review the first scored cases.
rMIB Gaming is a planned adaptation of the same approach for sports betting and gaming risk. There is no gaming demo; the demo below is rMIB Brokerage.
A rMIB Brokerage environment.
Signal sources, scoring thresholds, alert routing and user roles.
Configuration and connected sources when production is activated.
A business email and company details. Trading and account data through rMarket or your API.