DOCUMENT OCR FOR YOUR WORKFLOW
ID document OCR for access-control workflows
Prepare visitor records from supported identity documents while keeping admission rules in your access system. IdScanly helps staff review the person’s details before issuing a pass.
Access control
Where manual entry slows you down
Reception teams may retype visitor details from a document into a registration system and then again into a badge tool. OCR can support a draft visitor record without automating the decision to admit someone.
A practical workflow
Capture with permission
Explain the visitor-registration purpose and capture only the permitted document data.
Extract and map fields
Send the extracted fields to a draft visitor entry linked to the host or appointment.
Review before committing
Confirm the visitor, appointment and required checks before issuing a badge or opening access.
Integrate with your existing system
Send an authorised document image from your own backend to the IdScanly REST API. Create a scan session, upload the image and retrieve structured JSON when processing finishes. Map only the fields your application needs; keep API keys on your server and handle timeouts, incomplete fields and retries explicitly.
Read the API documentationBuild a review step into the process
Document type, country, image quality and layout affect the fields returned. Use confidence information and capture feedback to request a clearer image or send uncertain records to a person. Extracting a field is different from proving it is genuine. Keep the original value separate from any correction made by an operator.
OCR supports data entry. It does not independently provide document authentication, face matching, liveness detection or a complete AML/KYC service.
Keep the data flow proportionate
Collect only what the workflow requires and explain the purpose before upload. IdScanly processes documents without building an archive; temporary processing and result retrieval can involve files and records. The marketing/admin CRM receives identity and activity metadata, never document images or OCR fields. Your own application remains responsible for its storage, retention and user permissions.
Evaluate with your own document mix
Test representative countries, document versions, front/back views and realistic capture conditions. Measure field-level accuracy and review rates against checked references before connecting the output to a live business decision. Share your expected monthly image volume and planned launch date so integration requirements can be discussed.
Questions before integration
Does OCR recognise a face or unlock a gate?
No. OCR returns document fields. Face comparison, biometrics, watch-list checks, badge issuance and door-control actions belong to separate systems.
Build a review step into the process
Document type, country, image quality and layout affect the fields returned. Use confidence information and capture feedback to request a clearer image or send uncertain records to a person. Extracting a field is different from proving it is genuine. Keep the original value separate from any correction made by an operator.
Access control
Discuss this integration
Test representative countries, document versions, front/back views and realistic capture conditions. Measure field-level accuracy and review rates against checked references before connecting the output to a live business decision. Share your expected monthly image volume and planned launch date so integration requirements can be discussed.