Supported document type
Detect tampered and deepfake Loan Closure Certificate
A loan closure certificate, also called a no-dues certificate, is the lender saying a borrower owes nothing further and the security is released. People forge it to erase a liability before a new application, or to sell an asset that is still charged. The certificate is a short letter, so the risk sits in the closure date, the nil-outstanding statement, and the lender's stamp and signature.
API slug: loan_closure_certificate
What a genuine loan closure certificate contains
The certificate comes on the lender's letterhead and identifies the borrower, the loan account number, the type of loan, and the date it was closed. It states that no amounts are outstanding, lists security or original documents being released or returned, and carries a stamp and an authorised signatory. Some lenders include a reference number and a date of issue distinct from the closure date.
Dates have a fixed order: the final payment, then the closure, then the certificate. A certificate that predates the final payment, or a closure date that falls after the letter's own date, is inconsistent. The loan account number and borrower details should match the earlier sanction letter, statements, and bank debits, and the security described should be the asset the borrower is now offering.
How loan closure certificate forgeries are made
Nil balance overwrite
A letter that showed an outstanding amount, or a foreclosure quote, is converted into a closure statement by replacing the figure and wording. The overwritten sentence differs in rendering from its neighbours.
Backdated closure
The closure date is moved earlier so a liability appears to have ended before a credit application. The date then precedes the last recorded debit on the borrower's bank statement.
Stamp and signatory paste
A branch stamp and an officer's signature are copied from an unrelated letter. Pasted marks keep the sharpness of their source and fail to sit consistently on the paper texture.
Borrowed closure letter
A genuine certificate for another borrower or another loan is relabelled with new names and numbers. The edited fields are the weak point, and the loan account number conflicts with other papers.
What TamperCheck checks on a loan closure certificate
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.
Stamp authenticity and placement
Stamps are assessed for whether the ink was impressed onto the page or printed as part of it, and for whether the impression was placed digitally after the fact.
Letterhead, logo, and issuer plausibility
Issuer branding is checked for resolution and compression consistency against the body text it sits on. A logo lifted from a website carries the signature of its source, not of the document.
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.
And many more checks
The three above are the layers that carry the most weight on a loan closure certificate. 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 loan closure certificate, and why
Banks, underwriters, property buyers, and vehicle-finance reviewers. 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 loan closure certificate in 4 steps
Check the fields against each other
Read closure date, nil outstanding statement, and loan account number 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 loan closure certificate and returns a risk score from 0 to 100 in about a minute, at $0.50 per document.
Frequently asked questions
How do I verify a no dues certificate?
Confirm with the lender's branch using contact details you found yourself, and check that the closure date follows the final payment on the borrower's bank statement. Forensic analysis of the certificate looks for overwritten amounts and pasted stamps or signatures.
Are loan closure letters forged?
Yes, especially when a borrower needs a clean record for a new loan, a visa file, or the sale of a charged asset. The letter is short and unadorned, and the reward for a convincing copy is high.
What should a loan closure certificate contain?
The borrower's name, the loan account number, the closure date, a statement of no outstanding dues, a list of security or documents released, the lender's stamp, and an authorised signature. Its date of issue should be after the closure date.
Is a closure certificate the same as a payoff statement?
No. A payoff statement is a quote of what must be paid to end the loan. The closure certificate is issued after payment and confirms the loan is settled and the lender's claim on the security has ended.
TamperCheck analyses loan closure certificate 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 documentation for authentication, async jobs, and webhooks.