DocV Integration Overview

How DocV fits into RiskOS™

DocV is an enrichment that plugs into a RiskOS™ workflow. You never call DocV directly — you call the single RiskOS™ Evaluation API, and the workflow runs DocV as a step. For background on workflows, enrichments, and decisions, see Core Concepts.

Because document capture happens on the consumer's device, DocV is asynchronous: the evaluation pauses while the consumer captures their documents, then resumes and delivers a final decision through a webhook.

The verification lifecycle

Every DocV integration follows the same lifecycle, regardless of flow type or whether you use the SDK or Hosted Flows:

1. Create the evaluation — Your app submits consumer data to the Evaluation API.
2. Receive the launch asset — RiskOS™ pauses the workflow at the Document Request step and returns the launch asset for your path: a docvTransactionToken (SDK) or a top-level redirect_uri (Hosted Flows).
3. Launch verification — Your app hands the consumer off to the SDK or Hosted Flows.
4. The consumer completes capture — The capture experience collects and uploads the required media.
5. The workflow resumes — RiskOS™ continues the evaluation once capture finishes.
6. Receive the result — RiskOS™ delivers the final decision through the evaluation_completed webhook, or you retrieve it with a GET request.
7. Process the final decision — Your app routes the consumer based on the ACCEPT, REVIEW, or REJECT decision.

sequenceDiagram
    participant App as Your App
    participant RiskOS as RiskOS™
    participant DocV as DocV Capture
    participant Consumer

    App->>RiskOS: 1. Create evaluation (PII + DocV config)
    Note right of RiskOS: Workflow pauses at<br/>Document Request step
    RiskOS-->>App: 2. Launch asset (token or redirect_uri)

    App->>DocV: 3. Launch verification (SDK or Hosted)
    DocV->>Consumer: Present capture UI
    Consumer->>DocV: 4. Capture documents / selfie
    DocV->>RiskOS: Submit captured media
    Note right of RiskOS: 5. Workflow resumes

    RiskOS-->>App: 6. Webhook: evaluation_completed
    App->>App: 7. Route consumer on decision

Choose your integration path

You launch the Capture App one of two ways: with an SDK or with Hosted Flows. Both call the same Evaluation API and return results through the same webhooks, but they are distinct integration paths — selected by the workflow you call — and the launch asset you receive back differs by path. Choose a path before you build, then follow its dedicated end-to-end guide: DocV Direct API Integration or Integrate DocV with Hosted Flows.

Supported flow types

DocV supports four Capture App flows. Each follows the lifecycle described earlier in this topic; they differ in what the consumer captures, which docv fields the evaluation request requires, and which enrichment object the result contains. For the per-flow request fields and payload examples, see Configure by DocV product.

Related concepts

• Core Concepts
• Workflows
• Webhooks

Related enrichments

• Selfie Intelligence
• Selfie Reverification
• Secondary Document Capture