From published waiver to portable proof package.
Verifyistic keeps the human signing experience simple and the evidence chain explicit. Each stage has a clear input, output, and operational purpose.
1. Publish the exact text
Start with an attorney-approved waiver or acknowledgment. Define fields, required consent, and the version that customers will see.
- Draft and validate fields
- Publish an immutable version
- Keep prior versions available
2. Present the right signing path
Send, embed, QR, or kiosk the same template through the channel that fits your business.
- Secure signer URL
- Pre-arrival and front-counter flows
- No private API key in browser code
3. Capture consent and identity context
The session records signer input, consent, timestamp, IP, device context, and signature method according to the workflow.
- Server-side validation
- Guardian and conditional branches
- Audit event chain
4. Seal and route the proof
The worker finalizes the signed document, certificate, hashes, and verification data, then emits lifecycle events for downstream automation.
- Private document storage
- Authorized downloads
- Signed retry-safe webhooks
Clear answers before you build.
Is the signing URL public?+
The signer transport uses a high-entropy expiring token. Treat the URL as private and do not publish it in logs or analytics.
What if a webhook endpoint is offline?+
The delivery engine retries with bounded backoff and records a dead-letter state after the configured attempts.