Scan a Receipt, Get Your Chargeback Deadline

The problem a photo solves

Every chargeback deadline is date math, and the math is only as good as the date you feed it. That date sits on a statement or a receipt — often a paper one, often photographed at an angle on a kitchen table — and it is surrounded by other dates that look just as important: the statement date, the posting date, the delivery date. Pick the wrong one and the deadline you calculate is wrong by weeks, in the dangerous direction.

Scanning does not change the rules. What it changes is the typing: point a camera at the charge and the date, amount and merchant are lifted off the page for you. The catch — and it is the whole subject of this guide — is that software reading photos makes mistakes, so a scanning tool is only worth using if it is built to catch its own errors before they reach the calculation. Scan to Dispute is our version of that idea; this guide explains how it works, where it can go wrong, and the two dates you still need to understand yourself.

How Scan to Dispute works

You take or pick a photo — a statement line, a receipt, or a screenshot of the charge in your banking app.
The text is read in your browser. The reader is Tesseract.js, a JavaScript/WebAssembly port of the Tesseract OCR engine. OCR (optical character recognition) is mature, unglamorous technology: it turns pictures of printed text back into text. Nothing about it understands your dispute — it just reads characters.
You confirm every field. The date, amount and merchant it found are shown in editable fields. The date is spelled out in words ("Tuesday, August 13, 2026") because humans catch a wrong date in words far more easily than in digits. A date that works two ways — 03/04/2026 is March 4 in the US and 3 April in the UK — is put to you as an explicit question. Nothing is calculated before this step.
The confirmed details go to the deadline engine — the same rules engine behind the Chargeback Deadline Calculator, which checks the card-network window and the US federal windows and returns the earliest, binding deadline, with a calendar save, a printable summary and a route into the dispute letter generator.

Try it on the charge in front of you

Photo, confirm, deadline — free, no account, and the photo never leaves your device.

Scan my charge

Your photo never leaves your device

A bank statement is one of the most sensitive documents you own, so the architecture matters more than the promise. Scan to Dispute runs the OCR entirely on your device: the reader software is downloaded to your browser (its English language data is a few MB, cached in IndexedDB after the first download, so repeat use is fast), your photo is processed locally, and no image data is sent anywhere. There is no account and no upload — the same client-side-only pattern as every other tool on this site.

Be wary of the opposite design. Some statement tools ask you to upload the document to their servers for processing — including business OCR APIs that charge per page. That may be a fair trade for a company reconciling thousands of statements; for one consumer checking one deadline, it is exposure you do not need. If a tool wants your statement uploaded, read its privacy terms first.

How accurate is photo reading, honestly?

Short answer: nobody can give you a truthful percentage, and you should distrust anyone who does. Tesseract — the engine underneath — publishes no accuracy figure at all. What its official documentation does say, plainly, is where recognition struggles:

It works best on images of at least 300 DPI — in photo terms, close and sharp.
Its automatic light/dark separation "can be suboptimal, particularly if the page background is of uneven darkness" — shadows across the page are a real problem.
"The quality of Tesseract's line segmentation reduces significantly if a page is too skewed" — a tilted photo breaks lines before it breaks letters.
Noise the processing cannot remove "can cause accuracy rates to drop", and dark scan borders "can be erroneously picked up as extra characters".
Most relevant of all: "It is known tesseract has a problem to recognize text/data from tables" without custom configuration — and a bank statement is a table.
Handwriting is not supported; the FAQ says results "will be poor". PDFs are not read natively either — they must first be rendered as images, which is why this tool asks for a photo or a screenshot.

Put together, the honest expectation is this: on a straight, well-lit, close-up photo of printed statement text, most printed words read correctly — but any single character, including a digit in a date, can be misread. On a tilted, shadowed or faded thermal receipt, expect several errors. A screenshot of your banking app is crisp digital text and reads far better than any paper photo. This is precisely why the confirm step exists, why the date comes back to you in words, and why the result carries the instruction to check the fields against your statement before relying on the date. A scanning tool that skips the confirmation and shows you a deadline straight from a photo is not being clever; it is being careless with your money.

The two dates that run two different clocks

Scanning finds dates; it cannot decide which clock each one drives. That part is law, and it is where deadline mistakes actually happen:

Clock	Counts from	The rule
Card-network window	The transaction date	Visa, Mastercard, Amex and Discover each publish cardholder filing windows of up to 120 days from the transaction date. For goods never received, the window starts at the expected delivery date instead, capped at 540 days from the transaction. One honest note: the networks do not publish a single public consumer rulebook page for these windows — our calculator relies on the same published network guides it has always cited, and your issuer's agreement governs your case.
US credit — FCBA	The statement date	The Fair Credit Billing Act (15 U.S.C. §1666, mirrored in 12 CFR §1026.13) gives you 60 days from the date the statement was sent to dispute a billing error in writing.
US debit — Regulation E	The statement date	Regulation E (12 CFR §1005.11) sets the same 60-day error-notice window for electronic transfers. The bank generally must decide within 10 business days or provisionally credit you while it investigates (up to 45 days; 20 business days and up to 90 days for new accounts). Liability tiers in 12 CFR §1005.6 reward speed: report within 2 business days of learning of a loss and exposure is capped at $50; inside the 60-day window it can rise to $500.
UK credit — Section 75	The breach, not the statement	Section 75 of the Consumer Credit Act 1974 lets you claim against the card provider for breach of contract or misrepresentation on purchases of £100–£30,000, up to 6 years in England, Wales and Northern Ireland. A different process from a chargeback — and one that can still work after the chargeback window closes.

This is why the scan tool treats the two dates so differently. The transaction date can be pre-filled from the photo because you confirm it in words before it is used. The statement date is never copied from the photo — a statement page shows both dates side by side, and a reader that grabbed the wrong one would quietly corrupt the federal clock. You type the statement date yourself, from the statement, into its own labelled field. Slow on purpose, in exactly the place where a swap would hurt. For the full picture of how these windows interact, see the 60-day vs 120-day rule and how to never miss a chargeback deadline.

Taking a photo that reads first time

Prefer a screenshot. If the charge is in your banking app, screenshot it. Digital text is the easiest read there is.
Get close and square-on. Fill the frame with the statement line and hold the phone parallel to the page — skew is the silent killer.
Light it evenly. Bright, diffuse light; no shadow of your hand or phone across the text, and no flash glare on glossy paper.
Tap to focus on the line itself, and flatten crumpled receipts under a book for a minute first.
One charge per photo. A full statement page gives the reader dozens of dates and amounts to confuse; crop to the line you mean (the tool lists everything else it found, but a tight crop saves the sorting).

When typing beats scanning

Scanning is a shortcut, not a virtue. Type the details instead when:

The receipt is a faded thermal printout — the text the camera can barely see, the reader cannot see at all.
Anything important is handwritten — handwriting is not supported.
Your statement is a PDF — screenshot the relevant page first, or just type the one line.
You already know the date. If you can see "August 13" plainly, typing it into the deadline calculator is faster than any scan.

And whatever route you take: the amount in your dispute letter must match your statement exactly. A letter asking to reverse $129.90 on a $129.99 charge gives the bank a reason to doubt the whole letter. The confirm screen repeats the amount back for this reason — check it like you check the date.

FAQ

Can a photo really give me my chargeback deadline?

The photo supplies the facts — the transaction date, the amount, the merchant. The deadline itself is calculated from published card-network rules and US federal windows only after you have checked and confirmed those facts. A photo on its own proves nothing; it is a faster way of filling in the same checker you could type into.

Is my bank statement photo uploaded or stored?

No. With Scan to Dispute, the reading software (Tesseract.js) runs inside your browser on your device. Only that software is downloaded — once, after which it is cached — and your photo is never uploaded, stored or sent anywhere. Tools that ask you to upload a statement to their server work differently; read their privacy terms before using them.

How accurate is the OCR reading?

No official accuracy figure exists — Tesseract publishes none, and any site quoting you a percentage for photo reading is inventing it. The official documentation says recognition works best on images of at least 300 DPI, degrades with skew, uneven backgrounds and noise, and has a known problem with tables. On a straight, well-lit photo of printed text, most words read correctly, but any single character can be wrong — which is why every field must be confirmed before a deadline is calculated.

What if the tool reads the wrong date?

That is exactly what the confirm step is for: the date is shown back to you spelled out in words, dates that can be read two ways are put to you as a question, and every field stays editable. If you later spot that a deadline was based on a wrong date, re-run the check with the correct one — and when the two disagree, act on the earlier date. Filing early never hurts.

Does scanning work for UK cards?

The card-network window applies to UK cards too, and you can pick United Kingdom in the checker. The 60-day federal windows are US-only (FCBA for credit, Regulation E for debit). For UK credit card purchases of £100–£30,000, Section 75 of the Consumer Credit Act 1974 offers a separate claim route against the card provider, up to 6 years from the breach — the checker flags it when it applies.