Skip to content
Pricing
Log InStart Free TrialBook a Demo
Risk & Detection

Verdict Engine

A verdict engine is the decisioning layer that turns raw signals and risk scores into a concrete outcome such as allow, deny, or review. It is where measurement ends and action begins, applying policy to the evidence collected about a visitor.

How it works

How Verdict Engine works

A verdict engine consumes the outputs of the detection stack, identification results, confidence and risk scores, and individual signals, and evaluates them against a set of rules or a policy model. The result is a discrete verdict: permit the action, block it, or route it to an intermediate path such as a challenge or manual review.

Policies inside the engine typically combine thresholds with context. A rule might block when the risk score exceeds a limit and the visitor is unrecognized, but only challenge when the score is high yet the device is a trusted returning one. Good engines let teams express these conditions explicitly so that the reasoning behind a verdict is auditable rather than opaque.

Because a verdict drives a user-facing consequence, latency and consistency are critical. The engine must produce the same decision for the same inputs and do so fast enough to sit inline with a login, checkout, or signup without adding perceptible delay. Many designs also emit the reasons behind a verdict so downstream systems can log, review, or override it.

Why it matters

Why Verdict Engine matters for fraud prevention

Detection is only valuable if it changes what happens next, and the verdict engine is the component that closes that loop. Centralizing decisioning keeps policy consistent across every entry point, makes it easy to tune sensitivity in one place, and produces an auditable trail of why each user was allowed, blocked, or challenged. Without it, scores and signals are just data with no enforcement.

With TRACIO

How TRACIO handles it

TRACIO deliberately returns rich signals and scores rather than a single black-box verdict, so the decisioning policy lives with the customer where it can reflect their own risk appetite and appeals process. Teams build their verdict logic on top of the visitor ID, confidence score, Suspect Score, and the 24 Smart Signals, using webhooks and the API to act on outcomes in real time within the platform's sub-50ms P95 latency budget.

Related reading

Explore further

FAQ

Frequently asked questions

Identify every device with confidence

Start with a free plan of 2,500 API calls per month. No credit card required.