Talk to us →
Home / Verify a document
Document registry · live

Verify a document issued by LENS.

Every document LENS issues - quotations, bills of material, invoices, partner certificates, attestations, site handovers - is hashed and entered into a signed registry at the moment of issue. Scan the QR block, upload the file, or type the reference. The registry answers in one call: authentic, superseded, expired, or unknown.

Documents in registry
1,42,860
Median answer
0.6s
Issuing entities
3
Registry since
2019
Step 1 · present the document
No account needed
Camera off

The camera stream stays on your device - only the decoded reference is sent to the registry.

Look for this block
Specimen. The real block is generated per document and printed on the last page.

No camera? Use or the form.

Step 2 · registry answer
Nothing checked yet

A verified answer returns the full registry record. Nothing is inferred from the file itself.

Document
Reference
Issued by
Valid until
Signed by
Signature
SHA-256
Status
Registry reachable·TLS 1.3·ap-south-1 · Mumbai
How verification works

Four steps, none of them ours to fake.

The registry is append-only. A record cannot be edited after issue: only superseded by a newer one, which is why an old quotation reads as superseded rather than disappearing.

01 · At issue

Hashed and signed

The final file is hashed with SHA-256 and signed with the issuing entity's document key. Hash, signature, signatory and validity window go into the registry.

02 · On the page

Reference block printed

A QR block, the reference number and a six-character code are printed on the document itself, so a paper copy verifies as well as a PDF.

03 · You check

Scan, upload or type

An upload is compared byte-for-byte against the registry hash. A scan or reference returns the record so you can read it against the copy in your hand.

04 · Afterwards

Logged both ways

Each check is written to the audit trail. If the document is later revised, whoever verified it gets told: the registry knows who asked.

LENS Inc
US, Canada, UK, EU · Delaware registered · document keys held in us-east-1
LENSCORP AI PVT LTD
India, South Asia, ASEAN · Gurugram · keys and registry resident in ap-south-1
LENS AI LLC
GCC, Middle East, Africa · Dubai · keys held in me-central-1
The registry runs under independently audited controls
ISO 27001
Information security management
SOC 2 Type II
Audit trail integrity, tested annually
DPDPA
India · uploads resident in-country
GDPR
EU / UK · lawful basis on record
NIST
Signing keys in FIPS 140-2 HSMs
On the phone in your hand

Most scans happen standing at a desk, printout in hand.

So the mobile view leads with the camera, keeps the verdict above the fold, and puts the record behind one tap. The reference form is the fallback when a printout is creased or a photocopy has washed the QR out.

01Camera opens on load - no tap to start
02Verdict as a single colour-coded band, readable at arm's length
03Record collapses to five fields; the rest is one tap away
Questions people actually ask

Before you upload anything.

What happens to a file I upload?
It is hashed in your browser, sent to LENS over TLS 1.3, and retained as part of the verification audit trail: the record ID, the hash, the timestamp, and the file itself. Retention runs to seven years for commercial documents so that a dispute years later can be settled against what was actually checked. Data residency follows the issuing entity: an Indian document stays in ap-south-1.
The document says superseded. Is it a fake?
No. It means LENS issued it and has since issued a newer revision. Quotations get re-priced, BoMs get re-scoped, certificates get renewed. The result card names the replacement reference so you can ask for it directly. Treat superseded as "do not sign this one," not as "someone forged this."
Why does a hash mismatch matter if the text looks right?
Because a single changed digit - a bank account, a unit price, a delivery date - produces a completely different hash. A mismatch means the file in your possession is not the file LENS signed. It may be innocent: someone re-saved, flattened or re-compressed the PDF. It may not be. Either way, work from the original the registry returns, not the copy you were sent.
I only have a printout, and the QR is smudged.
Use the reference number and the six-character code printed beside it. Both are human-readable for exactly this reason. A photo of the page also works: the uploader reads the reference block by OCR, though it cannot confirm a hash from a photograph, so you get the record without a byte-level match.
Does anyone at LENS see that I checked?
Yes. Every check is written to the audit log against the document record, and the account team can see that the document was verified: that is the point of an audit trail. No email is required to check. It is required only to receive the authentic original, because sending a file to an address is a disclosure and gets logged as one.
Something came from "LENS" and the registry has never heard of it.
Stop and tell us. Forward the document and the sending address to trust@lenscorp.ai. Invoice fraud against enterprise buyers usually arrives as a plausible payment-details change on a real quotation. Do not pay, do not update bank details, and do not reply to the sender until you hear back. LENS never changes banking details by email.

Still not sure it came from us?

The trust desk answers within one business day, in your region's hours. Send the document, the address it arrived from, and the reference if it has one.

trust@lenscorp.ai → +91 99907 36796