Enrichments
An enrichment is a data service that adds risk, identity, and compliance signals to an evaluation beyond the data in the initial request.
An enrichment is a data service that supplements an evaluation with additional risk, identity, and compliance signals beyond the data provided in the initial API request. Enrichments are also referred to as products in the RiskOS™ platform.
During workflow execution, an Enrichment step calls a Socure product or third-party API to retrieve structured data — scores, reason codes, attributes, and validation results. The workflow then uses these signals in downstream rules and conditions to reach a decision.
How enrichments work
sequenceDiagram
participant App as Your Application
participant RiskOS as RiskOS™
participant Svc as Data Service
App->>RiskOS: POST /api/evaluation (PII + workflow)
RiskOS->>RiskOS: Run Input step
RiskOS->>Svc: Call enrichment (e.g., Phone Risk)
Svc-->>RiskOS: Return scores, reason codes, attributes
RiskOS->>RiskOS: Apply rules using enrichment signals
RiskOS->>RiskOS: Reach decision
RiskOS-->>App: Return decision + data_enrichments[]
- The workflow reaches an Enrichment step.
- RiskOS™ calls the configured data service with the relevant payload fields.
- The service returns structured results (scores, codes, attributes).
- RiskOS™ stores the results in the
data_enrichmentsarray of the evaluation response. - Downstream steps (Conditions, Rule Scorecards, Decisions) reference these results.
How RiskOS™ selects which enrichments run
Your workflow — not the evaluation request — determines which enrichments run and which appear in the data_enrichments array. The request carries the PII and configuration an enrichment needs, but it cannot add, remove, or filter enrichments.
- To change which enrichments run, edit the workflow in the RiskOS™ Dashboard.
- Because selection is workflow-driven, Sandbox and Production return the same set of enrichments for the same workflow. The same workflow returns the same
data_enrichments, so the response does not narrow based on what you send. See Enrichment Error Handling.
Migrating from ID+?Configure enrichments in the workflow rather than per evaluation. The ID+
decisionmodule is replaced by the top-leveldecisionfield, set by the workflow's Decision step. To trace which reason codes drove a decision, see Interpret a Decline.
Enrichment categories
| Category | Enrichments | What they provide |
|---|---|---|
| Identity verification | Verify, Verify Plus, Prefill, eCBSV, Deceased Check | KYC data, SSN verification, identity attributes |
| Document verification | Predictive DocV | Government ID capture and verification |
| Device & behavioral | Digital Intelligence, Account Intelligence | Device fingerprinting, behavioral signals, bank account verification |
| Fraud detection | Sigma Identity Fraud, Sigma Synthetic Fraud, Sigma First-Party Fraud | ML-based fraud scores and reason codes |
| Risk scoring | Address Risk, Email Risk, Phone Risk, Graph Intelligence | PII attribute risk scores and identity correlation |
| Compliance | Watchlist | Sanctions, PEP, and adverse media screening |
| User verification | OTP, CNAM | Contact information verification |
| Partner | Partner Ecosystem | Third-party data services |
Enrichments vs signals
| Concept | Scope | Example |
|---|---|---|
| Enrichment | The data service that the workflow calls | Sigma Identity Fraud |
| Signal | A discrete data point returned by an enrichment | sigma_identity_fraud.score = 0.92 |
An enrichment produces multiple signals. Signals are the inputs to rules and conditions.
Related topics
- Enrichments Overview — The full enrichment catalog with integration guides
- Reason Codes & Score Interpretation — How to read enrichment scores and reason codes
- Enrichment Error Handling — Handling enrichment failures
- Signals & Attributes — The data taxonomy enrichments feed into
Updated 18 days ago