Domain management after the first confirmed payment

A successful first payment should let a buyer start setting up a leased domain. Two separate checks could delay that access: registrar routing that covered only one NameBright domain, and a billing retry that incorrectly marked a funded lease as past due.

Namewrench now discovers NameBright domains for funded leases while preserving GoDaddy support. The portal checks lease authority before contacting a registrar. A successful registration read identifies the account that can manage the domain. That choice stays fixed during a request, including the final check before a change and the readback afterward. An uncertain registrar operation still requires verification before another change can begin.

The first captured payment also remains separate from creating the schedule for future installments. If Stripe schedule creation needs a retry, the confirmed payment keeps the lease active and domain management available. Retrying schedule setup uses the existing idempotency controls. Actual missed installments, refunds, disputes and agreement closure keep their existing restrictions. The seller receives a warning when future billing remains unverified, with payment details and a link to review the customer in Stripe. A separate notice confirms recovery, and cases requiring manual repair say so.

Registration renewal remains Namegarage's responsibility. We continue to track coverage through the lease end plus 90 days and send seller reminders when that target is outstanding. Healthy current registration can support buyer setup while those reminders remain due.

Focused checks cover a captured test payment, a failed schedule request, buyer sign-in and a simulated nameserver change within the same flow. They also cover registrar discovery, GoDaddy fallback, ownership refusals and unchanged renewal reminders. The rehearsal uses isolated storage and fake providers; it does not change a customer's live nameservers.