Sign · Seal · Prove
Contracts that can prove themselves.
--:-- --
Timestamped
to the second
RFC 3161 · PAdES · SHA-256
We're Accordify
How it is legally binding- Master services agreements/
- Offer letters/
- NDAs/
- Leases/
- Vendor onboarding/
- Consent forms/
- Purchase orders/
- Contractor agreements/
- Disclosures/
- Enrolment forms/
- 0
- accounts needed to sign
- SHA-256
- hash of every document
- RFC 3161
- trusted timestamp on every seal
- PAdES
- seal any PDF reader can check
The platform
Most e-signature tools stop at the signature. Accordify keeps going, until the document can defend itself years from now.
Product
One envelope, four moments
Prepare once, send to everyone, collect signatures in any order, and walk away with a sealed file and a ledger behind it.
Prepare
Drop in a PDF. Place signature, date, initials and text fields per recipient.
Send
Recipients get a secure link. Sequential or parallel routing.
Sign
Draw, type or upload. Consent is captured before the first field.
Seal
Flattened, sealed and timestamped the moment the last signer finishes.
The proof ledger
Every action hashes the one before it.
Created, sent, opened, signed, sealed: each event stores the hash of the previous one. Change or remove a single entry and the whole chain breaks, visibly. It is the audit trail you can check, not just read.
Try the verifierInteractive · try to tamper
- Envelope created7f3a…c91e
- Sent to 2 recipientsb208…44d0
- Opened by signer 119ce…a7f3
- Signed by signer 1e5d1…0b62
- Signed by signer 23c9a…f18d
- Sealed · timestampeda41b…92ee
✔ Hash chain intact. Try tampering with any entry.
Solutions
Built for work that needs a signature
The same sealed, provable envelope, tuned for the paperwork each team actually moves.
Sales & procurement
Order forms, MSAs and vendor agreements out the door in hours, not weeks.
- Order forms
- MSAs
- Vendor onboarding
HR & onboarding
Offer letters, policies and contractor agreements signed from a phone.
- Offer letters
- NDAs
- Policies
Legal & compliance
Evidence that survives a challenge: who signed, when, and that nothing changed.
- Audit trail
- Retention
- Verification
Real estate
Leases, disclosures and offers with several parties signing in order.
- Leases
- Disclosures
- Routing
Healthcare & education
Consent and enrolment forms with accessible, keyboard-friendly signing.
- Consent
- Enrolment
- WCAG 2.1
Operations & logistics
Delivery notes and service agreements signed on site, on any device.
- Field signing
- Templates
- Any device
Why Accordify
What can you prove later?
Signing is the easy half. The hard half is showing, years on, that the file is the one that was signed.
| Capability | Paper & PDF | Typical e-sign | Accordify |
|---|---|---|---|
| Detect changes after signing | Sometimes | ||
| Signer needs an account | n/a | Often | |
| Trusted timestamp on the file | Rarely | ||
| Anyone can verify, offline of the vendor | Vendor portal | ||
| Hash-chained audit trail | Log export |
Security & compliance
Legal weight, cryptographic backbone
Signatures that satisfy the law and a seal that satisfies a skeptic.
ESIGN & UETA
US federal and state e-signature law, with explicit consent captured before signing.
eIDAS
Electronic signatures recognised across the EU and UK.
PAdES seal
A standards-based PDF signature that any compliant reader can validate.
RFC 3161 timestamp
An independent, trusted time proving when the document was sealed.
KYC & KYB
Verified senders and organisations, so recipients know who is asking.
Role-based access
Org roles, per-envelope permissions and cross-organisation signing.
Accessible by design
WCAG 2.1 AA, full keyboard use and screen-reader support when signing.
Your data, your retention
Data processing terms and retention controls for your organisation.
Built for developers
A REST API, signed webhooks with retries, and an embeddable signing experience for web and React Native. Everything the dashboard does, your product can do.
- REST API & typed SDK
- Signed webhooks with retries
- Embedded signing for web and React Native
Create an envelope
curl -X POST $ACCORDIFY_API/v1/envelopes \
-H "Authorization: Bearer $ACCORDIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "title": "Master Services Agreement" }'
# → { "id": "env_…", "status": "draft" }
# webhook envelope.completed → your serverQuestions
Good questions, straight answers
Are Accordify signatures legally binding?
Yes, in the United States under the ESIGN Act and UETA, and in the EU and UK as electronic signatures under eIDAS. Some document types (wills, certain court filings) are excluded by law everywhere; see our ESIGN & eIDAS page.
Does my signer need an account?
No. Signers open a secure link, review the document, consent to sign electronically and sign by drawing, typing or uploading a signature. Nothing to install.
How do I prove a document was not changed?
Upload the PDF to our verify page. We check the PAdES signature, that it covers the whole file, the RFC 3161 timestamp and that the hash matches our records. Any change, even one character, fails.
Who can send documents?
Individuals complete identity verification (KYC) and businesses complete business verification (KYB) before sending. Signers are not required to do either.
Can I integrate Accordify into my product?
Yes. Create envelopes with the REST API, receive signed webhooks with automatic retries, and embed the signing experience in your web or React Native app.