E-signature and public verification

Open a public Letter Manager verification page

Validate the unique-code URL from the PDF QR code or Verify action.

Audience: Recipients, staff and verifiersPermission: Possession of the public verify linkModule v1.0.0

Exact navigationGenerated PDF QR code; or Admin/Client Letter History → Verify

Before you begin

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide covers

Validate the unique-code URL from the PDF QR code or Verify action. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open or scan the verification link.
Confirm the green verified presentation loads.
Compare sender, receiver, reference, verification code, subject and issue date as displayed.
Review email, postal and signature details only when configured to be public.
Treat a 404 as an invalid or missing unique code.

Fields, choices and supported possibilities

Action scopeValidate the unique-code URL from the PDF QR code or Verify action.

Module version1.0.0

Exact routeGenerated PDF QR code; or Admin/Client Letter History → Verify

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Code-backed validations and workflow rules

Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
Browser controls are not a substitute for server-side and operational verification.

Expected result and verification

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.