Document Types Overview
Document Types Overview
Every ZipZign document has a type that determines what happens after creation.
The three types
readable
Generate a PDF from HTML. No emails sent, no signing, no payment. Use this for:
- Receipts and invoices
- Reports
- Any document you need as a PDF
{
"type": "readable",
"title": "Invoice #1042",
"content": "<h1>Invoice</h1><p>Amount due: ${{amount}}</p>",
"variables": { "amount": "500.00" }
}
signable
Send a document to one or more signers. ZipZign emails each signer a link to a hosted signing page. Use this for:
- Contracts and NDAs
- Agreements and consent forms
- Any multi-party document requiring signatures
{
"type": "signable",
"title": "Service Agreement",
"content": "<h1>Agreement</h1><p>...</p>",
"signers": [
{ "name": "Alice", "email": "alice@example.com" },
{ "name": "Bob", "email": "bob@example.com" }
]
}
Max 6 signers per document.
payable
Collect payment without signing. ZipZign emails the payer a Stripe checkout link. Use this for:
- Deposits
- Service fees
- One-time charges tied to a document
{
"type": "payable",
"title": "Project Deposit",
"content": "<h1>Deposit Invoice</h1><p>50% deposit for website project.</p>",
"payment": {
"amount": 50000,
"currency": "usd",
"description": "Website project deposit",
"payerName": "Client Corp",
"payerEmail": "billing@clientcorp.com"
}
}
Amount is in the smallest currency unit (cents for USD). 50000 = $500.00.
Sign-then-pay
A signable document can include a payment object. After all signers sign, the payer is prompted to pay. The payer does not see signature UI; signers do not receive payment receipts.
See Sign-then-Pay for the full flow.
Status lifecycle
Each type follows a different status path:
Type | Status progression |
|---|---|
| |
| |
| |
| |
See Document Status & Lifecycle for the full reference.
Updated on: 16/04/2026
Thank you!