Integrations

Connect cheque capture to the systems that own the transaction

Chequedb sits between capture and the system of record. This page explains the integration patterns and what is confirmed during scoping. The names below are evaluation targets, not a certified-partner list; do not infer compatibility from a logo.

Request an integration review Read the API contract

Capture

Desktop, production, and high-speed scanners through drivers, OEM SDKs, or capture middleware; mobile camera capture; direct image upload.

Core banking

Evaluation targets include Fiserv, FIS, Jack Henry, Temenos, Finacle, and Oracle FLEXCUBE. Interface and version are confirmed during scoping.

ERP and accounting

Evaluation targets include SAP, Oracle, Microsoft Dynamics, NetSuite, QuickBooks, Xero, and Odoo. Mapping and posting rules are agreed per deployment.

Data exchange

REST API, JSON, CSV, and flat-file batch exchange. SFTP and message-queue patterns are scoped per deployment; webhooks and SDKs are not currently published.

Identity

SSO/SAML/OIDC and role mapping where the deployment supports it. Confirm the identity provider, group model, and maker-checker design.

Clearing path

X9.37, ACH, and settlement remain with the bank or payment operator. Chequedb supplies structured fields and evidence to the agreed boundary.

How an integration is scoped

  1. 1. System of record. Name the target system, version, interface, and owner.
  2. 2. Capture path. Confirm device, driver, image format, MICR output, and throughput.
  3. 3. Field map. Match extracted fields to target fields, including IDs and amounts.
  4. 4. Exception path. Decide what happens on low confidence, CAR/LAR mismatch, duplicate, or timeout.
  5. 5. Reconciliation. Agree the control totals, posting reference, and return path.
  6. 6. Security. Complete the data-flow, retention, and access review before production images.

What we need from you

  • • Target system and interface documentation.
  • • A de-identified sample of images and expected field values.
  • • The posting/reconciliation rule and the exception owner.
  • • Volume, peak load, and latency target.
  • • Security, retention, and data-residency requirements.
  • • A test environment or sandbox contact.

Compatibility is confirmed in writing for the specific version and scope. This page is not a warranty of integration with any third-party product.

Related technical pages

Bank check OCR API docsX9.37 and ACH guideOCR implementation guideSecurity & complianceScanner catalogue

Integration questions

Does Chequedb have certified connectors for our core banking system?

Chequedb integrates through APIs, file exchange, and capture middleware. Core banking compatibility depends on the version, interface, and scope. The names on this page are evaluation targets, not a certified-partner list. Confirm the exact interface in a scoping exercise.

Can we keep our existing cheque scanners?

Yes, where the scanner exposes images and MICR data through a supported driver, OEM SDK, or capture middleware. Confirm the model, operating system, duplex capture, MICR output, and throughput in a pilot. The scanner catalogue is an evaluation list, not a certified-support matrix.

What integration methods are available?

REST API for application integration, JSON/CSV/flat-file exchange for batch, and scanner/mobile capture feeds. SFTP and message-queue patterns are scoped per deployment. Webhooks and SDKs are not currently published; confirm the current interface during access provisioning.

Can Chequedb generate X9.37 or ACH files?

X9.37 generation, ACH origination, transmission, and settlement are separate integrations. Chequedb extracts and validates fields that can feed the bank’s existing clearing pipeline. Confirm the clearing-artifact scope before assuming the OCR response is a cash letter or ACH file.

How long does an integration take?

It depends on the interface, data mapping, security review, and test environment. A narrow pilot can be scoped in weeks; a core banking or clearing integration needs a longer joint plan. The pilot should include the exact capture path, field mapping, exception handling, and reconciliation.

Third-party names are trademarks of their respective owners. Evaluation targets are not a certified-partner list, and compatibility is confirmed for the specific version and scope.