ProductsIndustriesFAQsContactAPI DocsLoginBook a demo
Industries

Catch the edit before you cut the cheque.

Manipulated income proofs and edited statements surface in claims and underwriting every day. TrueShield names the edit - the field, the font, the broken total - before the payout leaves.

Try it free → Book a demo →

Free trial credits included · Full API documentation

Sample reportSAMPLE VERDICT
DocumentIncome proof · PDF
Tamper checkFailed
ReasonAmount field edited
IdentityPAN ↔ policy: match
Routed toInvestigation queue
⚠ Flagged for reviewAPI docs →
The problem

Where claims fraud hides

Most manipulated documents aren't crude fakes. They're real documents with one number changed - and one number is all it takes.

The convincing editA genuine statement with an inflated amount passes visual review. Forensics that examine fonts, spacing and totals don't get fooled by neat work.
Identity driftThe claimant, the policyholder and the PAN on file should be the same person. In fraudulent claims, they quietly aren't.
Patterns across transactionsDeposits staged before a claim and circular transfers are invisible on paper - and obvious in structured data.
What we check

What we check for insurers

Document forensics, identity matching and transaction analysis - assembled for the two moments that matter: underwriting and claims.

Edited-document detection, with the reasonEvery document is screened for alterations, and a failure names what changed - so investigators act on evidence, not suspicion. The OCR layer reads scans and photos as readily as digital PDFs.
Income proof validationSalary slips, bank statements and tax records are checked for internal consistency - and against each other.
PAN-to-policy identity matchPAN records confirm the person claiming is the person insured, catching identity drift between policy issue and claim.
Irregular transaction flagsStatement analysis surfaces staged deposits and unusual movement patterns around the claim window.
How it works

From claim intake to verdict

Intake

Documents attach to the claim exactly as they do today - PDFs, scans or photos.

Forensics

OCR extracts the data, then tamper, consistency and identity checks run together.

Verdict with reasons

Clean claims accelerate; flagged ones reach your investigation team with the evidence already assembled.

Works well with

The APIs behind the claims flow

Every call is encrypted in transit and at rest, DPDP-aligned, and logged with a full audit trail - and the data stays in India.

Advanced Bank Statement AnalyzerThe full financial picture behind a claim.Explore →
PAN Validator AdvanceName-match scoring against PAN records.Explore →
Income Tax Return VerificationStated income, checked against what the taxman saw.Explore →
FAQ

Before you put this in the claims path

What does the tamper verdict actually say?

Instead of a bare score, the verdict names what changed - an edited amount, a shifted date, mismatched fonts or a broken running balance - so claims teams can act on evidence.

Where does this fit in the claims process?

Most insurers run it at claim intake on income proofs and bank statements, and again at underwriting for high-value policies - both are single API calls.

Can identity be matched across documents?

Yes. PAN records are matched against the policyholder's stated details, so the person claiming is verifiably the person insured.

Does it work on scanned documents?

Yes. The OCR layer reads scans and photos as well as digital PDFs, then the same tamper and consistency checks run on the extracted data.

Pay the real claims faster. Catch the rest.

Free trial credits and full documentation from day one.

Start free trial or book a 20-minute call