AU10TIX Identity Verification Suite
Document, biometric and identity-data checks in a configurable verification suite.
Supplier popularity25%By Regula
Regula Document Reader SDK
Document capture, extraction and authenticity checks supplied as an SDK for configured identity workflows.
The offering
What Regula Document Reader SDK does
Document Reader SDK recognises identity-document types, captures document images and extracts visible-zone, MRZ, barcode and supported electronic data. The current product describes cross-checking these sources, document-liveness checks and server-side validation of electronic-document data. Its gambling page applies document evidence to onboarding and age workflows.
Select the exact documents, capture surfaces and verification checks required. Reading a template and authenticating its security features are different capabilities, so test both on the operator’s document mix. Define processing/retention, result interpretation, retries and manual review. Face verification and other AML or location controls require their own selected scope; an SDK document result does not itself authorise an account or withdrawal.
Who should explore it?
Operator engineers and identity reviewers implementing document evidence capture and validation.
- Extract and check a player’s submitted identity document
- Supply date-of-birth/document evidence to an operator’s age review
Documented capabilities
- Document type recognition
- OCR/MRZ/barcode reading
- Data-source cross-checks
- Document-liveness options
- Electronic-data verification
Reported in the linked public sources. We have not independently tested these capabilities.
Product details
- Document verification
- Document capture, extraction and authenticity evidence for configured identity workflows.Source
- Evidence sources
- Visible-zone OCR, MRZ, barcode and supported electronic data with cross-check and liveness/authenticity options.Source
- Document scope
- Supported template and check availability must be verified for the operator’s exact documents; broad database coverage is not jurisdiction permission.Source
- Implementation
- SDK integration across mobile, web or backend scenarios, with evidence handling specified by the buyer.Source
- Adjacent checks
- Biometric verification is separately presented with Face SDK; wider AML, source-of-funds and location controls remain separately scoped.Source
- Commercial model
- Usage- and business-specific pricing rather than a complete public numerical tariff.Source
Delivery & commercial details
- Delivery & integration
- Select the mobile, web or backend implementation and exact checks; test capture quality, evidence processing, result handling and review exceptions with required documents.Source
- Pricing
- The product describes flexible pricing based on usage and business needs. Request runtime/deployment, document/check scope, volume, support and update terms.Source
Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.
Buyer questions, answered
Does the template total establish every authenticity check?
No. Compare recognition/extraction with the security and electronic-data checks supported for each required document. Test the actual document mix and inconclusive cases.
SourceCan we use date-of-birth evidence to make an age decision?
Regula’s gambling page describes extracting date of birth for age review. Configure the operator’s actual age and eligibility policy; the evidence does not grant permission to play.
Source