- H2O Driverless AI builds time series models that predict expected transaction volume, with upper and lower bounds for every interval.
- Live volume is compared against the forecast in real time, and your operations or fraud team is alerted the moment it moves outside the expected range.
- The same approach finds unusual activity inside the data, such as a sudden burst of transactions from one device, merchant or account group.
- Every flagged anomaly comes with reason codes, so your analysts can see which factors made a record unusual.
You find out from your customers first
Your mobile app and payment services are where customers check balances, pay bills and resolve issues. When a service slows down or fails, customers move to the call center, transactions are lost, and some customers leave.
Fixed thresholds do not know that Monday morning looks different from Sunday night, or that payday looks different from the rest of the month. They either alert all the time, or stay quiet until the problem is already visible to customers.
How anomaly detection works
Step 1: Collect the volume history
Start with transaction counts and values by channel, product and time interval, from your payment and digital banking systems. Add calendar effects such as paydays, holidays and month end.
Step 2: Forecast what normal looks like
H2O Driverless AI trains time series models that forecast expected volume for each interval, and predicts upper and lower bounds from how much volume usually varies.
Step 3: Compare live volume with the forecast
Real time volume is scored against the expected range. When volume spikes above the upper bound or falls below the lower bound, your network, operations or fraud team gets an alert and can act before customers notice.
Step 4: Look inside the anomaly
Anomaly detection models look for unusual records inside the volume: a group of accounts, a device or a merchant that behaves unlike its peers. Reason codes show your analysts which factors made a record unusual.
Step 5: Keep the baseline current
Retrain the models as your volumes and channels change, and track model drift so the baseline stays accurate.
Where this fits your fraud program
Unusual volume is also a fraud signal. A sudden change in payment patterns is often the first sign that something is wrong, and the same anomaly models that catch service problems can flag activity for your fraud team to review, alongside the tools you already run.