Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
QR verification and receiver e-sign · How-to guide

Understand Bilty signature PNG validation

Understand the server-side checks for PNG structure, CRCs, dimensions, decompression bounds, visible ink, trailing data and file size. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.

Audience: Administrators and authorised Bilty operations staffPermission: Relevant Bilty Management capabilityModule v1.0.0
Jump to steps
Where to goSecure receiver e-sign receipt
Before you startRequired access: Relevant Bilty Management capability. Work on the correct tenant and record. Use least privilege and review any dependency or protected workflow warning before continuing.

What you’ll accomplish

Understand the server-side checks for PNG structure, CRCs, dimensions, decompression bounds, visible ink, trailing data and file size. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.

How the workflow fits together

Verify issued Bilties publicly, configure permitted fields and collect protected receiver POD signatures. Use the module's current status, permission checks, warnings and linked records to decide the next supported action. Where a downstream invoice, WhatsApp queue item, webhook, PDF, POD record or audit event applies, verify it separately.

Follow these steps

  1. Go to Secure receiver e-sign receipt and open the relevant current record or configuration view.
  2. Review the displayed state and compare it with the explanation in this guide.
  3. Compare the live values with the workflow described in this guide: Understand the server-side checks for PNG structure, CRCs, dimensions, decompression bounds, visible ink, trailing data and file size.
  4. Follow any linked record, status, public evidence, invoice, queue or audit entry rather than inferring that a downstream action happened.
  5. Use the related guides below for the operational action that changes the record.

Fields and decisions to review

Verification linkIssued public links are HMAC-protected capability URLs.
Public fieldsOnly explicitly configured non-financial shipment fields are shown.
E-sign tokenSignature submission uses a short-lived link-bound form token.
EvidenceCompleted signatures retain hashes and POD evidence; raw canvas payloads are not audit content.

Record, audit and evidence checks

Reopen the relevant Bilty record or register and confirm its identifier, current status, related parties, timestamps and connected evidence. Check the audit/compliance, payment, public-link, report, API, webhook or WhatsApp evidence that applies to this workflow rather than relying only on a success alert.

How to confirm it worked

Return to Secure receiver e-sign receipt or the resulting register and verify that the stored state matches the intended action. For any downstream automation, confirm the downstream record or queue/log entry as a separate completion check.

Technical basis for this guidance

This guide was checked against config/routes.php; controllers/Bilty_public.php; models/Bilty_management_model.php; views/public/verify.php; views/public/sign.php; assets/js/public_esign.js. It documents only behaviour exposed or enforced by the supplied module; internal secrets, raw signature payloads and unsupported future workflow assumptions are intentionally excluded.

Controls, checks and common mistakes

  • Public verification never exposes price/payment data or private contact numbers.
  • Receiver e-sign depends on public verification and fails closed when the dependency is disabled.
  • Do not treat possession of a public capability URL as staff authentication.
Data and workflow safetyConfirm the exact Bilty, authorised audience and final stored status before issuing, publishing a link, recording payment, changing shipment state or sharing a document.
Browse connected topics:qr verification and receiver e-signbilty management
Verify an issued Bilty from the QR codeConfigure fields shown on public Bilty verificationUnderstand data never shown on public Bilty verification