A departing client says you never returned their access. A new VP says they never approved the work. A bank says the service was never delivered. Pactbound is the sealed, identity-verified, timestamped receipt that proves what changed hands, who accepted it, and when, so the accusation ends there.
Under federal law, an electronic record or signature in an interstate transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form.
Summary of 15 U.S.C. § 7001(a) · E-Sign Act, 2000
You offboarded the client cleanly in March. Handed over every credential, flagged the failing backup, walked their new provider through it. In September they’re breached, and their lawyer says you left them exposed and never disclosed it.
Your record is scattered across three inboxes. The new provider won’t corroborate. You’re proving a negative, six months cold. Pactbound is what you wish that handoff had gone through. Every credential and disclosure sealed and formally acknowledged by the receiving party the day it happened, identity-verified and timestamped, in one receipt that settles it before it reaches a courtroom.
Six fights you stop having
Six months after a clean offboarding, a former client claims you never handed over access, or never warned them the backup had been failing. A sealed handoff, formally acknowledged by their new provider the day it happened, ends that argument before it starts.
Every bundle ships with structured evidence: identity-verified acknowledgments, signed timestamps, hash-of-file proofs. When you escalate, you escalate with a record built to be read, not a Slack thread.
The VP who approved the design left. The new VP wants it redone for free because they ‘never signed off.’ A sealed acknowledgment from the named original stakeholder settles it in one link.
‘While you’re in there, can you also...’ becomes contractual when it goes unrebutted. Pactbound captures every change as a sealed disclosure the other side formally acknowledges or rejects in writing.
A client paid by card, used the work, then filed a dispute claiming non-delivery. The sealed bundle is the proof-of-delivery-and-acceptance artifact a processor’s evidence form asks for, ready to attach.
A client sues two years later claiming you misrepresented the scope. Your insurer wants evidence of what was scoped, delivered, and accepted. Pactbound is that record, timestamped independently.
Three steps
Use it on a client transition, a milestone, or a single risky handoff. The receipt is yours either way.
Drag in the files, credentials, configs, and disclosures: what’s included, what’s known-broken, what’s out of scope. Pactbound packages everything into a sealed, tamper-evident bundle.
The client or successor opens a link, reviews every disclosure and item, and acknowledges via one-time-password email verification. Every view and signature is recorded with the exact timestamp and IP.
The receipt is timestamped independently, exportable as PDF, and structured to drop into a dispute, a small-claims filing, an insurance claim, or simply your own files as cover.
The eight handoff moments
The primitive
Change one byte and the receipt breaks. Anyone can confirm it’s genuine, independently, even if Pactbound disappears tomorrow. The cryptographic details are on the trust page for whoever wants them. How this stands up in court →
Every bundle ships with everything an external party needs to confirm authenticity: file hashes, the Merkle root, the timestamp reference. The verifier is open source. That’s what makes the receipt hold up: nobody has to trust us for the math to check out.
$ node scripts/verify-bundle.mjs bundle.pactbound --check-onchainYour first sealed handoff is free. No credit card. The next time a client, a successor, or a bank says it never happened, you’ll have the receipt that ends it.
Seal your first handoff: free