Understand e-sign form-token expiry and rate limits | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-e-sign-form-token-expiry-and-rate-limits Publisher: Pixie Technologies LLC QR verification and receiver e-sign (https://pixiecrm.com/help-centre/topic/bilty-public-verification-esign) · How-to guide Understand e-sign form-token expiry and rate limits Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Use the configurable short-lived form token, failed-attempt limit and rate window as part of the protected public signing flow. The guide follows the Help Centre standard: exact route, prerequisites, ordered steps, verification and operational boundaries. Audience: Administrators and authorised Bilty operations staff; Permission: Relevant Bilty Management capability; Module v1.0.0; Where to goBilty Management → Settings → QR verification & e-sign 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 this guide helps you do Use the configurable short-lived form token, failed-attempt limit and rate window as part of the protected public signing flow. 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 Bilty Management → Settings → QR verification & e-sign and open the relevant current record or configuration view. - Review the displayed state and compare it with the explanation in this guide. - Compare the live values with the workflow described in this guide: Use the configurable short-lived form token, failed-attempt limit and rate window as part of the protected public signing flow. - Follow any linked record, status, public evidence, invoice, queue or audit entry rather than inferring that a downstream action happened. - Use the related guides below for the operational action that changes the record. Settings to check 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. Check it worked Return to Bilty Management → Settings → QR verification & e-sign 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. 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-sign (https://pixiecrm.com/help-centre/topic/bilty-public-verification-esign)bilty management (https://pixiecrm.com/help-centre/category/bilty-management) Related guides Verify an issued Bilty from the QR code (https://pixiecrm.com/help-centre/verify-an-issued-bilty-from-the-qr-code)Configure fields shown on public Bilty verification (https://pixiecrm.com/help-centre/configure-fields-shown-on-public-bilty-verification)Understand data never shown on public Bilty verification (https://pixiecrm.com/help-centre/understand-data-never-shown-on-public-bilty-verification)