Verify an issued Bilty from the QR code
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Open the HMAC-protected public verification URL encoded in the issued Bilty QR and compare the permitted shipment fields. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries.
What this guide helps you do
Open the HMAC-protected public verification URL encoded in the issued Bilty QR and compare the permitted shipment fields. Bilty Management keeps drafts, issued records, public capability links, finance, integration events and audit evidence as connected but separately verifiable records.
How it works
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
- Go to Issued Bilty PDF → QR verification.
- Confirm the active tenant, intended Bilty record and your permission before entering or changing data.
- Complete the supported workflow: Open the HMAC-protected public verification URL encoded in the issued Bilty QR and compare the permitted shipment fields.
- Review the displayed validation, dependent fields and any privacy, finance or integration warning before continuing.
- Save, submit or run the action once and wait for the module response.
- Reopen the relevant register or record and verify the final status, linked records and audit evidence.
Settings to check
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.
Check it worked
Return to Issued Bilty PDF → QR verification 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.
Common mistakes to avoid
- 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.