Troubleshooting and FAQs

Yes. DocV V5 SDKs support per-transaction localization of default UI text (including Terms & Conditions). Set the desired language in your server-side Evaluation request config (see Q7).

Highlights

• Supports: English, Spanish (multiple variants), French, Simplified/Traditional Chinese, Haitian Creole, Italian, Korean, Polish, Russian, Tagalog, Urdu, Vietnamese, Arabic, Armenian, Bengali, Brazilian Portuguese, Hindi, Japanese, German, and more.
• Default: If you don’t pass a language, en-us is used.
• Custom UI text: If you override copy in the Admin Dashboard, provide your own translations for that custom text.

For the full list and locale codes, see your Language Options page.

Yes. Support for 16 KB page sizes is included starting with Android SDK v5.1.1. If you’re on an older version, upgrade to ≥ v5.1.1 to maintain compliance with Google’s latest requirements.

Yes. The DocV SDKs guide users and apply immediate quality checks (e.g., framing, glare/blur, document presence) before submitting to backend verification. Users may be prompted to retake images to improve quality and reduce downstream failures/abandonment.

• You’ll receive a case note webhook (case_notes_added) with Session Expired when the link validity window passes.
• Expired links are time-bound and single-session. To let the user try again, issue a new document request (typically by creating a new Evaluation so a fresh docvTransactionToken and link are generated).
• If you must tie attempts back to the same business record, include your own external transaction ID in the id field of the Evaluation.

For progress/event webhooks vs final results, see your Webhooks page (DocV Event Webhooks vs Evaluation Completed).

A resubmit decision is returned when the images don’t meet minimum criteria (e.g., unreadable text, missing side/back, glare/blur).

Recommended handling:

• Treat resubmit as non-terminal. Prompt the user to recapture by issuing a new document request (fresh link/token).
• Consider rate-limiting attempts and providing tips (good lighting, remove cases/covers, avoid glare).

• Flows & branding: Use useCaseKey to select a customized Capture App flow you’ve configured in the Dashboard (branding, steps, copy).
• Skip screens:
  • Document type selection: Skip by passing documentType (e.g., license, passport).
  • Splash/intro: Often configurable in the Dashboard flow.
• Consent/T&Cs: Must be presented within DocV for compliance. You may show additional disclosures in your own onboarding/handoff page, but the DocV consent screen itself is not removable.

In DocV V5, configuration is server-side only. You pass all options when you create the Evaluation. The SDK launch on the client only needs the docvTransactionToken and SDK key.

Common options (server-side, in your Evaluation request):

• language — UI locale for the Capture App (default en-us)
• useCaseKey — choose a specific flow configured in the Dashboard
• sendMessage — true to send the capture link via SMS
• redirect — { method: "POST" | "GET", url: "https://…" } after completion/cancel
• documentType — restrict to a single type (e.g., license, passport)

Example (JSON)

{
  "id": "your-transaction-id-123",
  "timestamp": "2025-07-31T15:00:10.761Z",
  "workflow": "consumer_onboarding",
  "data": {
    "individual": {
      "given_name": "Jane",
      "family_name": "Doe",
      "phone_number": "+19999998888",
      "docv": {
        "config": {
          "language": "en-us",
          "useCaseKey": "my_custom_flow",
          "sendMessage": true,
          "redirect": {
            "method": "POST",
            "url": "https://example.com/docv/callback"
          },
          "documentType": "license"
        }
      }
    }
  }
}

What the client gets
Your backend receives an Evaluation response with a DocV link/QR/token at the Document Request step. You then hand that to the client to launch the SDK or hosted capture.