PDF tamper detection API for lending and compliance teams.
Detect whether a bank statement, invoice, or contract was modified after it was generated.
31 forensic checks across metadata, file structure, and digital signatures — verdict in seconds.
By continuing you accept our Terms & Conditions. Maximum PDF file size is 10 MB.
The verification gap
KYC platforms verify the document. HTPBE verifies the file.
Two different checks — both matter.
KYC & identity platforms
Plaid · Persona · Alloy · Jumio
- Is this a real bank statement template?
- Does the account number match the identity?
- Is the document format consistent with the issuing bank?
Detects fake documents. Does not detect edited real documents.
HTPBE forensic API
Structural PDF integrity
- Was this specific PDF file modified after it was generated?
- Do metadata timestamps match the file structure?
- Were digital signatures valid at the time of signing?
Catches edits invisible to visual review and template checks.
Use Cases
Where teams use HTPBE
One API, three critical document workflows.
Bank Statement Verification
Catch edited balances and fabricated transaction histories before approving a loan application.
Learn more →Invoice Verification
Detect bank account swaps and amount changes in vendor invoices before payment is processed.
Learn more →Certificate & Diploma Verification
Expose edited academic credentials and professional certificates submitted during hiring or onboarding.
Learn more →Customer Stories
Teams that stopped document fraud
Compliance, finance, and risk teams use HTPBE to catch manipulated PDFs before they become costly mistakes.
Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.
Sarah M.
AP Manager
United States
We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document — it is in the file structure.
Lars V.
Risk Analyst, Online Lending
Netherlands
Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.
Priya K.
HR Operations Lead
India
Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.
Julien R.
Fraud Analyst, Fintech
France
Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for verified originals when something is flagged. Already saved us from a few bad decisions.
Marta S.
Compliance Coordinator
Spain
One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.
Tariq A.
Finance Manager
United Arab Emirates
Frequently Asked Questions
Get answers to common questions about PDF authenticity checking
HTPBE (Has This PDF Been Edited) is a free online service that detects whether a PDF document has been modified after it was originally created. Upload your PDF and get an instant result in seconds.
The service analyzes the PDF’s internal structure, metadata, and creation history to detect any signs of post-creation modifications. Results come in three states: Intact (no modification found), Modified (modification detected), or Cannot Verify (the PDF was created with consumer software such as Microsoft Word or Google Docs, where anyone can create a document from scratch).
Common scenarios: verifying payment confirmations from buyers, checking invoice integrity, validating certificates and diplomas, confirming contract integrity, and detecting document tampering.
You don’t need technical knowledge to use HTPBE—just upload your PDF and get clear results in seconds. The service is completely free, requires no registration, and works with PDF files up to 10 MB.
KYC platforms verify that a document looks authentic — correct template, matching identity, valid format. HTPBE checks whether the specific PDF file was modified after it was generated. These are different layers of verification.
A bank statement can pass every KYC template check and still have edited balances. HTPBE detects the modification at the file structure level — xref tables, incremental updates, producer field inconsistencies.
The API returns a structured JSON verdict: INTACT, MODIFIED, or INCONCLUSIVE. For modified documents, the response includes specific modification_markers — the named forensic signals that triggered the verdict, such as “Multiple xref tables detected” or “Incremental update chain length: 3”.
No black-box scores — every verdict is explained. See the full response schema at github.com/htpbe/docs.
Plans are monthly subscriptions: Starter at $15/mo (30 checks), Growth at $149/mo (350 checks), Pro at $499/mo (1,500 checks). There is no per-check billing — your quota resets monthly.
The free web tool at htpbe.tech is unlimited for manual checks and does not consume API quota.
Yes. Test keys (htpbe_test_...) are available on all plans including before you subscribe. They return deterministic synthetic results for integration testing and do not consume monthly quota.
Test keys only accept test URLs — they cannot be used to analyze real documents.
Yes — this is the primary use case for lending teams. HTPBE detects edited bank statements at the file structure level: multiple xref tables indicating post-export editing, producer field showing Excel or a consumer PDF tool instead of a banking system, and modification timestamps that differ from creation timestamps.
See the bank statement verification guide for integration details.