QRScan + A8PRO CR · Integrator resources
Add document reading to your software
QRScan and A8PRO CR extract document data. Your software uses it for customer records, agreements or other operations. Integration follows your workflow, regardless of industry.
ZIP · RU/KZ/EN guides, QRScan v2 OpenAPI, Postman collection and integration brief. No keys or installers.
Add the capability to your existing workflow
Operators stay in your system
Use data where you already register customers. Link document reading to a customer record or an operation in your application.
Structured fields instead of retyping
Receive available names, IIN and document details, map them to your fields and show the result to the operator.
One or both methods
QRScan captures original documents and digital documents displayed on a customer's phone. A8PRO CR works with compatible card readers and passport scanners.
Choose an integration interface
QRScan · service API
A smartphone captures the document in a browser. Your integration backend creates a session and receives JSON over HTTPS.
- Create a session and display mobile_url as a QR code.
- Wait for capture; receive the result when the operator is ready.
- Review the fields and durably save the result in your system.
- Send ACK with receipt_token to complete the exchange.
An access key is issued separately and kept server-side. The public demo illustrates the workflow but does not provide API access.
A8PRO CR · local interface
The Windows application connects a compatible reader to your system. Document reading and local result transfer do not require internet access.
- Record the A8PRO CR version, Windows, device and driver.
- Obtain the local interface contract for the selected release.
- Implement requests, field mapping and operator review.
- Test reading, device errors and repeated operations at the workstation.
Endpoints, authentication, response format and acknowledgement depend on the selected release. We do not claim a universal contract across versions; agree on it before development.
Connect reading to your system
1C or desktop software
The developer adds a reading command and fills the target fields. For A8PRO CR, identify whether the client runs on the workstation or a server.
CRM or web application
Connect QRScan through the backend. Design the workstation connection separately for A8PRO CR: the server's localhost is not the customer's computer.
Terminal server or remote workstation
Agree where the device, drivers and integration component run. Device forwarding must be checked on your infrastructure.
Responsibilities of A8PRO and your software
A8PRO
Provides the reading solution, agreed interface, exchange documentation and access terms. The selected hardware configuration is checked.
Integrator
Implements starting and receiving, field mapping, waiting and error handling, operator review and storage in the receiving system.
Fields and processing rules
Available results depend on the document and reading method. Not all fields are available together: chip and MRZ data differ. Validate dates and formats, allow corrections and never replace existing information with empty values.
Example QRScan field mapping
| API field | Your system field |
|---|---|
last_name / first_name / middle_name | Surname / given name / middle name |
iin | IIN — a string, not a number |
document_number | Document number — a string |
issuing_authority | Issuing authority |
issue_date / expiry_date | Issue / expiry dates after validation |
This is a mapping example, not a full API response or a shared format for both products. Agree on the A8PRO CR contract separately.
Checks before going live
- Normal reading, review and storage in the correct record.
- Empty fields, incomplete documents and valid dates.
- Cancellation, expiry, connection loss or disconnected device.
- Retry after a lost response without duplicate customer processing.
- Isolation of concurrent operations across workstations.
- For QRScan: storage before ACK, repeated ACK and no fallback to API v1.
Integration questions
Can any program be connected?
This depends on available interfaces and whether the program can be extended. 1C, CRM and other systems are potential integration types, not a promise of a ready-made module for every version.
Are different versions needed for different industries?
The reading mechanism is the same. Target fields and the receiving application's workflow differ.
Is buying a card reader enough?
You need compatible documents, equipment, drivers, A8PRO CR and a connection to the receiving application. The package is agreed before setup.
Where is the result stored?
Your system defines storage and access after delivery. QRScan exchanges must be completed with ACK; A8PRO CR follows the selected release's contract.
Information needed to assess integration
- Software name and version; who can extend it.
- Where it runs: workstation, browser, server or terminal session.
- Required documents and fields, and where they will be used.
- QRScan, A8PRO CR or both; for CR, device, driver and Windows.
- Number of workstations and desired reading workflow.
We use this information to agree on the exchange method, test scenario, package and implementation cost. Schedule and test access terms are defined for your project.