A project to build with System One models

Suspicious transaction triage, fine-tuned on your own cases

Give every payment a calibrated probability of being suspicious, fine-tuned on your past investigations, and route the risky ones to analysts.

Security and fraudAdvanced4 stepsSuggested by @biplov

The decision

A noul question, "this transaction needs review", over a state built from the transaction and a short account history. It is written as text or JSON: amounts, countries, merchant category, device changes and recent velocity.

How to build it

  1. Export past transactions with their investigation outcomes. Those are your labels.
  2. Fine-tune Laya on them in System One Studio (systemone run studio). It scores the fine-tune against the base on held-out rows before you ship.
  3. Serve it next to your payment flow, and send everything above your threshold to the analyst queue.
  4. Watch precision at the threshold weekly. Fraud patterns drift.

Make it better

Keep a rules engine for the hard constraints, such as sanctions and amount limits, and use the model for the grey zone the rules can't describe.

More projects to build

All projects