API use cases

PDF fraud detection API use cases

One API, six fraud detection workflows. Plug forensic PDF analysis into your lending, accounts payable, HR, claims, or contract management pipeline – without changing the rest of your stack.

Same API, every workflow

One endpoint behind every fraud check

Every use case below uses the same POST /v1/analyze endpoint. The verdict shape — intact, modified, or inconclusive — is identical regardless of document type. Only the named markers in the response differ.

Same key, same quota, same SDK. Bank statements, invoices, certificates, and contracts share one integration; you are not buying separate vendors per document type.

No comparison against a ‘clean’ original or third-party database — HTPBE? reads the PDF’s internal structure and decides on its own.

~3 sec
per document
63
forensic checks per document
1,500+
docs / month on Growth
Plans
subscriptions or one-off packs – see pricing

Featured patterns

Six fraud patterns we catch most often

These six document types account for the bulk of submitted document fraud across lending, hiring, AP, and claims workflows. Each card lists typical findings the engine reports and links to the integration guide.

Bank statement fraud detection

Detect Excel-edited and fabricated bank statements before they reach underwriters. 59% of fraudulent documents in lending are bank statements.

  • Produced or reworked outside a banking system
  • Edits saved after the statement was exported
  • Modification date that differs from the creation date
Integration guide

Invoice tamper detection

Detect tampered invoices before payment. Catch altered amounts, payee details, and bank account numbers that look identical to the originals.

  • Edits saved after the invoice was issued
  • Character-level overlays on the original values
  • Signs of an online PDF editor instead of accounting software
Integration guide

Certificate fraud detection

Detect fake diplomas, forged credentials, and altered certificates of completion before hiring. No original document or database required.

  • Signs of consumer PDF software on an ‘institutional’ certificate
  • Modification date that differs from the creation date
  • Edits saved after the certificate was issued
Integration guide

Contract tamper detection

Detect clause changes, signature bypass, and post-signing modifications. Post-signature modification is flagged at ‘certain’ confidence.

  • Modifications after digital signature – ‘certain’ confidence verdict
  • Signature removal detected in document structure
  • Dates inside the file that disagree
Integration guide

Insurance claims fraud detection

Detect altered repair estimates, inflated medical reports, and fabricated receipts at document intake, before adjuster review.

  • Signs of a consumer PDF editor on a claims document
  • Edits saved after the document was issued
  • Dates inside the file that disagree
Integration guide

Immigration document fraud detection

Detect tampered visa documents before submission. Catch edited bank statements, forged recommendation letters, and altered Certificates of Sponsorship.

  • Modification date inconsistency in a Certificate of Sponsorship
  • Post-signature edits on a recommendation letter
  • Excel-modified bank statement submitted as visa evidence
Integration guide

What ships in the box

Three properties that simplify your integration

one integration

One key, one endpoint, every document type

Bank statements, invoices, certificates, contracts – all share the same account and quota. Add a new document type to your pipeline without procurement.

no original needed

Structural analysis, not comparison

HTPBE? reads the PDF’s internal structure on its own. There is no comparison against a ‘clean’ original or a third-party institution database to maintain.

self-serve

From signup to first call in minutes

No sales call, no procurement process. Test keys are available on every plan for staging environments and CI pipelines.

By role

Fraud detection by team

Same engine, framed for the team that owns the workflow. Each page maps the detection layers to the document types your team sees.

How it works

Five forensic layers, one deterministic verdict

Every PDF we receive passes through the same structural pipeline – no model training, no thresholds to tune.

01

Metadata analysis

The dates and origin details recorded inside the file – the first layer flags signs of editing after creation.

02

File structure

How the file was built and saved over its lifetime. Edits made after export typically leave evidence at this layer.

03

Digital signatures

Signature chain integrity and post-signature modifications produce deterministic markers. Certainty-level signal.

04

Page assembly

How pages and their embedded resources were put together. Pages combined from different sources and later insertions surface at this layer.

05

Verdict with markers

Deterministic output: INTACT / MODIFIED / INCONCLUSIVE, with named markers for every finding – suitable for audit trail.

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 checked 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

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.