Fraud Investigation Engine reference profile.
For an alerted account or transaction, is this confirmed fraud, and what case disposition and recovery actions should follow?
Overview
Speeds the case investigation workflow after a fraud alert, reducing investigator time per case.
Who owns this decision
Head of Fraud Operations, Chief Risk Officer
What this Specialist Model actually does
Decision: For an alerted account or transaction, is this confirmed fraud, and what case disposition and recovery actions should follow?
The final taxonomy records 5 supporting or external components, but it doesn't promote an Oumi-owned specialist model for this engine.
Who uses this Specialist Model
- Head of Fraud Operations
- Chief Risk Officer
- VP Payments Risk
- Director of Fraud Investigations
Where the specialist model sits
The final taxonomy records 5 supporting or external components, but it doesn't promote an Oumi-owned specialist model for this engine.
Case-assembly layer pulling transaction, account, device, and prior-alert data into a unified case file
Supporting component
How Oumi connects to your stack →
Rules engine encoding payment-rail recovery windows and network chargeback rules
Supporting component
How Oumi connects to your stack →
Human investigator review and final disposition as the decision gate
Supporting component
Graph model
Supporting component
Graph model for connected-account and mule-network detection
Specialist LLM
Supporting component
Specialist LLM for case summary generation and evidence citation
How to evaluate and improve it
Evaluation
- Disposition precision against confirmed investigator outcomes
- Recovery value per investigated case
- Connected-account detection precision and recall
Feedback signals
- Investigator disposition on the case (confirmed, unfounded, inconclusive)
- Recovery outcome (funds recovered, chargeback won or lost)
- Cases where a connected-account flag was later confirmed or dismissed
- Investigator override of the recommended action
- Time from alert to case closure


