Create reading
Write question, choose method, cards, and seal result. Paid AI scroll should not appear before payment.
- Reading saved.
- Claim/access path works.
- No paid text before checkout.
Paid path check
Stripe test flow
The path from sealed reading to paid status, AI scroll, email, and access must pass in test mode before real money.
The payment path is alive only after a full manual end-to-end test.
Pay with test card
Checkout should go to Stripe, return to success, and trigger the webhook chain.
- Checkout session created.
- Webhook signature verified.
- finance_events and stripe_events recorded.
Check AI and email
After payment, AI should create a structured answer, and receipt or ready email must not break webhook.
- paid_status=paid.
- AI job completed.
- Email arrived or error was logged without breaking webhook.
checklist
What to check
- Use test keys and test webhook.
- Do not enable real payments before live checklist.
- Check success/cancel pages.
- Check access recovery after closing the tab.
red flags
When to stop
- Checkout success exists, but webhook did not arrive.
- Payment succeeded, but paid_status did not change.
- AI answer was created twice.
- Client sees raw technical error instead of calm message.
done when
Definition of done
- One test payment passed from question to open result.
- Webhook idempotency prevents duplicates.
- Email and account help recover access.
related doors
Production checklistThe master list before real users enter.VercelEnvironment variables, redeploy, build logs, and domain.SupabaseMigrations, Auth, RLS, storage, and rate limit.Resend emailSender, receipt, recovery, and Oracle Letters.AI transparencyWhat AI does and what the server checks.SupportLost links, payments, accessibility, and errors.