DocV + Watchlist

Overview

This solution combines Document Verification and Watchlist screening into a single onboarding flow.

It enables you to:

Together, these capabilities help you verify identities and enforce compliance during onboarding.

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 DocV and Watchlist screening complete.
Document capture An evaluation_paused status indicates Document Verification is required. Extract the docvTransactionToken from the response to launch the Capture App.
Watchlist screening After document verification completes, RiskOS™ screens verified identities against global sanctions, PEP, and adverse media lists before returning the final decision.

Integration path

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

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.
  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, completes Document Verification, and runs Watchlist Screening.
  8. RiskOS™ delivers the final decision via evaluation_completed webhook.
  9. Route the user:
    • ACCEPT → Continue onboarding
    • REJECT → Stop or route to fallback flow
SocureYour PlatformEnd UserSocureYour PlatformEnd UserExtract docvTransactionToken from responseProcess DocV + Watchlist screeningSubmit 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:

Next steps

[Start a new evaluation

Collect PII, configure DocV settings, and create an evaluation.](https://help.socure.com/riskos/docs/document-verification-watchlist-screening-start-an-evaluation)

[Handle DocV and final decision

Launch the DocV, process webhook events, and route users based on the final decision.](https://help.socure.com/riskos/docs/document-verification-watchlist-screening-handle-additional-verification)

[API Reference

Explore endpoints, request formats, and response schemas.](https://help.socure.com/riskos/reference/postevaluation)