Understand server-side QR signature validation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-server-side-qr-signature-validation Publisher: Pixie Technologies LLC Public scanning and signing Understand server-side QR signature validation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Meet the PNG, byte-size, image-dimension and non-blank checks performed after submission. Audience: Recipients and support staff; Permission: Staff login; Module v2.1.1; Where to goPublic QR page → Submit signature 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 this guide helps you do Meet the PNG, byte-size, image-dimension and non-blank checks performed after submission. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Draw the signature in the supplied canvas. - Submit through the form rather than uploading an arbitrary file. - If rejected, clear and draw a fuller signature. Fields and options Action scopeMeet the PNG, byte-size, image-dimension and non-blank checks performed after submission. Module version2.1.0 NavigationPublic QR page → Submit signature EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - The value must be a data:image/png;base64 URL. - Decoded PNG length must be between 150 and 750,000 bytes. - The image must be a valid PNG with acceptable dimensions. - Pixel analysis rejects a dot or effectively blank image. Check 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. Related guides QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Draw and clear a QR handwritten signature (https://pixiecrm.com/help-centre/draw-and-clear-a-qr-handwritten-signature)Accept the QR electronic-signature declaration (https://pixiecrm.com/help-centre/accept-the-qr-electronic-signature-declaration)Allow or refuse QR device geolocation (https://pixiecrm.com/help-centre/allow-or-refuse-qr-device-geolocation)Export invoices and sales PDFs (https://pixiecrm.com/help-centre/export-invoices-and-sales-pdfs)Create a credit note (https://pixiecrm.com/help-centre/create-a-credit-note)