Forged document detection.Transfers, bank statements, payslips and medical documents.
We detect edited amounts, names and dates, misleading statuses, balance breaks, editing software and documents submitted more than once — and mark the exact spot on the document. Results in under a minute.
Illustration of the inspection · sample document
What we detect
The forgery types we detect in transfers, statements, payslips and sick notes.
A balance break in a bank statement — detected and marked
The balance is recomputed on every row and the edited transaction is marked. Drag the line to compare.
- Row-by-row balance verification
- Precise marking of the edited cell
- A plain-language explanation for every finding
| Date | Description | Credit | Debit | Balance |
|---|---|---|---|---|
| 01.09 | Salary | 14,200.00 | 18,450.00 | |
| 03.09 | Rent | 5,600.00 | 12,850.00 | |
| 07.09 | Transfer from D. Levi | 19,000.00 | 21,850.00 | |
| 10.09 | Credit card | 3,120.00 | 18,730.00 | |
| 15.09 | Insurance | 410.00 | 18,320.00 |
| Date | Description | Credit | Debit | Balance | |
|---|---|---|---|---|---|
| 01.09 | Salary | 14,200.00 | 18,450.00 | ||
| 03.09 | Rent | 5,600.00 | 12,850.00 | ||
| 07.09 | Transfer from D. Levi | 19,000.00 | 21,850.00 | ||
| 10.09 | Credit card | 3,120.00 | 18,730.00 | ||
| 15.09 | Insurance | 410.00 | 18,320.00 |
Six detection layers. One risk score you can explain.
A language model alone can be wrong. That is why every document also goes through deterministic checks of the file structure, the arithmetic and the submission history — and every finding comes with its explanation.
The documents we check
ThisVerify knows the structure of Israeli documents — from banking apps and statements, through payslips, to HMO sick notes — and runs each one through its own checklist.
Forgery detection for bank transfers and receipts
We detect: edited amount, payee, date and reference · pending, scheduled or cancelled status · browser printing after editing the page · editing software in the file · a receipt submitted more than once. Every Israeli bank, PDF or screenshot.
- Amount, payee, date and reference in one consistent font and weight
- Status: executed, pending, scheduled or awaiting a second approver
- Bank code, branch and IBAN with check digits
- Weekday versus date, and time versus the device clock
Forgery detection for bank statements and transaction histories
We detect: edited transactions or amounts · running-balance breaks · deleted or inserted rows · swapped pages · dates that contradict the weekday · edited account-holder details. Current accounts and credit cards, every bank.
- Running-balance continuity, row by row
- Row height, fonts, column and decimal alignment
- Value and transaction dates versus weekdays
- Account holder, bank code and branch
| 01.09 | Salary | +14,200 | 18,450 |
| 03.09 | Rent | -5,600 | 12,850 |
| 07.09 | Deposit | +19,000 | 21,850 |
| 10.09 | Card | -3,120 | 18,730 |
Forgery detection for payslips and Form 106
We detect: edited gross or net pay · edited working days and pay components · swapped employee name, ID or employer details · template-built payslips · editing-software traces in the file.
- Gross, net and working days — font, weight and alignment
- Employer details, company number and withholding file
- Employee details and ID with check digit
- Layout of common payroll systems
Forgery detection for sick notes and medical documents
We detect: edited number of sick days · shifted visit, issue and leave dates · edited doctor name or licence number · adjusted lab values and diagnoses · pasted stamps. Sick notes, visit and discharge summaries, lab results and prescriptions.
- Number of sick days and incapacity period
- Visit date, issue date and start/end of the period
- Doctor name and licence number
- Lab values and reference ranges
Three seconds to upload. Under a minute to know.
- 1
Upload the document
PDF, screenshot or photo. Optionally add the amount and name you expect to see.
- 2
Six layers run in parallel
Structure, metadata, pixels, visual analysis, logic and history.
- 3
Get a clear report
A risk score, findings marked on the document, a recommended action — and a chat to ask about the report.
Built for people who make decisions based on documents
From a merchant receiving a Bit screenshot to a lender reviewing thousands of statements a month.
Businesses and sellers
Got a "transfer confirmation" before handing over goods? Check it before anything leaves.
Landlords and agents
Payslips, bank statements and balance confirmations from prospective tenants.
Lenders and credit
Income and equity documents at onboarding, through the dashboard or the API.
Insurance and claims
Receipts, invoices, medical documents and test results submitted with claims.
Employers and HR
Sick notes, payslips and documents submitted in hiring and absence management.
Accountants, lawyers and investigators
A documented first-pass review before a full forensic examination.
Financial documents deserve bank-grade security
Your documents contain sensitive information. Every file is encrypted before it is stored, accessible only to you, and deleted automatically when its retention period ends.
- AES-256-GCM encryption for every file and key
- Private storage in Frankfurt, no public links
- Strict isolation between accounts
- Audit log for every administrative action
- scrypt password hashing and brute-force protection
- Automatic deletion by retention policy
A simple API for automated workflows
Send a file, get a risk score, located findings and extracted data as JSON. Built for onboarding, underwriting and payment approval flows.
curl -X POST https://www.thisverify.com/api/v1/scans \
-H "Authorization: Bearer $THISVERIFY_KEY" \
-F "file=@transfer.png"
{ "verdict": "high_risk", "risk_score": 87,
"findings": [{ "category": "text_edit",
"severity": "high", "box": { "x": 30, "y": 40 } }] }Read the API docsStart free, grow as you need
Every plan includes every detection layer.
Trial
Get to know the platform and run occasional checks
- 10 checks per month
- Every document type
- Full findings report
- Files kept for 7 days
Professional
For businesses and professionals who check documents regularly
- 200 checks per month
- All detection layers
- Chat with the report
- Report export
- Files kept for 30 days
Business
For teams with high volumes and API integration
- 1,500 checks per month
- API access
- Batch checks
- Files kept for 90 days
- Priority support
Enterprise
For banks, lenders, insurers and real estate
- Custom volume
- SLA and data processing agreement
- Dedicated knowledge model
- Deployment in your cloud
- Dedicated account manager
Questions to ask before you trust a document
Can the system tell for certain that a document is forged?
It points to evidence and grades the risk. A "high risk" result rests on clear evidence such as edits, logical contradictions or editing software — but the final decision should be made by a person, and when in doubt you should confirm with the bank.
Which files can I upload?
PDF, JPG, PNG, WEBP and HEIC up to 10MB. Always upload the original file rather than a photo of a photo.
How long does a check take?
Usually 15 to 60 seconds, depending on size and page count.
What happens to the documents I upload?
They are encrypted and stored privately for your plan's retention period, then deleted automatically. You can delete a check at any time.
Does it work on phone screenshots?
Yes. Screenshots from banking apps, Bit and PayBox are among the most common documents we check, and they have a dedicated checklist.
Your next check could save thousands
10 free checks every month. No credit card.