Additional Document Scan
🪪 Additional Document Scan Workflow – REL-ID IDV SDK
This document explains the end-to-end process and API interactions involved in performing an Additional Document Scan using the REL-ID IDV SDK.
🎯 Purpose
The Additional Document Scan feature enables the mobile app to request and capture a secondary identity document from a logged-in user. This may be required in scenarios such as:
- Multi-document KYC
- Policy-based re-verification
- Additional compliance or audit steps
🔄 Workflow (Step-by-Step)
- ✅ User logs in to the mobile app.
- 📲 App calls
initiateIDVAdditionalDocumentScan(reason)to trigger the scan. - 🔔 SDK triggers event
getIDVDocumentScanProcessStartConfirmation. - 🖼️ App displays a prompt explaining why the document is required and shows a Start button.
- 👆 User taps Start.
- 📤 App responds using
setIDVDocumentScanProcessStartConfirmation(true, workflow). - 📸 SDK launches scanner and captures the document.
- 🧠 SDK performs OCR and extracts document details.
- 📥 SDK triggers
getIDVConfirmDocumentDetailswith OCR data. - 🧾 App shows the extracted fields for user review (e.g., Name, DOB).
- 👤 User taps Confirm or Rescan:
- If Confirm:
setIDVConfirmDocumentDetails(true, mode) - If Rescan:
setIDVConfirmDocumentDetails(false, mode)
- If Confirm:
- ✅ SDK triggers
onIDVAdditionalDocumentScanwith the final results. - 🟢 App displays success screen or proceeds to the next step.
flowchart TD
userLogsIn[User Logs In] --> onUserLoggedIn[SDK triggers onUserLoggedIn]
onUserLoggedIn --> initiateIDVAdditionalDocumentScan[App calls initiateIDVAdditionalDocumentScan]
initiateIDVAdditionalDocumentScan --> getIDVDocumentScanProcessStartConfirmation[SDK triggers getIDVDocumentScanProcessStartConfirmation]
getIDVDocumentScanProcessStartConfirmation --> setIDVDocumentScanProcessStartConfirmation[App calls setIDVDocumentScanProcessStartConfirmation]
setIDVDocumentScanProcessStartConfirmation --> initiateDocCapture[SDK initiates Document Capture]
initiateDocCapture --> scanDoc[User scans Document]
scanDoc --> onIDVAdditionalDocumentScan[SDK triggers onIDVAdditionalDocumentScan]
%% Success Callback Styling
style onUserLoggedIn fill:#d4fdd4,stroke:#228b22,stroke-width:2px
style getIDVDocumentScanProcessStartConfirmation fill:#d4fdd4,stroke:#228b22,stroke-width:2px
style onIDVAdditionalDocumentScan fill:#d4fdd4,stroke:#228b22,stroke-width:2px
%% App-Initiated Call Styling
style initiateIDVAdditionalDocumentScan fill:#ffe4b3,stroke:#ff8c00,stroke-width:2px
style setIDVDocumentScanProcessStartConfirmation fill:#ffe4b3,stroke:#ff8c00,stroke-width:2px
🟩 Green - Callbacks issued by REL-ID SDK
🟧 Orange - APIs invoked by the Client App
📦 APIs Involved
| API / Event | Purpose |
|---|---|
initiateIDVAdditionalDocumentScan | Triggers the scan |
getIDVDocumentScanProcessStartConfirmation | Requests user consent |
setIDVDocumentScanProcessStartConfirmation | Launches scanner if user agrees |
getIDVConfirmDocumentDetails | Returns extracted document fields |
setIDVConfirmDocumentDetails | Confirms or cancels the extracted data |
onIDVAdditionalDocumentScan | Final data delivery after confirmation |
🧾 Example Screen Content
- “Please scan your secondary identity proof”
- “Ensure the document is in focus and readable”
- Buttons:
- ✅ “Start Scan”
- 🔁 “Rescan”
- ✔️ “Confirm”
🧠 Notes
- This flow is available only after user login.
- The
challengeModein this flow is typically11. - The final result is received via the
onIDVAdditionalDocumentScanevent.
Updated 5 months ago
