Microblink VerifyID Integration Security Checks in Mission Control
This document provides an overview of the Microblink VerifyID security checks and how to interpret their results within the Launch Mobility Mission Control system. This integration enhances our ability to verify driver's licenses, leading to improved security and a more efficient registration process.
When a driver uploads their license through the app, Microblink's VerifyID tool performs a series of automated checks. The outcomes of these checks are then visible in the user's details within Mission Control. Understanding the different statuses and checks will help you interpret the verification results effectively.
Who qualifies: Custom Branded Organizations
Additional Feature: Yes (Contact your CX Team for additional details)
Status of Security Checks
The "Status of Security Check" field provides a general overview of the outcome for a specific Microblink security check. Here's a breakdown of the possible statuses:
- Unknown: The result of the verification is unclear or the system did not recognize the response from Microblink for this specific check. Further investigation might be needed.
- Pass: The specific verification check was successful, indicating that the element being checked meets the required standards.
- Fail: The specific verification check did not meet the required standards, suggesting a potential issue with the license or the extracted data.
- Not Performed: The specific check was not conducted. This could be because the type of driver's license being verified does not support that particular check, or certain preconditions were not met.
Security Checks Description
Security Check |
Description |
Purpose |
Match Check |
Verifies that key fields (name, DOB, ID number) match across different parts of the document (e.g., visual text vs. barcode). |
Detects tampering or mismatched data. |
Logic Check |
Ensures the document follows logical rules (e.g., issue date ≤ expiry date, valid ID format). |
Catches illogical or impossible entries. |
Field Format Check |
Validates that each field (dates, ID numbers) follows the expected format for the document type. |
Flags malformed or invalid data. |
Barcode Authenticity |
Checks if the barcode or MRZ (Machine-Readable Zone) is genuine and matches visible data. |
Detects fake or altered barcodes. |
Suspicious Data Check |
Looks for anomalies (unusual fonts, inconsistent spacing, known fraud patterns). |
Identifies potential forgeries. |
Data Integrity Check |
Confirms all required fields are present and unaltered. |
Ensures no critical data is missing or corrupted. |
Extracted Data Check |
Compares OCR-extracted text with the document’s visual data. |
Prevents OCR errors or hidden tampering. |
Screen Check |
Detects if the document is a digital screenshot (e.g., from a phone/computer). |
Blocks photos of screens instead of physical IDs. |
Photocopy Check |
Identifies if the image is a scanned copy or photocopy. |
Rejects non-original documents. |
Document Liveness Check |
Ensures the document is a real, physical ID (not a printout/digital fake). |
Prevents paper forgeries. |
Photo Forgery Check |
Analyzes the holder’s photo for signs of editing (pasted faces, pixelation). |
Catches manipulated photos. |
Security Features Check |
Verifies holograms, UV patterns, watermarks, or other anti-fraud elements. |
Confirms genuine security features. |
Visual Check |
Assesses overall image quality (sharpness, lighting, glare). |
Ensures the document is clear and readable. |
Version Check |
Validates that the document follows the latest issued format. |
Detects obsolete/outdated IDs. |
Expired Check |
Checks if the document is past its expiry date. |
Rejects invalid/expired IDs. |
Document Validity Check |
Confirms the document is legally valid (not reported lost/stolen). |
Ensures only active IDs are accepted. |
Creating a Detailed Report on Microblink Security Checks
You can generate a detailed report on Microblink security checks within Mission Control by following these steps:
- Create a New Report:
- Click on the "Create Report" button.
- Then, click on the "Create Custom Report" button.
- Select the Report Type:
- Choose Qualification Report as the report type.
- Add Columns to the Report:
- In the next step, add the following columns by navigating through the categories and clicking the "+" icon next to each:
- Categorical → Qualifications → Qualification Label
- Categorical → Requirement → Requirement Label
- Categorical → Requirement → Requirement Slug
- Categorical → Requirement → Requirement Answers
- Click the "Continue" button.
- In the next step, add the following columns by navigating through the categories and clicking the "+" icon next to each:
- Add Custom Filters:
- Add the following as custom filters:
- Categorical → Requirement → Requirement Slug
- Select the "Contains" filter option.
- Enter the slug name: driver_license_verification.
- Categorical → Requirement → Requirement Slug
- (Optional) Categorical → Requirement → Requirement Answers
- If you need to filter by specific verification outcomes, select the "Contains" filter option.
- Enter one of the following statuses to filter by:
- AUTOAPPROVED
- MANUALREJECTED
- NEEDSAPPROVAL
- (Optional) Categorical → Requirement → Requirement Answers
- Click the "Continue" button on the filter screen.
- Add the following as custom filters:
- Preview the Report:
- Finally, click the "Preview Report" button to review the generated report.
This report will provide a detailed breakdown of the driver's license verification results, including the specific checks performed and their outcomes, based on the filters you applied. This information can be valuable for monitoring the effectiveness of the Microblink integration and identifying any potential issues.