E-signature infrastructure for regulated work. Every signer passes an email one-time passcode, and every envelope is sealed with a hash-chained audit trail strong enough for legal, accountancy and property.
Every completed envelope is sealed as a PDF carrying a PAdES digital signature and an RFC-3161 timestamp. Alter one byte and the seal breaks.
A timeline you can read, share by URL and export as a signed PDF. The proof is a surface, not a buried download.
Create, send and track envelopes over a small JSON API; signers finish on a hosted, mobile-first page and a signed webhook tells your app it's done.
Create an envelope, add signers, capture the signature, receive a webhook. The whole SES surface is a small, predictable REST API.
curl "$PACTIVO_API/envelopes" \
-H "Authorization: Bearer pk_live_…" \
-H "Content-Type: application/json" \
-d '{
"title": "Client engagement letter",
"recipients": [{ "name": "Eleanor Hartley",
"email": "eleanor@hartley.co.uk" }],
"documents": [{ "file_name": "letter.pdf",
"content_base64": "JVBERi0…" }],
"verification": { "required": true, "type": "email_otp" }
}'A small, portable proof — anyone you hand it to can check it themselves, with no account.
A typed name is easy to dispute. Pactivo puts a one-time passcode on the signer, writes every step into a SHA-256 hash chain, and seals the finished document with a PAdES digital signature and an RFC-3161 timestamp — so the record is checkable, not assertable.
Read how the proof holds upYou pay for envelopes you send. That is the whole pricing page.