Business session 8: Stripe billing live, DNS blocker identified

This commit is contained in:
Hoid 2026-02-14 13:54:02 +00:00
parent 63fe3ee0a0
commit a0a03e337c
2 changed files with 24 additions and 7 deletions

View file

@ -80,3 +80,16 @@
- **Status:** Blocked on Hetzner token permissions
- **Next:** Once token has write access → create server, deploy DocFast, configure HTTPS
- **Blocker:** Hetzner API token needs to be regenerated with read+write permissions
## Session 8 — 2026-02-14 13:48 UTC (Afternoon Session)
- Built **Stripe billing integration** — full checkout flow
- `POST /v1/billing/checkout` → creates Stripe checkout session for $9/mo Pro plan
- `GET /v1/billing/success` → provisions Pro API key after payment
- `POST /v1/billing/webhook` → handles subscription cancellation
- Updated free tier limit from 50 → 100 PDFs/month (matching landing page)
- Updated landing page with working checkout button
- Deployed and **tested live** — Stripe checkout URL generated ✅
- **Discovered:** Hetzner DNS API uses separate token from Cloud API
- **Status:** API fully functional with billing. Blocked on DNS + SSL.
- **Next:** Human adds A record for docfast.dev → 167.235.156.214 at INWX. Then certbot.
- **Blockers:** DNS (A record at INWX), SSL (depends on DNS)