Deploy Panini check scanners — or any brand — into a single remote deposit workflow. Hardware-agnostic, open source, and purpose-built for reading both printed MICR and handwriting. Mix scanners across branches, build custom workflows, and never get locked into a single vendor ecosystem.
Works with Panini, Canon, Digital Check, Epson, RDM Open source — custom workflows Handwriting OCR + printed MICR
Most remote deposit platforms lock you into a single scanner brand, a fixed processing pipeline, or generic OCR that cannot read handwriting. Chequedb is different on all three fronts.
Use Panini scanners in one branch, Canon in another, Epson at a kiosk, and Digital Check at a teller station — all connected to the same RDC workflow. Chequedb normalises capture metadata and applies uniform validation regardless of which scanner produced the image. No vendor lock-in, no forklift upgrade when you want to evaluate a new scanner family.
The platform is open source, not a black box. Fork it, add custom validation rules, build bespoke approval flows, wire in proprietary fraud signals, or extend the OCR pipeline with your own models. You own the workflow code and the deployment — no vendor gatekeeping, no feature roadmap dependency.
Generic OCR reads printed text. Chequedb reads both — printed MICR control lines AND handwritten cursive fields: legal amounts, payee names, dates, endorsement text. Handles colloquial written amounts like "rupees one lac only" that most OCR engines cannot parse. Combined with per-field confidence scores, you auto-accept clear items and route low-confidence fields to human review.
Because Chequedb is open source, you are not limited to a fixed pipeline of "scan → OCR → deposit." Teams build custom workflows that match their operational reality:
Define rules for amount thresholds, payee blacklists, routing patterns, or date ranges — and route matched items to specific reviewer groups.
Build maker-checker, four-eyes, or multi-level approval flows that reflect your internal control policies, not a vendor template.
Add proprietary fraud detection models, integrate third-party risk APIs, or build rule-based heuristics into the same pipeline.
Generate audit logs, regulatory reports, and reconciliation exports in the format your examiners and internal audit team require.
Build a single scanner integration adapter that serves Panini, Canon, Epson, and Digital Check scanners through one code path.
Chequedb isolates scanner hardware at the capture edge and standardises the downstream control layer. Deploy one scanner family or mix several — validation, exception routing, and audit logic stay the same.
| Scanner family | Typical fit | Integration notes |
|---|---|---|
| Panini Vision Series and I-series | Branch teller, platform, and low-to-medium volume RDC | Panini scanners are widely deployed in North American banks. Evaluate MICR output quality, duplex image settings, SDK capabilities, and endorsement behavior through the Chequedb integration layer. |
| Canon imageFORMULA CR series | Branch, teller, and compact desktop capture | Evaluate MICR output, duplex image settings, feeder events, and workstation driver support across CR-55, CR-190, and CR-270 models. |
| Digital Check TellerScan and CheXpress | Teller, branch, and remote deposit capture workstations | Evaluate SDK access, batch recovery, scanner state events, and locked-down endpoint support for TS240, TS215, and CheXpress models. |
| Epson CaptureOne and TM-S families | Branch environments that combine check capture with other teller peripherals | Evaluate MICR/image support, peripheral management, endorsement needs, and OS support for TM-S100 and TM-S900 models. |
| RDM EC series and networked RDC devices | Distributed RDC, compact scanner deployments, and managed capture endpoints | Evaluate network or service-layer integration, device identity, firmware management, and duplex capture for EC8000 and EC7000 series. |
| MagTek Excella and other MICR-capable scanners | Specialized desktop, teller, and controlled capture flows | Evaluate native SDK coverage, MICR character support, image formats, and exception recovery behavior. |
Scanner names are listed as common evaluation targets, not as partnership or certification claims. Final support depends on model, SDK access, drivers, operating system, and deployment constraints. Because the platform is open source, adding or adapting support for an unlisted scanner family is always an option.
Scanner SDK projects usually succeed when hardware capture is isolated from the workflow controls that decide whether an item can move forward. The open-source architecture means every integration path is customisable.
A scanner SDK integration should deliver workflow-ready evidence, not just an image file. Chequedb attaches capture metadata, OCR, MICR, and handwriting recognition results so operations can review exceptions and audit the decision trail — regardless of which scanner brand produced the capture.
Standardise validation, handwriting OCR, fraud checks, approvals, reconciliation, and audit trails for every check item — with the freedom to mix scanner brands and build custom workflows on an open source platform.
Discuss Scanner Support