Fraud Detection · Documentation

How to Use This Demo

Driving Fraud Detection in the host, the Cloud/OSS inspector, and the operator console — with honest labels.

Fraud Detection
  1. 1

    Signing in + the risk queue

    The ecosystem is gated — sign in as the universal owner (admin / admin@123) or the read-only viewer; an unauthorized visitor sees only the sign-in card. Open Fraud Detection from the launcher; it mounts in the operator console. Risk signals are ranked by score, highest first; filter by disposition or a minimum score to focus on the riskiest.

  2. 2

    Score, disposition + escalate

    Open a signal to see its score and the rules that fired. You can re-score a booking (the dark inspector shows the stage's mode and cost; the surface shows the score and reasons). The owner sets a disposition — open, hold, cleared, or escalated — and can escalate a confirmed signal, which auto-opens a linked fraud-reversal case in the refund/dispute app (#21). Disposition changes and escalations are owner-only and audited.

How to Use This Demo · Fraud Detection · Abhishek Saxena