Hardware compatibility and evidence
Use this qualification matrix with the hardware catalogue. A listed device is a starting point for evaluation. Source inspection establishes the shape of an integration, while a hardware test establishes behaviour for the recorded configuration. Neither a manufacturer specification nor a related model’s test substitutes for that evidence.
Reviewed 26 October 2026. The matrix identifies the available evidence and the configuration details to confirm with the integration team. Hardware test configuration and dates remain to be confirmed for these rows.
| Integration | Operation | Evidence status | Configuration | Limit and test date |
|---|---|---|---|---|
| Configured document-reader module | Read reported status without starting capture | Source-inspected contract, 26 October 2026 | Reviewed Java 21 source line; reader model, OS, connection, firmware and driver release to confirm | Enabled module required. Hardware test configuration and date: to confirm with the integration team. |
| Cheque scanner integration | Captured cheque fields and optional OCR content/validation result | Source-inspected response model, 26 October 2026 | Exact scanner, connection, runtime, driver and firmware to confirm | Hardware test configuration and date: to confirm. Measure capture quality and OCR results on a labelled corpus. |
| Fujitsu F53, F56 and F510 listings | Advertised cash-dispenser integration | Advertised compatibility; hardware test evidence pending configuration review | Confirm each model/variant, cassette setup, connection, OS, driver and firmware separately | Request the capacity, operations and dated test record for the exact installed configuration. |
| REINER RS 891 and RS 893 listings | Advertised cheque/document capture integration | Advertised compatibility; hardware test evidence pending configuration review | Confirm model, optional sensors, image channels, OS, connection, driver and firmware | Optical MICR-line recognition is different from magnetic sensing. Magnetic MICR requires suitable hardware and a validated integration. |
| Payment terminal listings | Advertised payment-device integration | Advertised compatibility; configuration and certification scope to confirm | Exact terminal variant, payment application, processor, region and firmware required | Confirm certification scope for the terminal, payment application and complete deployment separately. |
| Cash-to-card devices | Supported cash handling, card issuance and receipt devices scoped together | Product-family scope; hardware test evidence pending configuration review | Confirm cash device, card format/issuance module, printer, OS and issuer/processor | Card activation and balances belong to the issuer/processor. Require joint failure and reconciliation tests. |
What a supported configuration record should contain
Ask the SDK integration team and hardware QA owner to identify the model and variant, interface, operating system and architecture, runtime build, driver and firmware versions, enabled options and operations tested. Record the test date, responsible team, evidence location, known limitations and recovery cases. Agree which party owns updates and regression checks.
A mobile cheque image can provide optical content without a scanner’s magnetic channel or ultraviolet image. A scanner may expose optional channels that are absent on another configuration. Confirm both the sensor and the returned data before including either in a fraud or validation requirement.
SDK and Satellite support are separate
The SDK connects applications to supported peripherals. Satellite manages device fleets and application operations across Windows, Linux and Android, with controls that depend on the platform and permissions. Confirm SDK driver and peripheral compatibility for your chosen operating system separately.