Supported document type
Detect tampered and deepfake Declaration
A signed declaration is one person asserting facts about themselves with no counterparty holding a matching copy, which makes it the weakest document in most onboarding files. Two separate things go wrong with it. The declared facts can simply be untrue, which no forensic analysis can see and only the supporting documents can contradict. Or the paper itself is altered: a figure changed, a date moved, a signature added to a page the declarant never completed. TamperCheck addresses the second.
API slug: declaration
Last updated:
What a genuine declaration contains
A declaration names the declarant with enough identifying detail to tie the statement to a person, sets out the declared facts as numbered statements or as ticked options on a printed form, and carries a statement of truth or a penalty clause spelling out the consequence of a false declaration. It ends with the place and date of signing and the declarant's signature. Many also carry a witness or notary block, and most sit on an organisation's own template, which means a form reference, a version number, and fixed field boxes appear in the margins and footer.
A declaration is checkable mainly against the file it arrived in. The declared address, income, dates, or dependants are meant to agree with the identity document, bank statements, and employer letters submitted alongside it, so the statement is really a set of claims other documents have to corroborate. Inside the page, the place and date anchor the statement of truth, the form version fixes exactly which fields exist, and the whole thing was written in one sitting. Entries in more than one hand or ink, or a field the stated form version does not have, are contradictions.
How declaration forgeries are made
Figures changed after signing
The declaration is genuine and one declared value is not: an income band, a length of residence, a number of dependants, a threshold answer. The signature below is real, which is what gets it accepted, and the altered characters carry a compression and rendering history the characters around them do not.
Signature applied to a page the declarant never saw
A signature is copied from an application form or identity document in the same file and placed on a declaration the person never made. The source is usually inside the same bundle, so the transplanted mark can be matched back to the document it came from, edge artefacts and all.
Place and date edits
The date or the stated place of signing is changed so a declaration appears to have been made before an event it was intended to cover, or within a window an application requires. This breaks the declaration against the file timestamps and against any received stamp the intake team applied.
Fields the form version never had
Where a declaration is rebuilt rather than filled in, the reconstruction drifts from the template: a field that does not exist on the version quoted in the footer, a label reworded, a box at the wrong width. Comparing the layout against the stated form version exposes the reconstruction even when every value on it is plausible.
Witness blocks added later
An unwitnessed declaration is given a witness name and signature to raise its standing. The added block usually sits at a baseline slightly off the form's own grid, and the witness details rarely correspond to anyone else in the file.
Whole declarations composed digitally
A blank template is reproduced and typed into, then saved as a scan-alike. Every value is consistent because nothing was ever transcribed by hand. What is missing is the evidence of capture: no paper texture, no scanner noise, and handwriting that shows none of the pressure variation a pen leaves.
What TamperCheck checks on a declaration
TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.
Signature forgery analysis
Signature regions are assessed for ink consistency and for how the stroke sits on the page, which distinguishes a genuine pen stroke from a pasted image of one.
Date and validity consistency
Issue, expiry, and period dates are checked against one another and against the file's own creation metadata, which catches backdating and validity extension.
Field-level forensics
Every text region is analysed in its own right rather than as part of one whole-page image. This catches the smoothed and feathered edits that whole-image Error Level Analysis misses entirely.
And many more checks
The three above are the layers that carry the most weight on a declaration. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.
Who verifies a declaration, and why
Compliance teams validating applicant statements during onboarding. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.
How to verify a declaration in 4 steps
Check the fields against each other
Read declared facts, signature, and declaration date together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.
Inspect the file metadata
Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.
Ask for a second document
Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.
Run a forensic check
Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 200+ forensic checks on a declaration and returns a risk score from 0 to 100 within seconds, at $0.50 per document.
Frequently asked questions
How do I verify a signed declaration?
Corroborate the declared facts against the other documents in the same file, because a declaration proves nothing on its own and is only as good as what supports it. Compare the declared address, income, and dates against the identity document and statements submitted with it, confirm the signature matches the one on those documents, and check the form version in the footer against the layout on the page.
Can a declaration form be tampered with?
Yes, and it is among the easiest documents to alter, because there is no issuer, no seal, and usually no second copy in anyone else's hands. The common edits are a single declared figure, a date, or an added signature. Each leaves the changed region with a different rendering and compression history from the untouched text beside it.
What is the difference between a declaration and an affidavit?
A declaration is signed by the declarant alone, while an affidavit is sworn or affirmed before an officer authorised to administer an oath, who then certifies it. That makes an affidavit evidence a court will take and a declaration a statement that mainly binds the declarant to its penalty clause. Forensically, the affidavit gives you a seal and a jurat to test, and the declaration does not.
Can you tell if a declaration was signed at the same time it was completed?
Often, yes. Entries made in one sitting share a pen, an ink profile, and a consistent hand, so a field completed later shows different stroke width, ink density, or line pressure from its neighbours. On a scanned or digital form, the same question is answered by comparing the rendering history of each field region against the rest of the page.
TamperCheck analyses declaration uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API & MCP documentation for authentication, async jobs, and webhooks.