AI document verification via mobile camera is not just OCR—it's a full pipeline: document detection in the frame, quality assessment, field extraction, validation, and authenticity check. Each step can become a bottleneck, so we use a combination of methods proven on dozens of projects. A typical scenario: the user photographs a passport in poor lighting, the document is partially shadowed, edges cropped. Even if OCR reads the text, the MRZ may be damaged and data fails validation. Without guidance, the user makes 3–5 attempts, worsening UX, increasing drop-off by up to 30%, and raising support costs. We solve this comprehensively, reducing failed attempts to single digits and saving the budget on fraud control. In our practice of implementing verification systems for banks and fintech services, recognition accuracy reaches 99% with proper pipeline configuration. Our team has over 8 years of experience in mobile document verification solutions and has successfully launched more than 50 projects in this area. We guarantee >99% accuracy with proper setup—each project is accompanied by a detailed quality audit.
Why Raw OCR Doesn't Work
Attempting to read a passport via Vision framework (iOS) or ML Kit (Android) and parse the result with regex is the most common first approach. It yields 70–80% accuracy in the lab and 40–60% on real users: glare, shooting angle, crumpled pages, document wear—all of this breaks simple OCR.
The correct pipeline adds three layers:
- Image preprocessing. Perspective correction (document shot at an angle), contrast enhancement, glare removal. On iOS—CIFilter + CIPerspectiveCorrection. On Android—OpenCV via JNI or CameraX with custom ImageAnalysis.
- Specialized document OCR. Not general OCR, but models trained on documents: Microsoft Azure Document Intelligence, Google Document AI, Amazon Textract. They return structured fields—surname, given_names, date_of_birth, document_number.
- Machine Readable Zone (MRZ) parsing. Passports contain MRZ per ICAO 9303 standard. This is the most reliable source: standardized font, clear structure, checksum. Libraries: mrz-java, passport-reader for iOS, or custom implementation.
Why We Choose Azure Document Intelligence?
Azure Document Intelligence delivers >99% accuracy on standardized documents, supports MRZ out of the box, and provides confidence scores for each field. Compared to Google Document AI (~98% accuracy) and Amazon Textract (95%, no built-in MRZ), Azure offers the best price/quality ratio for mobile scenarios. For budget projects, Google Document AI works; for AWS integration, Amazon Textract; but for mobile high-load scenarios, Azure is more stable.
| Provider | Accuracy on ID documents | Speed | MRZ support |
|---|---|---|---|
| Azure Document Intelligence | >99% | 2–5 sec | Yes |
| Google Document AI | >98% | 3–7 sec | Yes |
| Amazon Textract | >95% | 5–10 sec | No |
How We Integrate Azure Document Intelligence
// iOS — Swift import AzureAIDocumentIntelligence class DocumentVerificationService { private let client: DocumentIntelligenceClient func analyzePassport(imageData: Data) async throws -> PassportData { let request = AnalyzeDocumentRequest( urlSource: nil, base64Source: imageData.base64EncodedString() ) let operation = try await client.beginAnalyzeDocument( "prebuilt-idDocument", analyzeRequest: request ) let result = try await operation.waitForResult() guard let document = result.documents?.first else { throw DocumentError.noDocumentDetected } return PassportData( firstName: document.fields?["FirstName"]?.valueString, lastName: document.fields?["LastName"]?.valueString, documentNumber: document.fields?["DocumentNumber"]?.valueString, dateOfBirth: document.fields?["DateOfBirth"]?.valueDate, expiryDate: document.fields?["ExpirationDate"]?.valueDate, nationality: document.fields?["CountryRegion"]?.valueCountryRegion, mrz: document.fields?["MachineReadableZone"]?.valueString, confidence: document.confidence ?? 0 ) } } Confidence score is a critical parameter. If confidence < 0.8, we request a retake with user guidance (better lighting, hold flatter, don't cover edges).
Realtime Camera Guidance
The user should not make multiple attempts blindly. Real-time feedback during capture via Vision framework on iOS:
// Detects document bounds in realtime while camera is active func detectDocumentInFrame(_ pixelBuffer: CVPixelBuffer) { let request = VNDetectRectanglesRequest { [weak self] request, error in guard let observation = request.results?.first as? VNRectangleObservation else { self?.cameraGuidance = .noDocumentFound // "Point camera at document" return } let area = observation.boundingBox.width * observation.boundingBox.height if area < 0.4 { self?.cameraGuidance = .tooFar // "Move closer" } else if area > 0.9 { self?.cameraGuidance = .tooClose // "Move further away" } else { self?.cameraGuidance = .ready // Automatic capture } } request.minimumAspectRatio = 0.5 request.maximumAspectRatio = 1.0 request.minimumConfidence = 0.7 try? VNImageRequestHandler(cvPixelBuffer: pixelBuffer).perform([request]) } Automatic capture when positioning is ideal removes the need to press a button—reducing the number of poor shots.
Forgery Detection: What We Check?
Basic anti-spoofing for mobile verification includes:
| Check | Method |
|---|---|
| Physical document vs photo/screen | Detection of moire effect and paper texture (Azure, Onfido) |
| Liveness check | Random head movements, blinking (AWS Rekognition, FaceTec) |
| Cross-check MRZ with visual fields | Date of birth must match |
These methods ensure the document is real and belongs to the presenter.
How Is Personal Data Protection Ensured?
All data is processed in accordance with GDPR and local regulations. Document images are not stored after verification—only extracted fields. We use encryption at rest and in transit, and an isolated environment for model execution. For sensitive data, the solution can be deployed in the client's cloud (Azure / AWS).
Process of Work
- Analyze which documents need to be supported
- Choose OCR provider (Azure / Google / custom)
- Implement realtime camera guidance
- Integrate document analysis API
- MRZ parsing and cross-validation of fields
- Anti-spoofing and liveness check
- Compliance check (GDPR for passport data storage)
What's Included in the Result
- Camera module with realtime guidance and automatic capture
- Integration with chosen OCR service (Azure, Google, or custom model)
- MRZ parsing and cross-validation of fields
- Anti-spoofing and liveness check (optional)
- API documentation and integration guide
- Access to source code and test examples
- Support during release on App Store / Google Play
Time Estimates
MVP with Azure Document Intelligence and basic guidance—2–3 weeks. Full system with liveness check, anti-spoofing, and support for multiple document types—4–6 weeks.
To find out how to implement AI verification in your app, contact us. Order a consultation to assess your project—we'll choose the optimal solution and timeline. Get a free assessment of your case and recommendations for choosing a provider. AI verification integration pays off by reducing manual document checking.