What you can do on this page today
This page explains the intended verification service and its limits. It does not currently offer a reference-entry form, a file upload or a live authenticity result. If you have received an unfamiliar letter, check the issuing organisation through a contact route you independently trust rather than treating a printed reference or logo as a complete check.
For a general Epistles question, use the secure contact form and describe the concern without sending private document contents. Do not provide a verification code from another service, a password or payment credentials. The client verification page identifies the recorded fingerprint and allows an exact-file comparison. It keeps the letter body and recipient details private. Public guidance and a working verification transaction are different stages of the service.
What a QR verification code can prove
A QR code on an Epistles-issued document should connect to an official verification page through a high-entropy token. A recipient can check whether Epistles recognises that issued record and, where supported, compare a digital file with the fingerprint retained at finalisation. This can make an unfamiliar letter easier to assess than an unsigned photocopy with no identifying information.
A QR code alone does not prove who physically posted a letter, who read it or whether every word on a printed copy is identical to a stored PDF. The verification response must explain its scope in plain language. It should not disclose addresses, private attachments, case details or a customer's identity simply because a visitor scanned a code.