Scanner capture
The manufacturer’s driver or SDK controls device access, feeding, image capture and the magnetic read where the hardware supports it.
SCANNER SDK INTEGRATION · REMOTE DEPOSIT CAPTURE
Turn scanner output into useful cheque data. Send front and back images and the MICR read from your Panini or Digital Check scanner to one API, and get handwritten amounts, payee, date and MICR fields back as JSON for validation and operator review.
Compare the extracted values and apply your workflow rules.
Illustrative scenarios with fictional data. These controls do not call the OCR API or approve a deposit.
SCANNER TO WORKFLOW
The manufacturer’s driver or SDK controls device access, feeding, image capture and the magnetic read where the hardware supports it.
Your adapter associates the front and back images, device read and job identifier, then submits the agreed inputs to processing.
Your application handles capture failures, missing fields and OCR disagreements before a deposit item proceeds.
MODEL + DRIVER + OPERATING SYSTEM
| Pilot detail | What to confirm |
|---|---|
| Exact model and firmware | Image sides, feeder behaviour, magnetic read capability and vendor support. |
| Operating system and driver / SDK | Supported versions, licensing, installation and any local service needed for browser access. |
| Capture output | Image format, resolution, orientation, front/back association and raw MICR format. |
| Processing contract | Enabled fields, upload limits, normalisation rules and handling of device/image disagreements. |
| Operational behaviour | Jams, double feeds, reconnects, rescans, duplicate jobs and reviewer access to the source images. |
Validate the exact scanner, driver and operating system combination in your hardware pilot.
RDC REQUEST WALKTHROUGH
After the scanner finishes a feed, your adapter has a front image, a back image, a raw MICR string and a job identifier. Submit the front image for extraction from your server, keep the MICR string and job identifier in your own record, and join the two when the response arrives.
| Adapter step | What your integration does |
|---|---|
| 1. Capture | The scanner SDK feeds the cheque and returns front and back images plus the magnetic MICR read, where the device has a read head. |
| 2. Record the job | Store the job identifier, raw MICR characters (with leading zeros), image paths and operator or branch context. |
| 3. Submit for extraction | Upload the front image from your backend. The response returns date, payee, both amounts, bank, branch, cheque number and drawer. |
| 4. Reconcile | Compare the OCR cheque number with the MICR cheque number, and the written amount with the numeric amount. Flag any disagreement. |
| 5. Route the item | Clean items continue to your deposit workflow. Disagreements and unreadable fields go to an operator with the source images. |
curl --fail-with-body --request POST \
"${CHEQUEDB_BASE_URL}/api/v1/ocr/cheque/upload" \
--header "Authorization: Bearer ${CHEQUEDB_TOKEN}" \
--form "file=@./scans/job-1042-front.jpg"The service URL, authentication scheme and enabled fields are provisioned for your deployment. See the cheque API integration guide for the full response example.
WHERE SCANNER RDC FITS
| Deployment | Typical capture | MICR source | Main integration concern |
|---|---|---|---|
| Branch / teller capture | Desktop or teller scanner, often batch feeds | Magnetic read head plus image | Throughput, jams and operator review at the counter |
| Merchant / commercial RDC | Compact single-feed scanner at the business | Magnetic read head plus image | Installing drivers on customer machines and supporting remote users |
| Back-office processing | High-volume scanner in an operations centre | Magnetic read head plus image | Batch reconciliation, exceptions queues and audit trail |
| Mobile deposit | Phone camera in a banking app | Image only (optical MICR) | Glare, blur and recapture guidance |
NATIVE SCANNER SUPPORT
These models have a configured capture handoff: duplex images and the raw MICR line flow straight into OCR, validation and review. Other models can connect through the manufacturer SDK and a processing adapter.
Single-feed desktop scanner for branch and back-office remote deposit capture.
View CX30 supportTeller and batch capture with duplex images and MICR read.
View TS250 supportCompact scanner for merchant and commercial remote deposit capture.
View Micro Elite supportDesktop cheque scanner for teller and commercial deposit workflows.
View Vision X supportMICR & OCR
Scanners with a magnetic read head can capture MICR data. OCR reads the cheque image. Keep both sources available to resolve disagreements in your workflow.
Retain raw characters, delimiters and device error information where available. Do not strip leading zeros from account identifiers.
Routing, account and cheque number conventions vary. Some MICR schemes also encode amounts or other processing information.
A readable control line does not prove a cheque is authentic or eligible. Use the source image and your bank’s validation rules.
BEFORE ROLLOUT
Include the bank layouts, languages and handwriting your team sees every day, captured on the devices you intend to use. Share only images you are authorised to use.
Measure correct reads for each field, amount disagreements and the items that need review. Check response times at your expected volume.
Agree the supported formats, API contract, review rules and data handling before connecting the service to your live workflow.
QUESTIONS & ANSWERS
Yes. Scanner or mobile captures are submitted to the cheque OCR API, which returns the handwritten amount, payee, date and MICR fields as JSON for your validation and review steps. Deposit submission and clearing stay with your banking integration. See the cheque API integration guide for the upload example and response fields.
Yes. The Panini Vision X has native support, so duplex images and the raw MICR line flow into OCR, validation and review. Other Panini models can connect through the Panini SDK and a processing adapter after a pilot confirms the model, driver and operating system.
Yes. The API receives images and your adapter keeps the device MICR read, so branches can run Digital Check and Panini scanners side by side. Each model still needs its own driver or SDK and a check in your pilot.
Both. The scanner reads the magnetic MICR line, and the OCR response adds the handwritten amount in words, the numeric amount, payee and date. Comparing the two amounts helps catch misreads before a deposit item proceeds.
Send the front image to the API from your backend, and keep the back image, raw MICR string, job identifier and operator context in your own record. Join them with the OCR response so reviewers see every source in one place.
Plan device control through the supported manufacturer driver or SDK, with a processing adapter for the captured output. Confirm the integration components and responsibilities for the exact device and operating system.
Compatibility depends on the exact model, firmware, driver or SDK, operating system and output format. Use the scanner catalogue to shortlist devices, then validate the intended combination in a pilot.
Browser-to-device access depends on the hardware and vendor integration. A local service or adapter may be required. Confirm the installation, permissions and support model before choosing the capture architecture.
Agree licensing for the vendor SDK and any integration components with the relevant providers. Confirm the terms for your scanner, operating system and deployment.
BUILD WITH CHEQUEDB
Tell us about your app, cheque layouts and required fields. Let’s plan an evaluation with your documents.