Where MobiCheque sits, and what it never touches
Written for the technical reviewers. This page covers the boundary, the deployment options, the integration paths and how a pilot actually runs.
- Fastest start
- Console only
- Typical pilot
- 8–10 weeks
- Core banking change
- Not required to pilot
The boundary, drawn explicitly
The most common question from an integration team is where responsibility transfers. This is the answer.
Capture
Mobile app or branch device
Extract
OCR reads the cheque fields
Verify
Duplicate, date and fraud checks
Review
Your reviewer decides in the console
No funds move inside this boundary. MobiCheque produces a verified, documented case — not a payment instruction.
Your existing systems and clearing process
Core banking, your clearing arrangements and settlement continue exactly as they do today. MobiCheque hands off a verified case and stops there.
Clearing
We sit upstream of your clearing process
MobiCheque prepares and verifies the cheque before it enters your existing clearing arrangements. It does not replace, bypass or interact with those arrangements, and it does not submit anything to a clearing house on your behalf.
Three ways to run it
Chosen by your policy on where cheque data may be processed, not by which tier you buy.
Managed cloud
We host and operate the platform. Your institution gets an isolated tenant with its own data, users and configuration.
- No infrastructure work on your side
- Isolated per-institution tenant
- We handle updates and monitoring
Best fit
Pilots and mid-sized institutions
Private cloud
The platform runs in a cloud account you own, in a region you choose. You keep infrastructure-level control and visibility.
- You control the hosting region
- Your own network and key management
- We deploy and support remotely
Best fit
Institutions with residency requirements
On-premise
Deployment within your own data centre for institutions whose policy does not permit cloud processing of cheque data.
- Runs entirely inside your network
- No external data egress
- Scoped per engagement
Best fit
Tier-1 banks with strict policy
Confirm before publishing
Data residency
State your current hosting provider and region explicitly here. Kenyan institutions increasingly require in-country residency, and a vague answer on this point stalls reviews.
How deep you integrate is your call
A pilot needs no integration at all. Deeper connection is available when you are ready for it.
| Path | What it gives you | Effort on your side |
|---|---|---|
| REST API | Submit cheques, poll status and pull decisions programmatically. Suitable when you want MobiCheque behind your own front end. | Days |
| Webhooks | We push status changes to an endpoint you control as a cheque moves through capture, verification and decision. | Days |
| Batch file exchange | Scheduled structured exports and imports for institutions whose core systems prefer file drops over live calls. | Days to weeks |
| Console only | No integration at all to start. Your reviewers work in the hosted console and export records. The usual pilot starting point. | None |
What a pilot actually looks like
Structured as a parallel run so nothing in your live process depends on us while we are being evaluated.
Scoping
We map your current cheque flow, agree the pilot scope, volumes and success measures, and complete your security review.
Environment setup
Tenant provisioned, deployment model configured, reviewer roles created and your team invited to the console.
Parallel run
Cheques are processed through MobiCheque alongside your existing process so results can be compared without operational risk.
Review and decision
We report on measured results against the agreed success measures, and you decide whether to expand, integrate deeper, or stop.
Want the technical detail?
We will walk your integration and security teams through the architecture, answer questions live, and scope a pilot against your actual volumes.