Transaction Fraud Engine reference profile.
Approve, challenge, hold, or decline a transaction.
Overview
Reduce fraud loss.
Who owns this decision
Chief Risk Officer, Head of Fraud
What this Specialist Model actually does
Decision: Approve, challenge, hold, or decline a transaction.
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
- Chief Risk Officer
- Head of Fraud
- VP Payments Risk
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.
Rules engine
Supporting component
Rules engine for hard controls
How Oumi connects to your stack →
Real-time tabular model
Supporting component
How Oumi connects to your stack →
Graph model
Supporting component
Graph model for connected entities
How Oumi connects to your stack →
Sequence model
Supporting component
Sequence model for behavioral history
How Oumi connects to your stack →
Specialist LLM
Supporting component
Specialist LLM for investigator explanation
How to evaluate and improve it
Feedback signals
- Chargeback outcome
- Customer fraud confirmation
- Authentication outcome
- Manual review decision
- Merchant termination
- Funds recovery
- False decline complaint


