What is Cheque OCR?
Cheque OCR reads a cheque image and returns the banking details printed on the leaf as structured data. Nobody has to copy them out by hand. In most business flows the cheque is a cancelled cheque, submitted as proof of a bank account.
That workflow wants the account number, the account holder name and the IFSC from the leaf.
Indian cheques follow a standard layout, which is what makes them readable at scale. The account number and account holder name are printed on the leaf, and the IFSC sits near the branch details. The band along the bottom carries the cheque number and the MICR code that identifies the bank and branch.
Reading a cheque through an API
A cheque OCR API takes the uploaded image and returns the fields it could read. Your application captures bank details inside the onboarding or mandate journey, instead of parking the file in a review queue.
That matters because a wrong digit costs you later, when a partner is already waiting to be paid.
The response describes what the image shows. Checking that the account exists and belongs to the person or business named is a separate account verification step. Most teams run the two together.
What a cheque image can give you
A reading may return the account number, the account holder name as printed, the IFSC and the bank and branch details. It can also pick up the cheque number and the MICR band, plus the date, payee and amount on a filled cheque.
What you get varies with the data source, the bank cheque layout and the condition of the image.
Real submissions are messy. Cheques arrive photographed at an angle, with a cancellation line across the middle, folded, in shadow, or cropped so the MICR band is missing. Designing the capture step around those images is most of the work.
Where Cheque OCR fits across industries
- Lending and NBFCs. You capture the disbursement account from a cancelled cheque at sanction. A wrong account there means the money lands nowhere.
- Insurance. Claim settlement and premium mandate forms arrive with a cancelled cheque, and the payout account has to match the policyholder record.
- Fintech and payment platforms. Merchant onboarding needs a settlement account before you release any collection.
- Marketplaces. Sellers register at scale, send a photograph of a cheque, and expect to list the same day.
- Logistics and fleet. Transporter, driver-partner and vendor payouts run against accounts you capture during partner onboarding.
- Staffing and gig platforms. Worker payout accounts arrive in bulk, often from a phone, and a failed credit hits the worker directly.
How to capture bank details from a cheque online
Most teams still collect a cancelled cheque by email or a shared drive. It lands in an operations inbox, and someone retypes it hours or days later. Capturing it online moves that work into the session the partner is already in, while they can still fix a bad photograph.
Decide early what the captured account gates. Some teams hold go-live until the account has been checked, and others let a seller finish onboarding and hold only the first payout. Both are defensible, and the choice decides where a failed capture hurts.
Building the cheque upload step
Ask for the bottom band in your capture screen. Many failures are simply a cropped frame, and a preview that puts the MICR band inside the guides fixes more cases than any other change to the flow.
Keep the image with the structured reading. Finance and audit teams reconciling a payout months later need the source document as well as the values in the ledger. What the reading covers, and which checks go with it, depends on the selected service contract.
Consent rules for a cheque image
A cheque image carries bank account details, a name and a signature specimen in one frame. That makes it personal and financial data. Collect it only where you have a stated, lawful reason, and tell the person or business what you will use it for before they upload it.
Take consent for the collection and for the account verification that follows, and keep that record with the file. Restrict access to staff whose work needs it, log who viewed the image, and mask what does not need to appear on screen. Retain the image and the extracted fields only as long as your policy and applicable law require.
Use the details only for the purpose they were given for: paying the account holder, or setting up a mandate they agreed to. Using a captured account for anything else is a purpose change and needs its own basis.