How to Verify an E-Stamp Certificate Is Genuine (and Matches the Agreement It Is Attached To)
Fake and reused stamp papers are an old problem with a new form. How to verify an e-stamp certificate online, what to check on the certificate against the agreement, the signs of a reused or altered certificate, and how to make verification a step in your contract workflow.
An e-stamp certificate is only as good as its match to the document it accompanies. A genuine certificate attached to the wrong agreement, a certificate reused across several agreements, or an altered PDF of a certificate each leaves the agreement unstamped in law, with the consequence under section 35 of the Indian Stamp Act, 1899 that it cannot be admitted in evidence until duty and penalty are paid. This guide explains how to verify a certificate and what to compare. Position as of October 2026.
What a genuine certificate shows
E-stamp certificates issued through SHCIL's system or a state treasury portal carry: a unique certificate number; the date and time of issue; the account reference; the names of the first party, second party and the party paying the duty; the description of the instrument (article); the consideration or value; the stamp duty amount; and a verification mechanism (a QR code, a barcode or an online lookup). The layout varies by state and system. ****
How to verify online
- Go to the issuing system's verification page (SHCIL's e-stamp verification for states it serves; the state treasury portal for GRAS, e-GRAS and similar systems).
- Enter the state, the certificate number and, where asked, the stamp duty type and the date.
- Compare the details returned by the system with the certificate in your hands: parties, instrument description, value, amount, date.
- Scan the QR code where provided and compare again.
- Record the verification (screenshot or reference) with the agreement.
A certificate whose number is not found, or whose details differ from the system's record, is not to be relied on.
What to compare against the agreement
| Certificate field | Must match |
|---|---|
| First and second party | The parties to the agreement (names as in the agreement) |
| Instrument description / article | The type of agreement (lease, agreement, indemnity bond) |
| Consideration / value | The value on which duty was computed (rent and deposit, contract value) |
| Stamp duty amount | The rate for that article in that state |
| Date of issue | On or before the date of execution (section 17: stamped before or at execution) |
| State | The state of execution or of the property |
A certificate issued after the execution date is a red flag: the agreement was signed first and stamped later.
Signs of reuse or alteration
- The same certificate number appearing on more than one agreement.
- Certificate details that match the system but a party name that does not match the agreement.
- A certificate image with inconsistent fonts or alignment, or a QR code that resolves to different details.
- A certificate for a lower value than the agreement's consideration.
Making verification a workflow step
- Generate the certificate within the workflow from the intake data (parties, article, value), so mismatch cannot arise.
- Attach the certificate as the first page of the execution version automatically.
- For agreements where the counterparty supplies the certificate, require verification before signature and store the verification record.
- Report monthly on executed agreements without a verified certificate.
If you find a problem
An agreement with a defective or missing stamp is not void; it is inadmissible until regularised. Pay the duty and penalty through the state's adjudication process before you need to rely on the document, not after.
Where Legatio fits. Legatio generates e-stamp certificates from intake data where the state system allows, attaches them per instrument, stores the verification record, and reports on agreements lacking a verified certificate. Verification itself is done against the issuing system.
Position stated as of October 2026. General information; verification procedures differ by state and system.