RuseTect · live payment path (L1 + L2)Live Console

Engine: checking…
Replay of recorded IBM AMLworld test period payments (synthetic dataset)sim time: waiting
Scored0payments through the cascade
L1 cleared0approved by gatekeeper
L2 escalated0sent to XGBoost + LightGBM
Verify / hold0OTP recheck or analyst hold
Block + STR0auto blocked, STR drafted
L4 cases0mule clusters to review
n/aprecision of blocks vs. ground truth
n/alaundering payments blocked
0 / 0caught / laundering seen
0false blocks
n/amedian latency per payment
L-1 lure detector · scam message or call transcript
Alert budget: nothing scored yet
Paste an SMS, WhatsApp message or call transcript. The model scores it, names the scam workflow and tactics, and decides whether the user should be interrupted. A payment that follows a risky message is escalated.
Alert feed · newest firstground truth label shown for the demo only
Load account history, then stream payments. Blocks and holds appear here with the reasons the model gave.
L4 ring linker · largest cases
Cases form when blocked payments share accounts.
L0 onboarding gate · new account applications (Feedzai BAF, test months)
Two held out applications from the synthetic Feedzai BAF dataset. One is labelled fraud, one genuine. The model sees neither label.