Carriers need a valid signature, not a particular brand.
When underwriting asks for DocuSign or Adobe Sign, they usually mean: a legally valid e-signature, proof of who signed, and a record nobody could change. SealProof gives you all of that, plus evidence anyone can check. Here's what to show your carrier.
Six questions, and how SealProof answers them.
It's a legally valid signature
SealProof is designed around the U.S. ESIGN Act and UETA. Each signer agrees to sign electronically, in the exact words they saw, and consumers get the electronic record disclosure. Both are recorded.
It was really the client
A unique link to their email, plus optional checks: a one-time code by email or text, an access code you give them, or a photo ID and selfie check. The certificate records which were used.
There's a complete audit trail
Every view, code and signature, with time, IP address and device, in a Certificate of Completion at the end of the signed PDF, the way underwriters are used to seeing it.
Nothing changed after signing
The finished PDF is sealed and timestamped by an independent authority. Change one character and verification fails, so an altered application can't pass as the signed one.
It's a normal PDF
Underwriting gets an ordinary PDF that opens, prints and files like any other. When a packet combines several forms, each can also be sent as its own sealed file.
Anyone can check it, years later
Your carrier can verify any document at sealproof.io/verify, free and without an account. The check doesn't depend on SealProof still being around.
The same essentials, plus proof others don't keep.
What carriers expect from the big e-signature names, next to SealProof. Including the two places we're not there yet.
| What carriers look for | Expected from DocuSign or Adobe Acrobat Sign | SealProof |
|---|---|---|
| Consent to sign electronically (ESIGN / UETA) | Yes | ✓ Recorded word for word, in the signer's language |
| Certificate of completion with the audit trail | Yes | ✓ Inside the signed PDF: who, when, IP, device and identity checks |
| Tamper-evident signed PDF | Yes | ✓ Sealed with a key held in AWS KMS hardware |
| Signer authentication options (codes, ID checks) | Yes | ✓ Email or text codes, access codes, photo ID and selfie, in person |
| Independent trusted timestamp on every document | Varies by product | ✓ RFC 3161, from an independent timestamp authority |
| Free verification without an account | Varies by product | ✓ sealproof.io/verify, plus an open-source offline verifier |
| Public record that the document existed when signed | Not typically | ✓ The SealProof Anchor, stamped into Bitcoin |
| Signature shown as valid in Adobe Acrobat | Yes | — Coming. Until then, verify at sealproof.io/verify |
| SOC 2 or ISO 27001 report | Yes | — Not yet. We provide a completed security questionnaire instead |
The middle column reflects features DocuSign and Adobe Acrobat Sign publicly document; they vary by product and plan. DocuSign and Adobe Acrobat Sign are trademarks of their owners, and SealProof isn't affiliated with them.
A short email that answers what they'll ask.
Copy it, fill in the names, and send it from your own email. Attach a sealed sample if they want to see one.
Subject: Electronic signatures for our applications Hi [underwriter's name], We use SealProof (sealproof.io) for electronic signatures. A few points that usually answer underwriting's questions: - It's designed around the U.S. ESIGN Act and UETA. Each signer consents to sign electronically, and that consent is recorded. - Every signed PDF ends with a Certificate of Completion: who signed, when, from which IP address and device, and how they were identified (for example an emailed code or a photo ID check). - The finished PDF is sealed and independently timestamped, so any change after signing is detectable. - You can check any document we send at sealproof.io/verify, free and without an account. A vendor review packet (security questionnaire and a sample sealed document) is available at sealproof.io/trust. Can you confirm you'll accept applications signed this way, or let me know what else you need? Thank you, [Your name] [Agency]
When a carrier pushes back.
My carrier's guidelines name DocuSign. Can I still use SealProof?
Will the signature show as valid when they open it in Adobe Acrobat?
How does the underwriter know the document wasn't changed?
What if there's a claim years from now?
Do you have SOC 2 or ISO 27001?
Can I send a carrier each form separately?
More detail for security and compliance reviewers is on Why SealProof can be trusted.