How native agreement signing works on Namegarage
A direct domain purchase outside Escrow.com needs a signed agreement. Buyers used to sign on DocuSeal in a separate tab. The buyer announcement shows what buyers see. This post explains how it is built.
Why we moved it
The hosted signer cost more than its monthly fee. Our code had to authenticate its webhooks, prevent duplicate submissions, recover lost ones, and check template versions. A rejected webhook could leave a purchase stuck after the vendor had marked it complete. The vendor's emails carried no test marker, so we could not rehearse safely. New purchases therefore sign on our own /agreement/ page. An agreement keeps the signer it started with.
Who may sign
The buyer first proves control of the purchase email address. A Google, Apple, GitHub, or LinkedIn sign-in counts only when the provider verified that address. Otherwise the buyer enters a six-digit code sent to it.
The seller signs only while signed in with an account on an allowlist. A signing link identifies the agreement. By itself, it authorizes nothing.
Each party consents to sign electronically, then types their name as the signature.
Authorization fails closed. If a session, allowlist, or agreement read fails, the request is refused. An error never becomes permission.
Records that cannot change
Agreement versions, documents, signatures, and events live in D1. Database triggers reject updates and deletes to the stored agreement versions, document bodies, signatures and event records. A correction to the buyer's details creates a new version instead of editing the old one.
The signed record is one self-contained HTML file. It ends with a signing certificate that lists consent times, how each email was confirmed, and signature times. The completion emails and the seller's Telegram notice carry the file's SHA-256, so either party can check a saved copy. The hash shows that the file is unchanged. It is not identity certification by a third party.
The agreement page loads only our own scripts: no analytics, ads, or third-party origins.
Test mode
Test mode runs the same guards as production: email confirmation, the seller allowlist, consent, and immutable records. Test agreements are stored as marked test rows, kept apart from real ones. Their email and Telegram notifications are marked [TEST].
Retiring the old integration
Moving new purchases off DocuSeal does not erase its history. Existing purchase records retain their read-only status paths. The Privacy Policy still names DocuSeal as a recipient for agreements signed there, because those hosted copies still exist. We’ve kept the provider account and its historical data.
Public catalog tools
The public catalog API, SDK, and agent skills still provide read-only catalog access. Buyers and sellers sign from their agreement page.

Comments
Comments are reviewed before publication. The Author badge marks replies from the author.
Your test session has expired. Stop testing to use comments and sign-in normally, or open a fresh test link to keep testing.
Stopping testing reloads this page in normal mode.
Read approved comments on the discussion page.
Open the discussion page