Document Verification Setup

Before You Start

Make sure you have the following:

Execution Flow

Predictive DocV runs as an enrichment step in a RiskOS™ workflow. Because document capture happens on the consumer's device, the workflow pauses at the Document Request step and resumes automatically once capture finishes.

flowchart LR
    A[Input] --> B[Document Request]
    B -. user handoff .-> C[Capture App]
    C --> D[Document Verification]
    D --> E[Conditional Decision Logic]
    E --> F[Decision]

1. Input — You call the Evaluation API with PII and optional DocV config.
2. Document Request — The workflow pauses and returns a URL / QR / token (or sends SMS if enabled) for user handoff to the DocV Capture App.
3. Document Verification — After the consumer completes capture, the workflow resumes, verifies the images, and returns DocV results.
4. Image Request (optional but recommended) — Retrieves captured images and attaches them to the case in RiskOS™.
5. Conditional Decision Logic — Routes based on the DocV decision, reason codes, document type, and other signals.
6. Decision — Emits the final outcome (accept, reject, resubmit, review, or cancel).

📘

Note:

After Document Request, the workflow stays paused until the end user acts (opens the link/QR/SMS and completes capture) or the Document Request expires. There is no API to “force-continue” — RiskOS™ automatically resumes at Document Verification once capture finishes or the session expires.

Add DocV to a Workflow

1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
2. On the workflow canvas, select the plus (+) icon.
3. Add a Document Request enrichment step, then add a Document Verification enrichment step.
4. (Recommended) Add an Image Request enrichment step to attach captured images to the case.
5. Add Conditional Decision Logic and a Decision step to route on the DocV outputs.

After the enrichment is added, its outputs are available to all downstream workflow components.

📘

Note:

If your account has multiple DocV flows, there is typically an enrichment step for each flow (for example, Socure Document Request - Default Flow, Socure Document Request - No Selfie).

Required and Optional Inputs

DocV evaluates the consumer information provided through your workflow. Providing complete and accurate inputs improves extraction matching and verification confidence.

Required Inputs

• data.individual.given_name — Consumer's first/given name
• data.individual.family_name — Consumer's last/family name
• data.individual.phone_number — Phone number in E.164 format
• data.individual.address.country — Country code in ISO 3166-1 alpha-2 format

Optional Supporting Inputs

When available, include these fields to improve match accuracy and verification confidence:

• data.individual.date_of_birth
• data.individual.email
• data.individual.address.line_1
• data.individual.address.locality
• data.individual.address.major_admin_division
• data.individual.address.postal_code
• data.individual.docv.config — Capture App behavior (language, send_message, redirect, document_type, use_case_key)

Omitting optional fields does not prevent execution, but extracted documentData is compared to input PII, so richer inputs strengthen the result.

Workflow Components Used by DocV

Common Decision Patterns

DocV returns a module decision plus reason codes rather than a numeric risk score. Use documentVerification.decision.value in conditions and decision rules to route evaluations. The following patterns are common starting points — adjust them to match your organization's fraud policy and risk tolerance.

Decision-Based Routing

Attribute-Based Routing

Error Handling

Errors can occur on the Document Request and Document Verification enrichment steps. Configure error handling in the workflow for these fields:

• socure_doc_request_error is set
• socure_docv_error is set

Common configurations:

• On error, route to resubmit and add integration logic to initiate a new evaluation request.
• On error, route to cancel and add integration logic to troubleshoot and initiate a new evaluation request.
• Tag the case (for example, docv_error, docv_request_error, docv_verification_error) for filtering and reporting.

Resubmit Handling

A resubmit decision typically means a captured image prevented verification — a quality issue or a disallowed ID type, not necessarily fraud. Start a new evaluation so the consumer receives a fresh DocV transaction to recapture their images.

Recommendations:

• Tailor the consumer messaging based on the returned reasonCodes (for example, use a different ID type, retake in brighter light).
• Limit the number of retry attempts to avoid endless loops.
• For streamlined re-attempt flows or policy nuances, contact your Solutions Consultant team.

Save and Publish

Once your workflow is configured, publish it to go live. After publishing, capture the workflow identifier you pass as workflow on the Evaluation API request.

Workflow Testing Checklist

Use this checklist to confirm accuracy, resilience, and completeness before going live.

Related Enrichments

Related Concepts

• Socure Hosted UX (Capture App)
• Enrichment Step
• Condition Step
• Decision Step
• Configuring Decision Logic

Helpful Links