FAQs

DocV links are single-use. If the flow completes or times out, re-clicking the link will show “Session Expired” for security.

The DocV SDK also incorporates Socure’s Digital Intelligence SDK, which collects additional device signals such as device metadata and behavioral data.

The Capture App includes multiple on-device checks to help users capture a high-quality image—detecting glare, blur, corners, and face presence before auto-capture.
Server-side validation then performs deeper analysis, including barcode readability, OCR accuracy, and image classification.

If an image fails these checks, the app prompts targeted retakes to correct the specific issue. Users are given up to three attempts.
After three unsuccessful attempts, the app allows the user to continue. This is intentional—to minimize friction and avoid trapping users in an endless retake loop.
Even if the image quality is suboptimal, DocV’s decisioning process will still evaluate it and determine the final outcome (accepted, resubmitted, or rejected).

In short: The system prioritizes guidance and quality but ultimately balances user experience with downstream decision integrity.

When camera permissions are declined, the SDK will not crash; it returns a structured error you can handle:

SocureDocVFailure(
    error: SocureDocV.SocureDocVError.cameraPermissionDeclined,
    deviceSessionToken: Optional("eyJraWQiOiJmMzRiN2YiLCJhbGciOiJIU........kz6r88aPCmg")
)

You can present a user-friendly prompt (e.g., “Camera permission is disabled; enable access in Settings to continue”) and optionally deep-link to settings depending on platform.

Forwarding alone does not trigger a risk code by default. Device/IP mismatches are logged and may reduce confidence, but alerts only fire if custom mismatch or velocity rules are enabled.

Cause
On some devices in low-power mode, the browser overlays a transient “play” icon on video elements. This is device/browser behavior and cannot be disabled.

Impact
The overlay is temporary and does not affect SDK capture or verification.

• Advise end users that the icon is expected and will disappear momentarily.
• Suggest disabling low-power mode if the overlay is distracting.

• Ensure the SDK is initialized with a current, unused token.
• Regenerate a new token if the previous one has expired, been consumed, or invalidated.

• The DocV SDK must reach Socure backend services over HTTPS.
• Review corporate firewall/proxy rules to allow outbound HTTPS traffic.
• Temporarily disable ad-blockers/VPN/content filters that might block SDK scripts or domains.

• End user denied camera permission.
• Browser/device or iframe policies are blocking camera access.

• Ask the user to allow camera access when prompted.
• If you load the Web SDK inside an iframe, include permissive sandbox flags:

<iframe sandbox="allow-same-origin allow-scripts allow-camera"></iframe>

• Chrome
• Safari
• Firefox (mobile supported)

• Serve the page over HTTPS so browsers permit camera usage.
• If using embedded webviews, confirm they support getUserMedia.

While uncommon, some devices may crash or freeze due to OS/browser version, device capabilities, or low memory (RAM/GPU).

• Update the device OS and browser to the latest version.
• Close unused apps and browser tabs to free memory.
• Clear cache and reload the Capture App page.
• Restart the device, then retry the capture flow.

These actions typically resolve device-level issues and allow users to complete verification successfully.

The redirect object instructs the Capture App to send users to a specified URL once they’ve completed uploading their documents. It supports the following fields:

• method
• url
• (optionally) delay in some implementations

Please note that the redirect is purely a UX/navigation feature — it does not deliver verification results.

• Redirect users to a “next step” page in your app (e.g., “Thanks, continue your application”) after document upload completes.
• Pass a branded or context-aware URL (including parameters such as customerUserId) so your app can return users to the correct workflow step.
• For mobile flows, remember that Capture App typically opens in a new tab. Your redirect will occur within that tab. Many teams also use Web SDK options like autoOpen and closeCaptureWindowOnComplete for a smoother UX.

These JavaScript callback methods are defined in the config object passed to SocureDocVSDK.launch(). They're triggered at key points in the document capture flow so your web app can react in real time.

• onProgress(event) – Fires as the user moves through flow stages (e.g., WAITING_FOR_USER_TO_REDIRECT, WAITING_FOR_UPLOAD).
• onSuccess(response) – Fires when document images are uploaded successfully (corresponds to DOCUMENTS_UPLOADED).
• onError(error) – Fires when an error occurs (e.g., CONSENT_DECLINED, DOCUMENTS_UPLOAD_FAILED).

• UI Updates:
  Use onProgress() to show loading indicators, track QR-code or mobile handoff steps, and display success messages after uploads.

• Flow Control:
  After onSuccess(), your app can fetch DocV evaluation results from your backend or advance the user in your onboarding process.

• Mobile Handoff UX:
  Use flags such as closeCaptureWindowOnComplete and autoOpenTabOnMobile to return users smoothly to your main page and show completion confirmation.

“Enable Selfie Auto Capture Interface” turns the selfie step in the DocV Capture App into a guided, automatic selfie capture flow instead of a basic “tap to take photo” flow.

Concretely, when this is enabled:

• The selfie step uses a selfie auto-capture module (labeled SelfieAutoCapture in configs/SDK) rather than the older manual selfie screen.

• The Capture App shows a face box and real-time guidance, with messages like:

  • “Move your phone in front of your face like you’re taking a selfie”
  • “Align your face to the box”
  • “Move closer / move your phone away”
  • “Face must be fully visible / look directly at the camera”

• The SDK continuously analyzes the camera preview and automatically captures the selfie once quality/position conditions are met (instead of requiring the user to press the shutter).

• After auto-capture, the user still sees a confirmation screen with options like Submit / Retake, so they can reject a bad frame before upload.

Net effect for users: more “point and hold” selfie capture, less “aim, tap, and hope the frame is good.”

“Skip splash screen” removes the initial intro screen of the DocV Capture App and drops the user directly into the first actionable step of the flow.

Concretely, when it’s enabled in the DocV flow configuration:

• Users do not see the usual splash/intro page (logo + “Get started” style screen).

• After the link opens, they go straight to:

  • document type selection, or

  • the first capture screen (e.g., “Position your ID”) if you’ve already fixed the document type in the flow.

• Consent / terms screens still appear where required; only the non-essential intro/splash step is removed.

Effectively: it shortens the flow by one tap and makes the experience feel more “immediate” once the user opens the DocV link.