One-Scan National ID Verification
Extract data from ID cards with advanced barcode decoding, hologram text recognition, and optional liveness checks for secure, instant verification across global formats.
IDENTITY CITY, ID 12345
Field Reference
Comprehensive data extraction from all types of national identity documents
| Field Name | Description |
|---|---|
| document_number | Unique identifier of the ID card |
| full_name | Complete name as printed on the ID |
| dob | Date of birth in ISO format (YYYY-MM-DD) |
| expiry_date | Expiration date in ISO format (YYYY-MM-DD) |
| issuing_authority | Government body that issued the ID |
| barcode_payload_json | Complete decoded data from barcode/QR code |
| face_crop_base64 | Base64 encoded image of the face from ID |
How Accurate Is It?
We have not published a benchmark for national ID cards yet, so we will not put a made-up number here. This is what we have measured, and how errors get caught.
97-99%
Clean Typed Text
Character accuracy on clean typed text in our 2026 OCR benchmark. Printed ID fields are typed text, but glare, wear and angled photos pull it down.
MRZ + barcode
A Second Reading
Where a card carries an MRZ, its check digits are validated, so a misread usually fails the checksum and gets flagged. Barcodes on the card are decoded alongside the printed text.
Fields the engine is unsure about are flagged for a reviewer instead of guessed. The best test is your own sample, so bring a few real national ID cards captures to the demo.
Verification Workflow
Three-step process for secure, accurate ID verification
Time and Checks
What changes when national ID cards are read by DocsAPI instead of typed in by hand
Time
Speed from our 2026 OCR benchmark, including the network round-trip. Capture quality matters more than processing time: a blurry photo costs the user a retake, so guide them to a clean, flat, well-lit shot.
Checks Before the Data Moves On
- MRZ check digits validated where the card has an MRZ
- Field formats checked before the data moves on
- Low-confidence fields flagged for a reviewer instead of guessed
Fraud catch rates depend on your applicant mix and capture flow, so we would rather test on your samples than quote a number.
Developer Output
Structured data ready for your application
{
"request_id": "req_01HGXYZ123456789",
"document_type": "national_id",
"confidence_score": 0.98,
"extracted_fields": {
"document_number": "AB123456789",
"full_name": "JANE MARIE SMITH",
"dob": "1985-06-15",
"expiry_date": "2028-06-14",
"issuing_authority": "DEPARTMENT OF HOME AFFAIRS"
},
"barcode_payload": {
"encoded_data": "SMITH<<JANE<MARIE<<<<<<<<<<<<<<<<<",
"id_number": "AB123456789",
"nationality": "USA",
"gender": "F",
"additional_data": {
"address": "123 MAIN ST, ANYTOWN, CA 90210",
"issue_date": "2018-06-15"
}
},
"face_crop_base64": "data:image/jpeg;base64,/9j/4AAQSkZJRgABA...",
"verification_results": {
"tamper_check": "PASSED",
"expiry_check": "VALID",
"duplicate_check": "NO_DUPLICATES_FOUND"
}
}Regional Compliance
Privacy-first approach for sensitive identity documents
Our platform is designed to meet the strictest global privacy standards, including GDPR, CCPA, and regional regulations for handling sensitive identity documents. We provide flexible deployment options to meet your specific compliance requirements.
Frequently Asked Questions
Common questions about our National ID verification
Add ID verification to your flow.
Integrate our National ID verification API in minutes and start verifying identities securely.
