logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.25.2

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland 🇫🇮

Status

Algorithm v2.25.2

Back to FAQ
FAQ

How do I verify a payslip or salary slip is genuine?

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 →

← Previous

How do lenders and underwriters verify bank statements?

Next →

How do I verify a certificate of authenticity or a diploma?

Related questions

Keep reading

3 answers

How do I verify a certificate of authenticity or a diploma?

The question has two halves. One: was the certificate PDF edited after it was issued? A changed name, grade, or date usually leaves structural traces that surface as Modified — and that is what a tamper check answers.

The other half — whether the issuing body actually awarded the certificate — no file check can answer. That lives in the registrar’s or awarding body’s records. Use HTPBE? to rule out file tampering, the issuer’s own portal to confirm the record. See fake certificate detection →

Does verifying a PDF mean you need the original to compare against?

No. That is the most common myth. You don’t need a reference copy — structural analysis reads the evidence already inside the file you were sent: its revision layers, cross-reference structure, timestamps, producer fingerprint, signature state.

That is what lets HTPBE? return a verdict on a file you have never seen, from a sender you can’t reach. One question — was this file edited after it was created — answered without ever comparing it to an original. How one-sided PDF analysis works →

Does HTPBE? verify someone’s identity, or that a document is valid against the issuer?

No. HTPBE? verifies one thing only: whether the file was edited or forged after it was issued. It does not confirm a person’s identity, it does not check a document against the issuing authority’s records, and it does not judge whether the content is true.

Those are separate jobs. Identity — “is this really them” — belongs to KYC/IDV platforms such as Persona or Onfido. Confirming a record belongs to the issuer’s own portal. HTPBE? is the structural file-integrity layer that runs alongside them — tamper detection, not a verification platform. How HTPBE? differs from KYC platforms →