QR verification on UP certificates: how a verifier checks yours

The code printed on your certificate is what turns it from a piece of paper into something checkable. What a verifier sees when they scan it, and what breaks it.

In short

The code resolves to the department's own record of your certificate, so a verifier is comparing your copy against the issuer's rather than reading your paper. Present the signed PDF wherever you can.

What the code carries

It resolves to the issuing system's record of your certificate: the application number, the certificate number, the holder's particulars and the issuing office. The verifier is not reading your document; they are reading the department's copy of it and comparing. That is why a genuine certificate cannot be improved by editing the print.

What a verifier does

1. 1Scans the code, or enters the certificate number on the verification page: Both routes reach the same record.
2. 2Compares the particulars on screen with the document in hand: Name, father's name, date of issue and the issuing Tehsil.
3. 3Checks the date against their own requirement: This is where a certificate older than the institution's recency rule is refused, even though the record is valid.

What breaks verification. A photocopy of a photocopy where the code no longer scans; a cropped scan that cuts the code off; a photograph at an angle. The record is fine. The document has become unreadable, and the burden is on you.

Present the PDF where you can

A digitally signed PDF carries both the signature and a scannable code, and it cannot degrade. Where a desk will take a file, give them the file. Where they need paper, print the PDF fresh rather than copying an old print.