How do I verify a PDF is authentic without the original to compare against?
You don’t have a copy to match it against, so you read the evidence inside the one PDF you were sent. A genuine file carries a consistent internal history: timestamps that line up, one clean revision layer, a producer fingerprint that fits the system that should have made it, an intact signature state if it was signed. An edited file breaks that consistency somewhere.
HTPBE? runs exactly this one-sided structural analysis and returns Intact, Modified, or Cannot Determine. It tells you whether the file was edited after it was generated — not whether the content is true, and not who sent it. Check whether a PDF is real →
← Previous
Why does my PDF show a creation date in the future?
Next →
How do I verify a bank statement is real?
Related questions
Keep reading
3 answers
A genuine bank statement is written directly by the bank’s core system, which leaves a distinctive structural signature. Re-save it through an editor or rebuild it in a spreadsheet and the file picks up a consumer-tool producer fingerprint and timestamps that drift apart — the mismatch HTPBE? flags as Modified.
The boundary: this checks the file, not the facts. It tells you whether the PDF was edited after the bank produced it. It does not confirm the account holder’s identity or that the balance is true — for that, pull the statement straight from the bank. See fake bank statement detection →
Most start by eyeballing logos, fonts, and totals — all of which a careful forger can reproduce. The structural layer is harder to fake. So lenders increasingly add an automated file check that catches edits hiding behind a correct-looking layout: a spreadsheet rebuild, an editor re-save, a balance changed after export.
HTPBE? runs that check at scale through the API — a verdict plus the named markers behind it for every statement in an application. It is a file-integrity layer that runs alongside identity and income verification, not instead of it. Bank statement detection guide. See the API →
Check that the net-pay maths, pay dates, and employer details are internally consistent, then look at how the file was produced. The most common forgery is a real payslip re-typed or edited in Word and exported again — which changes the producer fingerprint and the revision history HTPBE? reads.
HTPBE? tells you whether the payslip PDF was altered after it was generated. It does not confirm that the employer or the salary figure is real. That is the employer’s record to confirm, not the file’s. See fake salary slip detection →