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[]
  1. The workflow reaches an Enrichment step.
  2. RiskOS™ calls the configured data service with the relevant payload fields.
  3. The service returns structured results (scores, codes, attributes).
  4. Results are stored in the data_enrichments array of the evaluation response.
  5. 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:

FieldDescription
enrichment_nameName of the enrichment/product
enrichment_endpointAPI endpoint called
enrichment_providerSocure or partner service
requestPayload sent to the enrichment
responseFull response returned, including scores and reason codes

Enrichment categories

CategoryEnrichmentsWhat they provide
Identity verificationVerify, Verify Plus, Prefill, eCBSV, Deceased CheckKYC data, SSN verification, identity attributes
Document verificationPredictive DocVGovernment ID capture and verification
Device & behavioralDigital Intelligence, Account IntelligenceDevice fingerprinting, behavioral signals, bank account verification
Fraud detectionSigma Identity Fraud, Sigma Synthetic Fraud, Sigma First-Party FraudML-based fraud scores and reason codes
Risk scoringAddress Risk, Email Risk, Phone Risk, Graph IntelligencePII attribute risk scores and identity correlation
ComplianceWatchlistSanctions, PEP, and adverse media screening
User verificationOTP, CNAMContact information verification
PartnerMiddesk, Experian, Thomson Reuters Clear, and othersThird-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

ConceptScopeExample
EnrichmentThe data service that is calledSigma Identity Fraud
SignalA discrete data point returned by an enrichmentsigma_identity_fraud.score = 0.92

An enrichment produces multiple signals. Signals are the inputs to rules and conditions.


Related concepts