## Overview

This solution uses DocV to verify user identities through government ID scans and biometric selfie capture in a single onboarding flow.

It enables you to:

- Capture and verify government-issued identity documents
- Match the document holder through biometric selfie verification
- Extract identity data directly from verified documents

Together, these capabilities help you verify user identities with high confidence while reducing manual review.

## Key behaviors

| Behavior | Detail |
| --- | --- |
| **Decision delivery** | The initial API response pauses the evaluation for document capture. The final decision is delivered asynchronously via `evaluation_completed` webhook after Document Verification completes. |
| **Document capture** | An `evaluation_paused` status indicates Document Verification is required. Extract the `docvTransactionToken` from the response to launch the [Capture App](https://help.socure.com/riskos/docs/capture-app). |

## Integration path

This solution uses the Direct API integration, where your application owns the onboarding experience end to end.

- Collect and submit user data via API
- Full control over user experience and data handling
- Launch the Document Verification Capture App from your frontend
- Final decision delivered via webhook after document capture completes

## End-to-end flow

1. Set up your backend environment and configure API keys.
2. Collect user identity data (PII) on your custom frontend.
3. Create an evaluation (`POST /api/evaluation`) with PII and DocV settings.
4. RiskOS™ pauses the evaluation (`eval_status: evaluation_paused`) and returns a `docvTransactionToken` used to launch the Capture App via SDK or redirect.
5. Launch the DocV Web SDK or redirect to the Capture App URL.
6. The user completes government ID capture and selfie verification.
7. RiskOS™ resumes the evaluation and completes Document Verification.
8. RiskOS™ delivers the final decision via `evaluation_completed` webhook.
9. Route the user:
   - `ACCEPT` → Continue onboarding
   - `REJECT` → Stop or route to fallback flow
   - Retry behavior: DocV runs once per evaluation. If the session fails (for example, expired, declined, or resubmit), you must create a new evaluation to retry.

```
SocureYour PlatformEnd UserSocureYour PlatformEnd UserExtract docvTransactionToken from responseProcess Document VerificationSubmit PII via signup form1POST /api/evaluation with PII and DocV settings2evaluation_paused + docvTransactionToken3Launch DocV SDK (Capture App)4Submit document images and selfie5Webhook: evaluation_completed (ACCEPT / REJECT)6Show final onboarding result7
```

## Evaluation processing

During the Direct API flow, RiskOS™ orchestrates multiple products and verification steps:

- **Document Verification**: Verifies user identity through government-issued ID scan and biometric selfie capture.
- **Fraud detection**: Catches fake IDs, deepfakes, and stolen documents.