Glossary

Definitions of the core RiskOS™ platform terms — evaluations, workflows, enrichments, signals, decisions, cases, and more.

This glossary defines the core terms you'll encounter across RiskOS™ documentation. For a conceptual walkthrough of how these pieces fit together, see Understanding RiskOS™.


Core platform terms

TermDefinition
EvaluationA single execution of a workflow — the runtime unit of work in RiskOS™. Every identity, fraud, or compliance check is an evaluation. See Evaluations.
WorkflowA configurable sequence of steps that processes an evaluation, from data intake through enrichments and rules to a decision. See Workflows.
EnrichmentA data service (also called a product) that adds risk, identity, or compliance signals to an evaluation. See Enrichments.
SignalA discrete data point returned by an enrichment and used in decisioning (for example, a risk score or match result). See Signals & Attributes.
AttributeAn input data point describing the entity being evaluated (name, DOB, SSN, email, phone, device data), sent in the evaluation request.
Reason codeA human-readable code that explains why an evaluation received a particular outcome. Reason codes are explanations, not decision inputs.
TagA metadata label conditionally attached to an evaluation for filtering, automation, and analytics.
Derived valueA value computed by a workflow step from attributes, signals, or other derived values.
DecisionThe final outcome of an evaluation: ACCEPT, REJECT, or REVIEW. See Decisions.
CaseThe record created when an evaluation routes to manual review. See Cases & Manual Review.
StepA single building block in a workflow (for example, an Input, Enrichment, Condition, or Decision step).

Product tiers

TermDefinition
Socure LaunchThe self-service RiskOS™ tier. Create a Sandbox account and start integrating without a sales process. Each solution runs a pre-configured, non-editable workflow with Socure-recommended thresholds. Doesn't include First-Party Fraud, OTP, or eCBSV. Production usage is billed per evaluation, with $1,000 in free credits monthly. See Solutions for Startups Overview.
Socure EnterpriseThe full RiskOS™ platform tier. Build and configure custom workflows from scratch in the Workflow Editor, with access to the full enrichment catalog (including First-Party Fraud, OTP, and eCBSV) and configurable thresholds. Requires a contract and typically has minimum commitments.
📘

Note:

Both tiers run the same evaluation engine and return the same response payload — the difference is workflow configurability and module access, not the underlying platform. See Solutions for Startups FAQs for how to move from Launch to Enterprise.


Workflow delivery terms

TermDefinition
Custom workflowA workflow built and managed by the customer in the Workflow Editor.
Hosted FlowA preconfigured workflow with a Socure-managed end-user UI (also called Socure Hosted UX). See Hosted Flows.
Workflow EditorThe visual workflow builder in the RiskOS™ Dashboard.

Status and lifecycle terms

TermDefinition
StateThe runtime position of an evaluation (for example, evaluation_in_progress, evaluation_paused, evaluation_completed).
StatusThe lifecycle position of a case (Open, On Hold, Closed). See Statuses & Lifecycle.
LifecycleThe full sequence of state and status transitions an evaluation or case moves through.
PausedAn evaluation runtime state in which the workflow is waiting for user action (distinct from the "On Hold" case status).

Decision values

Decision values are returned as uppercase codes in the API response:

ValueMeaning
ACCEPTThe entity passed all checks.
REJECTThe entity failed one or more checks.
REVIEWThe evaluation requires human assessment.

RESUBMIT and CANCEL are Decision Rules step configuration values, not standard API decision values.


Integration terms

TermDefinition
Evaluation APIThe POST /api/evaluation endpoint used to run an evaluation.
SandboxThe non-production RiskOS™ environment for testing.
ProductionThe live RiskOS™ environment.
WebhookAn HTTPS POST notification RiskOS™ sends to deliver asynchronous results.
data_enrichmentsThe API response field containing enrichment results.
SDK keyThe client-side credential used by mobile and web SDKs.
API keyThe server-side credential used for API authentication.

Related topics


Did this page help you?