Identity & KYC
Government-issued IDs hold critical identity data for KYC, onboarding, and compliance. Formats vary by country and state. Sensible turns license, passport, and national ID data into structured JSON for identity verification, fraud detection, and regulatory workflows.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data






Layouts shift by state and country, capture quality varies, and security features and MRZ data have to be read precisely. Hybrid extraction handles the variation and validates the MRZ against the printed fields.
01
Every US state has its own driver's license design, and each revises it periodically. Passports follow ICAO standards but vary by country. Sensible adapts to each jurisdiction's layout while extracting the same core identity fields.
02
IDs are typically photographed by users, not flatbed scanned. Glare from holograms, perspective distortion, finger occlusion, and shadows produce images that need correction before extraction begins. Sensible's LLM parsing handles degraded mobile captures that rigid OCR pipelines reject.
03
Holograms, watermarks, microprint, and ghost images create visual noise that overlays the text fields. The machine-readable zone (MRZ) on passports encodes identity data with check digits that validate extraction accuracy. Sensible isolates text regions and validates MRZ check digits for a built-in accuracy cross-check.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
We configure every government ID extraction to your exact schema, not a fixed field list. The fields below are the ones verification teams pull most often — tell us what your KYC or onboarding workflow needs and we map the rest.
01
Identity data
Full name, date of birth, gender, address, document number, issuing authority, issue date, expiration date, nationality
02
Document-specific
License class/type, restrictions, endorsements, organ donor status (driver's license), MRZ data (passport), visa type
03
Verification signals
Document expiration status, MRZ check digit validation, photo region coordinates, barcode data (PDF417 for US licenses)
config.json
SenseML
{ /* SenseML: government ID extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "full_name", "description": "full name, name, first name last name" },
{ "id": "date_of_birth", "description": "date of birth, DOB, birth date" },
{ "id": "document_number", "description": "document number, license number, DLN, passport number" },
{ "id": "expiration_date", "description": "expiration date, expires, EXP" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes driver's licenses, passports, national ID cards, and state IDs from US and international jurisdictions. Hybrid extraction handles the range of document designs and security features.
Driver's licenses (all 50 states + DC), state ID cards, US passport, US passport card, military ID
National passports (ICAO-compliant), national ID cards, residence permits, work permits, refugee travel documents
Answers about ID types, MRZ validation, and jurisdiction support.
Yes. Sensible extracts the expiration date and validation rules can flag expired documents automatically. Issue dates and date of birth are also extracted for age verification.
Sensible detects photo presence on the ID and extracts all text fields. Photo region coordinates are available for identity verification workflows.
Driver's licenses, passports, national ID cards, and state ID cards from the US and many international jurisdictions are supported today. That set isn't a hard boundary. When you bring an ID type or jurisdiction Sensible hasn't seen, a configuration is built so the right fields come back.
Yes. Sensible extracts Machine Readable Zone (MRZ) data including document number, nationality, date of birth, expiration date, and check digits for validation.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.