What are RiskOS™ Workflows?

RiskOS™ workflows automate decision-making for risk management and fraud detection. You can create and customize multiple workflows to support different strategies and use cases such as bank account verification, account takeover (ATO) prevention, and payment transaction screening.

Once published, a workflow orchestrates how an event is evaluated—from initial data intake to a final decision.

How it works

1. Define your use case

   Start by identifying the business scenario your workflow should support (e.g., identity verification, fraud detection, compliance checks). A clear use case ensures the workflow structure aligns with real-world needs.

2. Build your workflow

   Use the Workflow Editor in RiskOS™ to visually build and customize workflows by adding steps—the core building blocks that determine how evaluations are processed.

   
   

   Each step represents an action or logic that moves an event closer to a decision. Steps can be chained to collect, enrich, transform, and analyze data before producing an outcome.

   
   

   Common step types:

   
   

   • Input: Captures applicant-provided data at the beginning of the workflow.
   • Enrichment: Pulls in additional data from Socure or third-party services to enhance decisioning.
   • Transformations: Manipulates and transforms data in the flow with spreadsheet-like functions.
   • Conditions: Applies logic to determine whether an event continues, is flagged, or modified.
   • Decision: Finalizes the outcome by automatically approving, declining, or routing for manual review.

   
   

   You can mix and match step types to fit your use case—whether identity verification, transaction risk assessment, or fraud detection. See Build Your Workflow for more detail.

3. Evaluate an event

   When a workflow is published and live, it evaluates incoming events in real time via the /api/evaluation API.

   
   

   • Each step executes sequentially.
   • Conditions and rules are applied to decide whether the event should be (usually) Accepted, Rejected, or flagged for Review.
   • Events may also be placed On Hold if more information is required (e.g., pending Document Verification or One-Time Password input).

   
   

   Evaluation outcomes are visible in the Cases section of the workbench.

4. Manual review

   If a workflow cannot clearly approve or decline an event, it can be routed for Manual Review.

   
   

   • Reviewers open cases in the Case Management view.
   • A case remains Open or On Hold until the reviewer completes the decision.
   • Reviewers can override, approve, or decline as needed.

   
   

   See Case Management for details on reviewer tools and workflows.

Next steps