Point your camera at the charge. This tool reads the date, amount and merchant from a photo of your statement or receipt — inside your browser, so the photo is never uploaded — and checks every deadline that applies. You confirm every field before anything is calculated, because software can misread a single digit.
Snap the charge — get your deadline
Private by design — your photo is read in your browser and never uploaded.
Advertisement
How it works
Three steps — and the checks that keep the answer honest
Photograph the charge. A statement line, a receipt, or a screenshot from your banking app. The reading software (Tesseract.js, an OCR engine — it reads printed text, nothing more magical than that) runs in your browser. The photo itself never leaves your device.
Confirm every field. The date, amount and merchant it read are shown back to you — the date spelled out in words, so a misread digit is easy to spot. If a date can be read two ways (03/04 is March 4 in the US and 3 April in the UK), the tool asks you which it is instead of guessing. The statement date is never filled in from the photo at all — you type it yourself, so the two clocks can never be swapped.
Get your deadline. The confirmed details go through the exact same rules engine as our Chargeback Deadline Calculator — no separate math, no separate numbers.
Clock
The rule that applies
Card-network window
Published Visa, Mastercard, Amex and Discover dispute rules: 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
US credit cards — FCBA
Fair Credit Billing Act (FCBA): you have 60 days from the date your statement was sent to dispute a billing error in writing (15 U.S.C. §1666; 12 CFR §1026.13)
US debit cards — Reg E
Regulation E: notify your bank of an error within 60 days of the statement (12 CFR §1005.11); liability tiers in 12 CFR §1005.6
UK credit cards — Section 75
A separate route, not a chargeback: claim against the card provider for breach of contract or misrepresentation on purchases of £100–£30,000, up to 6 years (Consumer Credit Act 1974, s.75)
Why the confirm step is not optional
Statement photos are exactly the hard case for text-reading software: the official Tesseract documentation notes it works best on sharp images of at least 300 DPI, that skewed pages and uneven backgrounds degrade it, and that it has a known problem reading tables — and a bank statement is a table. So this tool is built on one assumption: the reading will sometimes be wrong, and the design must catch it. You see the date in words. Ambiguous dates are put to you as a question. Extra dates and amounts found on the page are listed so you can pick the right line. And if the photo cannot be read at all, the same form simply opens empty — typing works just as well.
The full story: photo deadlines, done honestly
How the reading works, how accurate it really is (no invented percentages), how to take a photo that reads first time, and when typing beats scanning.
No. The photo is read by OCR software (Tesseract.js) that runs inside your browser on your own device. Only the reader software downloads, once; your photo is never uploaded, stored or sent to any server. That is also why the tool works on screenshots of your banking app.
There is no honest percentage: Tesseract publishes no accuracy figure, and results depend on the photo. On a straight, well-lit, close-up photo of printed statement text, most words read correctly — but any single character, including a digit in a date, can be misread. Tilted, shadowed, crumpled or faded thermal receipts read worse, and tables are a known weakness. That is why this tool never calculates from a reading directly: you see every field, in words, and confirm or fix it first.
Both, for different clocks. The network window counts from the transaction date; the US federal 60-day window counts from the statement date. This tool keeps the two fields separate and never copies a statement date into the transaction field — you type the statement date yourself, from the statement, so the two clocks cannot be mixed up.
Straight-on, close and well-lit beats everything else. A screenshot of the charge in your banking app is digital text and usually reads best of all. Handwriting is not supported, PDFs are not read directly (screenshot the page instead), and the reader is loaded for English text.
Sources (checked October 24, 2026): Tesseract.js official repository and FAQ (github.com/naptha/tesseract.js — WebAssembly port of Tesseract; language data cached in IndexedDB; handwriting not supported); Tesseract documentation, "ImproveQuality" (tesseract-ocr.github.io — best at 300 DPI or more; skew, uneven backgrounds and tables degrade recognition); Fair Credit Billing Act, 15 U.S.C. §1666 and 12 CFR §1026.13 (60 days from the statement, credit); Regulation E, 12 CFR §1005.11 and §1005.6 (60 days from the statement, debit). Card-network filing windows and the Section 75 route are the same sourced rules used by our deadline calculator (network guides at chargeback.io and chargeflow.io; UK guides at experian.co.uk, which.co.uk, oceanfinance.co.uk — verified October 17, 2026).
General information only — not legal advice. Deadlines here are planning figures computed from published card-network rules and statutes. Your cardholder agreement governs your dispute; verify with your issuer.
Chargeback Clock