Computer Vision & OCR Auto Document Scanning
Automated extraction and authenticity verification for Indonesian merchant legal documents during onboarding.
Computer Vision & OCR Auto Document Scanning
Prototype page exposes input contracts, processing stages, structured outputs, quality controls, privacy controls, integration points, PoC questions and evidence needed before production acceptance.
Inputs
Processing Pipeline
Malware scan, MIME validation, image quality check and secure temporary object creation.
Document-type classifier identifies NIB / NPWP / Akta / permit format and version.
Extract text, key-value relationships, tables and signature/stamp zones.
Analyze recapture artifacts, editing inconsistencies and visual manipulation signals.
Normalize names/addresses/IDs and compare consistency across documents.
Low-confidence fields and authenticity alerts create review tasks.
Structured Outputs
| # | Question to provider | Prototype status | Evidence / response expected |
|---|---|---|---|
| 1 | Which Indonesian official documents are natively supported and what OCR accuracy is measured for each? | PoC response | Provide per-document precision/recall or field accuracy on labeled Indonesian samples. |
| 2 | Which methods detect document authenticity/manipulation and what accuracy / FAR-FRR is observed? | PoC response | Provide test methodology, attack classes and error rates. |
| 3 | Is the model specifically trained for Indonesian documents and how are format changes handled? | PoC response | Provide training/validation approach and update governance. |
| 4 | What is the output format, per-field confidence and human-review workflow? | PoC response | Provide JSON schema, confidence semantics and review thresholds. |
| 5 | What is latency per document and maximum throughput? | PoC response | Provide p50/p95/p99 latency and sustained/concurrent throughput. |
| 6 | Which deployment options are supported and where are documents processed/stored? | PoC response | Provide SaaS/private/on-prem architecture and data residency map. |
Data minimization
Extract and retain only fields required for KYB decisioning; suppress unrelated document content.
Sensitive-document isolation
Raw scans are stored separately from analyst-facing structured fields; access is more restrictive.
No secondary training
Vendor/model training on merchant documents is disabled unless separately assessed and contractually approved.
Retention & deletion
Raw document retention is shorter than derived KYB records where legally/operationally feasible; deletion propagates to caches and backups.
Illustrative structured output
Schema is intentionally explicit to support decision-engine integration, explainability and audit. Values are simulated.
Document Investigation Workbench
Interactive upload/preview, structured fields, authenticity indicators and cross-document comparison.
Open Workbench →