NCR SCPM and SCPM2 supported hardware integration
NCR SCPM hardware captures and protects the paper. It is NCR hardware, not ChequeDB hardware. ChequeDB supports the integration and turns its cheque images and MICR data into item-level decisions, then coordinates the bank-host workflow through posting, reconciliation, clearing, and archive.
Capture
Front, rear, and available UV images; MICR signal; escrow and physical custody.
Intelligence
OCR/ICR, image quality, field confidence, validation, duplicates, and risk evidence.
Orchestration
Item decisions, bank-host calls, review, posting, clearing, reconciliation, and archive.
The module does not parse, score, post, or clear the cheque
SCPM is strong media-handling engineering. The complete deposit system still needs software to understand each cheque, apply bank policy, make a reversible decision, and prove what happened after capture.
| Layer | What it owns | What it does not own alone |
|---|---|---|
| NCR SCPM / SCPM2 hardware | Paper transport, bunch separation, double-feed checks, images, MICR signal, escrow, return, endorsement, and storage. | OCR/ICR, amount recognition, fraud decisions, customer-account rules, core posting, clearing, or archive policy. |
| NCR-supported device stack | XFS device access, Bunch Cheque Acceptance states, APTRA or Advance NDC transaction control, and supported physical commands. | The bank's full image-intelligence, exception, reconciliation, and deposit-lifecycle policy. |
| ChequeDB | Image intelligence, structured cheque data, validation, duplicates and risk, item decisions, review, host orchestration, and audit evidence. | Unsupported direct hardware control or final bank policy that the institution keeps in its host systems. |
| Bank host and operations | Account authority, limits, posting, customer messaging, clearing, settlement, reconciliation, retention, and operational oversight. | Reliable cheque-image understanding unless an intelligence layer supplies it. |
Keep every paper item tied to its image, decision, and host reference
A bunch is not one decision. It is a group of separately identified cheques moving through one physical transaction. ChequeDB preserves item-level correlation while the supported NCR path keeps the paper reversible in escrow.
Accept
Endorse and secure the approved item, then bind the physical result to the posted deposit reference.
Review
Hold or route the item according to the bank's configured policy, with the image crop, reason, and decision evidence attached.
Return
Re-bunch and present the declined items through the supported device flow without confusing their images or reasons.
More than a parse response or a score
The result is a controlled deposit record, not a loose OCR payload. ChequeDB can carry the transaction from captured evidence to the bank host and through every operational exception that follows.
Cheque image intelligence
Read printed and handwritten fields from front, rear, and available UV images. Return values, image-quality results, and field-level confidence.
Cheque-specific validation
Normalise MICR control data, reconcile written and numeric amounts, apply date rules, and validate required regions and endorsements.
Duplicate and risk controls
Detect repeat presentment, combine bank rules with image evidence, and route uncertain or high-risk items without losing the source record.
Item-level decisions
Treat every cheque in the bunch as a separate item. Accept, review, or return according to the configured policy while keeping item order and evidence correlated.
Bank-host orchestration
Call account and deposit rules, carry idempotency and transaction references, return decisions before physical commit, and coordinate core posting.
Reconciliation and archive
Link device events, images, extracted fields, rules, approvals, physical outcomes, host references, clearing status, and archive evidence.
Explore the underlying cheque data extraction workflow or the developer-facing bank check OCR API used to return structured fields, confidence, and validation evidence.
One durable state machine from insertion to reconciliation
Timeouts, retries, partial bunch outcomes, reversals, and host uncertainty are normal transaction states. Each one needs an idempotent response and a recoverable evidence trail before the paper and account balances diverge.
- 01
Open the deposit
Create one transaction reference and stable item identifiers before paper leaves the customer's control.
- 02
Capture the bunch
The supported NCR stack separates each item, captures its evidence, and holds the paper in escrow.
- 03
Understand every cheque
ChequeDB reads the images, normalises MICR, validates fields, and produces confidence and risk evidence.
- 04
Ask the bank host
Account, limit, product, deposit, and risk rules are evaluated with the extracted cheque record.
- 05
Return an item decision
Each cheque receives an accept, review, or return outcome before the configured physical commit point.
- 06
Commit and reconcile
The NCR stack endorses and stores or re-bunches and returns paper; ChequeDB links the outcome to posting, clearing, and archive records.
Use the complete NCR device stack and confirm its current support status
Possession of an SCPM does not create a supported scanner integration. Drivers, firmware, XFS service providers, Bunch Cheque Acceptance services, APTRA or Advance NDC configuration, licences, and maintenance support determine what can be safely controlled.
ChequeDB does not manufacture, resell, or maintain the SCPM. Hardware supply, compatibility, lifecycle, firmware, device software, maintenance, and current vendor support must be confirmed with NCR or the bank's authorised NCR channel for the exact configuration.
ChequeDB sits above that supported device boundary. It accepts the images and item context, returns business decisions through an approved interface, and keeps the deposit record consistent across device, bank host, review, and clearing systems.
What the integration pilot proves
- Every paper item maps to the correct front, rear, optional UV, and MICR evidence.
- Host timeouts and retries cannot double-post a deposit or lose the physical decision.
- Mixed accept and return outcomes preserve sequence, reasons, and customer messaging.
- Endorsement and storage evidence matches the committed item record.
- Review, reversal, clearing, reconciliation, and archive states remain traceable.
Continue the architecture review
Compare the hardware estate, the cheque intelligence layer, and the operational workflow as separate procurement decisions.
Cheque scanner catalog
Compare capture hardware, throughput, MICR support, and deployment fit.
ExploreCheque scanning software
See how images become validated fields, exceptions, and controlled outputs.
ExploreCheque management workflow
Review approvals, lifecycle control, reconciliation, search, and audit history.
ExploreNCR SCPM and Bunch Cheque Acceptance FAQ
The practical boundary between the physical module, ChequeDB, and the bank host.
Does ChequeDB support NCR SCPM and SCPM2 cheque deposits?
Does ChequeDB support NCR SCPM and SCPM2 cheque deposits?
What does the NCR SCPM hardware do by itself?
What does the NCR SCPM hardware do by itself?
Does the SCPM parse the cheque or return risk scores?
Does the SCPM parse the cheque or return risk scores?
What is Bunch Cheque Acceptance?
What is Bunch Cheque Acceptance?
Can ChequeDB orchestrate the bank host and core-banking workflow?
Can ChequeDB orchestrate the bank host and core-banking workflow?
Does ChequeDB control an NCR module through an unsupported hardware API?
Does ChequeDB control an NCR module through an unsupported hardware API?
Does ChequeDB manufacture or sell the NCR SCPM hardware?
Does ChequeDB manufacture or sell the NCR SCPM hardware?
Design the complete cheque deposit path
Bring the NCR configuration, host contract, transaction states, and sample cheque evidence. The integration review maps the supported device boundary and the ChequeDB workflow around it.
Book an Architecture Review