Verdict reads your transaction files, scores each one for fraud, and shows you the reasons behind the number — plus how suspicious transactions relate to each other. No black box.
Most fraud tools hand you a number and ask you to trust it. Verdict hands you the number and the reasoning — every time, on your own data, in language a reviewer and an auditor can both follow.
Weights, thresholds, rules, and denylists are editable data, not engineering tickets. Tune Verdict to your portfolio and your risk appetite, then change your mind tomorrow.
Five scoring lenses, BIN and decline-code enrichment, and relationship analysis that links a single bad actor across merchants — the work that catches organized fraud, not just one-off declines.
Each score returns its top contributing factors in words: “card seen across three merchants in two minutes,” not an opaque probability. Reviewers act faster when they can see the reasoning.
Every run records the model and ruleset versions that produced it. Re-run later and you get the same verdict — the audit trail is built in, not bolted on.
Each engine examines a different dimension of risk. Their signals are combined into one explained score, with each engine's contribution shown — so you always know which lens drove the call.
Your own logic, authored as editable data. The conditions you know matter for your portfolio.
Normalizes raw processor decline codes into a fraud taxonomy, so an issuer’s “do not honor” carries weight.
Links transactions that share a card, email, or device across merchants — the fingerprint of organized fraud.
Learns what normal looks like per merchant, then flags the transactions that break the pattern.
Known-bad entities set a minimum band. An analyst’s confirmed-fraud label becomes tomorrow’s automatic catch.
Drop a file at the API, the portal, or a watched folder. Verdict does the rest and hands back scored, explained, exportable results.
Upload a CSV or XLSX — by API, portal, or scheduled drop folder. Columns map to a canonical model automatically.
Each row gets BIN reference data and a normalized decline class. No full card numbers stored.
Five engines run, producing a score, a band, and the factors behind them — plus ring analysis across the batch.
Triage in the portal, export to CSV/XLSX, and watch the portfolio trend build run over run.
Verdict scores and explains. It never touches money — and that design choice keeps it out of the heavy regulation that would otherwise apply, so you can put it to work without a compliance marathon.
The same API powers the portal, your integrations, and the drop-folder watcher. Wire it up once; feed it however you like.
Push files over HTTP, let analysts upload in the portal, or have a processor drop them in a watched folder. Same pipeline, same verdicts.
Immutable, per-run, tenant-scoped reports: summary, flagged, rings, declines, and a rolling portfolio trend.
Scoring profiles, rulesets, and denylists are first-class API objects. Calibrate per tenant; reproduce any run on demand.
Verdict is rolling out to payments teams now. Tell us about your company and your stack, and we’ll set you up with a scoped trial on your own files.