What are Enrichments?
Learn how enrichment steps call Socure products and third-party APIs to add identity, risk, and compliance data to every evaluation.
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).
- Results are stored in the
data_enrichmentsarray of the evaluation response. - Downstream steps (Conditions, Rule Scorecards, Decisions) reference these results.
Where enrichment results appear in the API
Enrichment results are returned in the data_enrichments array of the evaluation response. Each entry represents a single enrichment call:
| Field | Description |
|---|---|
enrichment_name | Name of the enrichment/product |
enrichment_endpoint | API endpoint called |
enrichment_provider | Socure or partner service |
request | Payload sent to the enrichment |
response | Full response returned, including scores and reason codes |
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 | Middesk, Experian, Thomson Reuters Clear, and others | Third-party data services |
For the complete enrichment catalog with integration guides, see Enrichments Overview.
Error handling
If an enrichment call fails, RiskOS™ retries up to three times (2,000 ms max per attempt). On final failure:
- The enrichment output is set to
null. - Downstream Condition steps referencing the failed enrichment evaluate to
false. - You can configure fallback Enrichment steps to chain alternative providers.
For error handling details, see Enrichment Error Handling.
Enrichments vs signals
| Concept | Scope | Example |
|---|---|---|
| Enrichment | The data service that is called | 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 concepts
- Evaluations — The execution context for enrichments
- Workflows — Where Enrichment steps are configured
- Signals & Attributes — The data taxonomy: signals, reason codes, tags, and derived values
- Rules & Conditions — How enrichment signals drive decisions
- Decisions — The outcomes that enrichment signals drive toward
- Statuses & Lifecycle — Evaluation states during enrichment execution
- Terminology Governance — "Enrichment" not "product" or "module" in technical docs
- Enrichments Overview — Full catalog and integration guides
- Workflow Steps: Enrichment — Enrichment step configuration reference
Updated 3 days ago
