E-signature and public verification

Draw, clear and submit a letter signature

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to use the signature pad and send the base64 PNG to the acceptance endpoint.

Audience: Letter recipientsPermission: Possession of the public signature linkModule v1.0.0

Jump to steps

Where to goPublic signature page → signature pad → Accept & Sign Document

Before you start

Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.

What this guide helps you do

Use the signature pad and send the base64 PNG to the acceptance endpoint. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Draw the signature on the canvas.
Use Clear Signature if a redraw is needed.
Select Accept & Sign Document.
If the canvas is empty, draw a signature and submit again.
Wait for the signed confirmation state.

Fields and options

Action scopeUse the signature pad and send the base64 PNG to the acceptance endpoint.

Module version1.0.0

Exact routePublic signature page → signature pad → Accept & Sign Document

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules and limits

Signature Pad 4.0.0 is loaded from jsDelivr.
Client-side JavaScript converts the canvas to a PNG data URL.
The controller strips the data URL prefix, base64-decodes the data and writes a PNG file.

Check it worked

The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
Any warning, missing file or failed send is investigated rather than bypassed.

Security, privacy and operational checks

Apply least privilege and verify recipient identity before sending or exposing public links.
Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
Test configuration and deployment changes with controlled records before production-wide use.
Interpret email opens and e-signatures according to their documented technical limitations.

Was this guide useful?Your response is stored only in this browser.