owner
Prices
Document price, product promise, delivery route, and refund rule together.
Do not change price copy without checking checkout and refund text.
money and locks
Payment change rules
Rules for pricing, Stripe, checkout, success/cancel pages, refunds, membership, gift readings, and paid reports.
The payment flow should be boringly reliable: no surprises, no double charges, no promises the product does not fulfill.
technical owner
Checkout
Test success and cancel pages, webhook notes, email delivery, and account archive.
Do not call checkout ready just because the button is visible.
support
Refunds
Use refund policy and support-op workflow, record reason and outcome.
Do not argue with a customer in mystical language or promise impossible outcomes.
Before payment edit
Clarify exactly what changes: price, promise, product, webhook, email, membership, or refund rule.
- Record current value and desired value.
- Check public pricing page and FAQ.
- Prepare rollback to previous product/price copy.
After payment edit
Verification ends only after the user path has been walked.
- Run test checkout if keys and environment allow.
- Open success/cancel pages and account purchase history.
- Confirm support macro still matches reality.
checklist
- Pricing page matches checkout product.
- Refund policy matches support macro.
- Email receipt/scroll access language matches delivery reality.
handoff
- Owner receives old price, new price, checked routes, test result, and rollback note.
red flags
- Price changed but FAQ did not.
- Success page promises what webhook/email does not do.
- Refund macro contradicts refund policy.
related doors