Tamper-evident contract.
Click-to-sign captures the client’s name, IP address, user-agent, a device fingerprint (canvas / fonts / timezone / screen / language), a timestamp, and a SHA-256 hash of the contract body. The signed row becomes tamper-evident the moment the signature lands — a database trigger blocks edits to the body, the hash, and the signing fields. We can’t alter it after the fact, and neither can you. The hash proves the body hasn’t changed since signing; an independent trusted timestamp is what proves when it existed[1]— that piece is coming via RFC 3161 timestamping (free TSA on Solo, qualified TSA on paid).
Delivery gate.
Final files sit in private storage until the invoice is marked paid. The client only ever sees a 24-hour signed download link, and only after you click Mark paid. No mark-paid, no files. Every signed-URL fetch is logged with timestamp and IP, and that access log lands in the dispute kit. Re-issue the link as many times as needed. The lock is the leverage.
Dispute PDF.
One button generates a dated, content-hashed dossier you mail to your bank or processor: contract acceptance with hash and device fingerprint, IP and user-agent log, payment timestamp, file-delivery timestamps with sizes, signed-URL access log, full activity timeline, and the inbound BCC communication thread. Roughly twelve pages of organized evidence, structured around Stripe’s published dispute-evidence categories and Visa Compelling Evidence 3.0 main-element requirements.[2]
A clean dossier beats a screenshot scramble — but card networks favor the cardholder when the evidence is evenly matched. We help you start the response from a strong position; we don’t guarantee a win.
What this is, and what it isn’t.
Click-to-sign is a Simple Electronic Signature (SES). In the US it’s already fully enforceable under ESIGN/UETA — there’s no upgrade tier and no QES needed. SES is also admissible under EU eIDAS, UK ECA 2000, Canada PIPEDA + UECA, and Australia ETA 1999. For EU contracts that legally require a Qualified Electronic Signature(QES), the upload path is coming: download the PDF, sign with any QES tool you have (DocuSign QES, Adobe Sign QES, any EU Qualified Trust Service Provider, a national gov tool), upload the signed PDF back — PaidProof preserves it and timestamps the upload. PaidProof is tooling. The contract is yours, the parties are yours, and the legal weight is yours. See /evidence for the field-by-field breakdown.
[1] A self-stored hash proves integrity(the body hasn’t changed) but cannot, on its own, prove when the document existed — the system holding the hash also controls its clock. RFC 3161 timestamping fixes that with an independent Time Stamp Authority signature. Roadmap item, not yet shipped — tracked transparently.
[2]No tool can guarantee a chargeback outcome — issuers and card networks decide. PaidProof produces the evidence package processors and courts ask to see. See the disclaimer and /evidence.