Fraud Review Queue

Review suspicious transactions with risk signals, customer history, device context, rules triggered, evidence, and approve or block decisions. This example brings Queue and High risk together so finance and operations teams can find the next task without losing context.

It includes representative records such as Card payment · unusual location and Rapid account payout. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Fraud Review Queue
Use this template in Figr

Template facts

Screen

Inbox

Primary action

Review next

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to review next while keeping waiting, high risk and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Queue gives users an obvious place to start.
  • Supporting view: High risk keeps the related context close.
  • Primary action: Review next stays visible when people need it.
  • First signal: Waiting shows a useful value (34).
  • Second signal: High risk gives additional context (8).
  • Sample record: Card payment · unusual location.
  • Next record: Rapid account payout.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Queue → High risk → Review next → Review outcome

Patterns used

Inbox, Queue, High risk, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to queue and high risk. People need to distinguish Card payment · unusual location from Rapid account payout. Keep waiting visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Review next”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Accounting Close, Tax Documents, Vendor Payments.

Start from this in Figr

Design a fraud review queue screen inside our existing product. Use our current components, tokens and content language. Include Queue and High risk views, credible records like Card payment · unusual location, and a clear “Review next” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr