The Akoben Platform
Akoben receives transaction events from payment switches, core banking systems and mobile wallets, evaluates each event against configurable fraud rules and behavioural indicators, produces a risk decision, and routes anything suspicious into an investigator workflow with a complete audit trail.
The platform is organised into five modules.
Platform modules
- Transaction Monitoring — continuous evaluation of payment, wallet, card and bank transaction flows.
- Fraud Prevention — real-time scoring and decisioning before a transaction completes.
- Fraud Rules Engine — thresholds, velocity, behavioural and account conditions.
- Case Management — alert triage, assignment, investigation, escalation and resolution.
- Analytics & Reporting — fraud trends, alert volumes and operational performance metrics.
- How Akoben Works — the end-to-end path a transaction takes through the system.
Common questions
What does the Akoben platform do?
Akoben receives transaction events from payment switches, core banking systems and mobile wallets. Each event is evaluated against configurable fraud rules and behavioural indicators to produce a risk decision. A transaction that breaches a rule raises an alert, which is routed into a case queue where an investigator can triage, assign, investigate, escalate and resolve it. Every step in that process is recorded to an audit trail.
Case management carries an alert from triage through assignment, investigation, escalation and resolution. Analytics and reporting summarises the resulting fraud trends and alert volumes as operational performance metrics.
The transaction monitoring, fraud prevention, fraud rules engine, case management, and analytics and reporting modules are described in full on their own pages, linked below.
How does Akoben's fraud rules engine work?
The fraud rules engine evaluates each transaction against custom rules and thresholds. A rule checks transaction attributes such as amount and velocity, alongside device, account and behavioural checks, comparing each against the condition the rule sets. When a transaction matches a rule's condition, the platform produces a risk decision for that transaction. A transaction that breaches a rule generates an alert, which is routed into the case management module's queue, where an investigator can triage, assign, investigate, escalate and resolve it.
A rule's condition can reference a fixed threshold, a transaction's velocity, the device or account associated with it, or a behavioural check. The rules engine evaluates each incoming transaction against these conditions to produce a decision for that transaction.
A transaction that breaches a rule's condition generates an alert. That alert appears in the case management module's queue, where an investigator triages, assigns, investigates, escalates and resolves it.
Discuss your transaction monitoring requirements
Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.
Request a demo