DocV + Watchlist

Combine document verification with global sanctions screening in RiskOS™ to verify identities and enforce compliance during onboarding.

Start building

Overview

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

It enables you to:

  • Verify user identity through government ID scans and biometric selfie capture
  • Screen users against global sanctions, PEP, and adverse media lists

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


Key behaviors

BehaviorDetail
Decision deliveryThe 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 captureAn evaluation_paused status indicates Document Verification is required. Extract the docvTransactionToken from the response to launch the Capture App.
Watchlist screeningAfter 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.

  • 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 and watchlist screening complete

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

sequenceDiagram
    autonumber
    participant User as End User
    participant App as Your Platform
    participant Socure as Socure

    User->>App: Submit PII via signup form
    App->>Socure: POST /api/evaluation with PII and DocV settings
    Socure-->>App: evaluation_paused + docvTransactionToken

    Note over App: Extract docvTransactionToken from response
    App-->>User: Launch DocV SDK (Capture App)
    User->>Socure: Submit document images and selfie

    activate Socure
    Note over Socure: Process DocV + Watchlist screening
    Socure-->>App: Webhook: evaluation_completed (ACCEPT / REJECT)
    deactivate Socure

    App-->>User: Show final onboarding result

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.

Watchlist screening

Screens verified identities against global sanctions, PEP, and adverse media lists.


Next steps