Understand QR verification code and evidence hash
Interpret the HMAC-backed evidence and grouped verification code. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → QR Compliance Records → Open signed record
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What you’ll accomplish
Interpret the HMAC-backed evidence and grouped verification code. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to Cryptographic evidence.
- Check evidence hash and verification code.
- Compare them with the public page/PDF stamp where displayed.
Fields and options to review
Action scopeInterpret the HMAC-backed evidence and grouped verification code.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open signed record
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The evidence hash is an HMAC over the signed evidence payload using the module compliance secret.
- The verification code groups the first 20 hexadecimal characters into five four-character groups.
How to confirm it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.