Did you know? A university certificate can be printed beautifully, complete with a seal and a QR code, yet none of those visual details alone prove that it is genuine. A QR code is easy to create. The important question is what happens after a verifier reads it.
Quick answer: a certificate QR code may lead to an official verification service or contain document-verification data. A trustworthy service checks evidence such as document integrity, issuer identity and current validity. In Singapore, systems including OpenCerts and government document-verification services support verification of certain digital records. Scanning a square is not proof: the verification result and its source matter.
The 30-second explanation
- Issuer creates the record: an authorised school or organisation issues a digital credential.
- Record is protected: a supported verification method binds important document data to evidence that later changes can be detected.
- Holder shares it: the recipient presents the supported file, verification link or QR-enabled document.
- Verifier checks: an official service evaluates whether the credential is intact and associated with an accepted issuer.
- Verifier reviews: the person checks the actual name, qualification, date and status before relying on the result.
A QR code is only a doorway
Imagine a student receives an award certificate with a QR code. An employer scans it and sees a page saying “Verified”. Is that enough? Only if the page is a trusted verification service, and only if the result refers to the actual credential and issuer involved.
Anyone can print a QR code that opens a page with a reassuring green tick. Anyone can copy a crest onto a convincing-looking document. A genuine verification system needs checks that go beyond the appearance of the page.
The QR symbol itself is a readable pattern carrying data, often a web address. Its purpose is to make a verification action easy to start. It cannot independently certify the record it is attached to.
What is OpenCerts in Singapore?
OpenCerts is an approach used for verifiable educational credentials. Its official portal at opencerts.io allows people to open an appropriate .opencert file and check the credential. The Institute of Banking and Finance describes OpenCerts as a standard used for educational qualifications such as certificates, transcripts and degrees.
The verifier checks the integrity of an issued document and the identity of the issuer through supported technical evidence. The official portal describes comparing information from the credential with evidence recorded when the certificate was created. In relevant implementations, this includes blockchain-backed records and proof of the issuing institution.
An important distinction: you do not need a QR code for every OpenCerts verification. The official workflow can use the .opencert file itself. A QR code printed on another document may instead lead to an issuer or verifier site. Those are related but not interchangeable approaches.
Step 1: Confirm that the issuer is real
Suppose a document claims to be from a recognised college. A verifier needs more than the college’s logo. It must be able to establish that the issuing identity behind the cryptographic record is connected to the legitimate institution.
OpenCerts documentation explains approaches to issuer identity involving trusted domain records and associated proof. A claim made by an unknown publisher is not the same as evidence associated with an institution’s controlled domain.
For readers, the practical question is simple: Does the verification process recognise the actual issuing organisation, and is this the official service the issuer tells me to use?
Step 2: Check that the document has not been changed
Now imagine a genuine diploma is altered so that a grade is changed. A well-designed verifiable credential binds the issued content to a mathematical fingerprint, often called a cryptographic hash, or to other tamper-evident information.
Changing an important field should make the issued proof and the altered document disagree. When the relevant verification checks fail, the result should not be treated as a valid unchanged credential.
This is not the same as a scanner comparing two photographs. The comparison concerns the protected digital record. A screenshot or ordinary printout that merely looks identical does not automatically give you access to the underlying proof.
Step 3: Check the credential’s current status
Authentic issuance is not always the end of the story. An institution may revoke a credential that was issued in error, or an organisation may publish updated verification information. OpenCerts’ technical FAQ describes checking document status as part of a supported verifier.
A credential that was genuine when first issued might no longer have the status a recipient expects. Therefore, a useful verifier checks the status available under the applicable credential framework, not simply the document’s visual appearance.
For highly consequential decisions, reviewers should follow the issuing body’s verification instructions and consider whether more checks are required. A technical result answers specific questions about the record; it does not prove every claim someone makes about a person’s broader experience.
What about QR codes on government documents?
Singapore’s FileSG provides another instructive example. Its official FAQ explains how selected government-issued documents using the OpenAttestation format can be verified by scanning a QR code on the document in the designated verification workflow, or by uploading the appropriate OA file.
The guidance specifies that only QR codes on documents issued through that supported service can be verified in that manner. A random QR code with “For Verification” printed next to it is not automatically a FileSG credential.
Singapore’s Immigration & Checkpoints Authority similarly advises readers checking the QR code or URL of a digital certificate to inspect the browser address and use its official digital certificate verification route. The common lesson is to arrive at the genuine verifier, not a look-alike site.
Why a green tick can still mislead
- Wrong website: a copied page can display a fake “verified” banner.
- Wrong document: a genuine result may refer to a different person’s certificate.
- Incomplete review: an intact document does not by itself establish that its subject met an employer’s separate eligibility requirements.
- Outdated screenshot: a picture of a past verification page may not reflect current status.
- Copied QR code: an authentic code placed on another document does not necessarily authenticate the altered document.
A careful employer or school should inspect the credential details presented by the actual official service, compare them with the document and verify that the result corresponds to the person and qualification under review.
A step-by-step safe verification routine
- Use the official channel: begin at the issuer’s established website or a documented national verification service.
- Use the expected format: upload a supported .opencert or OA file when the verifier calls for one, or scan through the official verification workflow.
- Read the result: check integrity, issuer and any status information the verifier actually provides.
- Compare details: look at names, qualification title, issue date and other relevant fields rather than only the colour of the banner.
- Handle privacy properly: avoid uploading credentials with personal data to unknown third-party “QR checkers”.
Why the difference matters for students
Students often collect many types of learning evidence: participation badges, workshop certificates, examination results, academic transcripts and degrees. These do not all have the same issuer, evidential value or verification method.
A programme organiser can make a simple public web page with a QR code. A school can issue a recognised digital certificate. Another system can create a cryptographically verifiable record. The visible square may appear similar in all three cases, but the evidence behind each is not the same.
Learning to ask Who issued this? What exactly is being verified? What proof is available? helps students become discerning readers of digital documents.
A five-minute classroom thought experiment
Sketch two imaginary award certificates that look identical. One QR code goes to a school-controlled verification page; the other points to a website that an unknown person set up yesterday. Ask your classmates which evidence they would need before trusting either certificate.
Next imagine that both links display a green tick. What additional check matters? The official issuer, the verification method and the relationship between the checked record and the document being presented. This turns QR codes into a lesson about source evaluation and trustworthy information.
Questions readers often ask
Does scanning a certificate QR code prove it is real?
No. The square only carries information. You need a trustworthy verification process that checks the appropriate record and issuing identity.
Do all certificates with QR codes use blockchain?
No. A code can link to an ordinary website, a central database, a cryptographic verification service or another system. The symbol does not reveal the trust architecture on its own.
Can I verify an OpenCerts qualification without scanning a QR code?
Yes, when you have a supported .opencert file, the official OpenCerts portal can perform verification using that file.
Does a valid digital certificate prove a person attended every lesson?
Not necessarily. Verification can confirm issuance and integrity under the credential’s rules. Specific attendance or competence claims must be evaluated from the actual record and issuing process.
The idea to remember
QR codes make evidence easier to reach; they do not create evidence by themselves. Trust comes from a legitimate issuer, an intact record, a sound verification method and a person who reads the result carefully.
Continue with How Product Packaging Connects to Digital Information, Scan Safely and Spot QR Code Scams and Learning Foundations and Evidence of Progress.
Sources and further reading
- OpenCerts: Official Credential Verification Portal — opening and verifying supported files.
- OpenCerts: Frequently Asked Questions — integrity, issuer identity and credential status.
- Institute of Banking and Finance Singapore: OpenCerts FAQ — educational credentials and supported verification.
- FileSG: Verify Documents and QR Codes — supported OpenAttestation file and QR methods.
- ICA: How to Check a Digital Certificate QR Code — use the genuine official verification URL.
Explore the How QR Codes Work series
Explore the science behind a QR code, then follow the same technology into different parts of daily life.
The foundations
- How a Square Stores Words, Links and Numbers
- Why a Damaged Code Can Still Scan
- Static vs Dynamic QR Codes Explained
- Scan Safely and Spot QR Code Scams
- Why Cameras Can Read Tilted and Rotated Codes
- Why QR Codes Have Different Sizes and Versions
QR codes in everyday life
- How Scan-to-Pay Connects to Banks and Wallets
- How Event Tickets and Check-In Prevent Reuse
- Share Wi-Fi Without Typing a Password
- How Product Packaging Connects to Digital Information
- Share Contacts and Calendar Events Without Typing
- How Authenticator Apps Set Up Two-Step Verification
- From Restaurant Menus to Kitchen Orders
- How Parcel Lockers Verify Collection and Returns
- How a Phone Signs In to a Computer
- Museums, Exhibits and Public Information
- Boarding Passes and Airport Gate Scanning
- Warehouse Inventory and Stock Tracking
- CDC Vouchers and One-Time Redemption
- Classroom Attendance and Singpass E-Attendance
- Library Books, Borrowing and Digital Catalogues
- Digital Receipts and Warranty Registration
- School Worksheets, Homework and Learning Videos
- Hospital Visitor Passes and Clinic Check-In
- Cross-Border Payments and Currency Conversion
- Food Traceability, Batch Numbers and Recalls
- Train Tickets, Fare Gates and Contactless Cards
- Charity Donations and Safer Giving in Singapore
- EV Charging Stations and Payment Sessions
- Equipment Maintenance and Inspection Records
- Printing, Colours, Logos and Design Mistakes