Fake medical certificate detection API
Detect sick notes, doctor’s notes, and fitness-to-work certificates that were edited after a clinic issued them. One API call reads the PDF’s own structure and returns forensic evidence of post-issuance modification – at intake, before a claim is paid or an absence is approved.
HTPBE? analyzes the structural layer of the PDF file – the layer that records every edit, even invisible ones. We do not verify whether the person was actually ill, whether the diagnosis is real, whether the issuing practice or doctor is licensed, or whether anything written on the certificate is true. We answer one narrow question: does this file show evidence of having been written to after it was issued? Medical facts and practitioner registration are a separate check, and we do not replace them.
What a verdict is worth depends on how the certificate reached you. A certificate that arrives digitally signed by the practice gives the strongest basis for a verdict. A paper note that the employee scanned or photographed can never be INTACT – INCONCLUSIVE is the ceiling for scans, and on this document type scanned notes are the normal case, not a red flag. Treat INCONCLUSIVE on a scan as the expected baseline; treat it on a document that claims to be a direct clinical export as a reason for manual review.
The problem
A real sick note, edited after it was issued, prints identically
The common sick-note fraud is not a document invented from nothing. It is a genuine certificate that a real clinic issued – for two days, for last month, for a colleague – reopened in a PDF editor or a word processor and saved again with a different date, a different name, or a longer absence period. Nothing about the page betrays it. The letterhead is real, the layout is real, the stamp is real, because they came from a real document.
Claims teams and HR administrators review these documents on screen. Screen review cannot see an edit that leaves no visual trace, and it cannot compare a submission with an original that the reviewer has never held. Neither can OCR: extracting the text tells you what the file says now, not whether it said something else when the clinic produced it.
The file itself keeps a record. Editing a PDF leaves evidence in the file’s structure, usually along with traces of the tool that did the writing. HTPBE? reads that record directly from the binary structure and reports what it finds, with named markers, in about three seconds.
Common sick-note and fitness-to-work fraud patterns
- Absence period extended – the end date pushed out by days or weeks
- Dates moved so an old certificate covers a recent absence
- Patient name replaced with the name of the person submitting it
- Diagnosis or restriction text rewritten to support a disability claim
- A fitness-to-work clearance edited to remove stated work restrictions
- Clinic letterhead lifted from a genuine note and reused on a fabricated one
- Pages taken from several documents and assembled into one certificate
What this looks like
Document fraud in 2026 – three concrete patterns
Three real fraud mechanics we catch at the structural PDF layer.
Absence period extended – the end date pushed out by days or weeks
Dates moved so an old certificate covers a recent absence
Patient name replaced with the name of the person submitting it
Diagnosis or restriction text rewritten to support a disability claim
A fitness-to-work clearance edited to remove stated work restrictions
Clinic letterhead lifted from a genuine note and reused on a fabricated one
Pages taken from several documents and assembled into one certificate
The detection gap
KYC platforms check the document. HTPBE? checks 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? tamper detection API
Structural PDF integrity
- Was this specific PDF file modified after it was generated?
- Does the file carry evidence of editing after export?
- Were digital signatures valid at the time of signing?
What HTPBE? checks
Forensic signals analyzed in every medical certificate
Five layers of structural analysis – results in under 3 seconds
Multiple revision layers
Writing to a PDF after the clinic produced it usually leaves an extra revision layer inside the file – the primary structural marker that a document was changed after issuance.
Re-saved by another tool
HTPBE? detects a certificate that was opened in another tool and saved again after the clinic produced it.
Judged on the file, not the letterhead
Traces of a consumer PDF editor show which tool last wrote the file. However closely it copies a practice’s layout, a certificate comes back MODIFIED when the file itself carries evidence of editing or fabrication, whatever tool produced it. INCONCLUSIVE means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud.
Dates that disagree
HTPBE? flags a certificate whose own internal dates show it was written to after it was first produced, whatever the reason for the edit. The check does not depend on any date printed on the page.
Signature removal and post-signature edits
Where a practice signs certificates digitally, HTPBE? detects both content changed after signing and a signature block that was stripped out before re-submission. Both return ‘certain’ confidence – the highest verdict level we issue.
Multi-source page assembly
HTPBE? checks how the pages of a document came together. Pages assembled from independently rendered sources indicate a certificate built from parts of other files rather than issued by the practice as it stands.
Share with engineering
Wire this into your intake pipeline in under a day
Two API calls – one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.
Pricing
Self-serve plans, no sales call
All plans include the same forensic checks. Pick the quota that matches your monthly document volume.
manualStarter
30 credits/mo
Manual spot-checks and integration testing
most commonGrowth
350 credits/mo
Active document processing pipelines
high volumePro
1,500 credits/mo
High-volume automation and API integrations
Enterprise (unlimited, on-premise available) — see full pricing
API key on signup. Free test environment on every plan. No card required.
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
FAQ
Frequently asked questions
Which medical certificate types can be checked?
Can you verify that the doctor or clinic on the certificate is real?
What does a ‘modified’ verdict mean for a sick note?
Most of our sick notes are scanned or photographed. Does that change the result?
Can you tell which field was changed – the dates, the name, the diagnosis?
How does this fit into an HR absence or claims workflow?
POST /v1/analyze, read the verdict from GET /v1/result/{id}, and route anything returning modified into a manual review queue rather than into an automated decision. The call adds under three seconds, and the returned id can be stored against the absence or claim record as an audit trail. Given that certificates are health-related documents, we recommend a human reviews every flagged case before any action is taken, and that a verdict never triggers an automatic decision about a person.What about a certificate generated from scratch by an AI tool or a template site?
modified when the file itself carries evidence of editing or fabrication, whatever tool produced it. An inconclusive result means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud. Checking with the issuing practice is a sensible next step.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.