Stripe Subscriptions Capability Buildprint
This Capability Buildprint packages a guarded workflow for adding Stripe subscription billing to an existing host app.
It is designed for coding agents. It is not a copy-paste billing tutorial.
What it adds
- Stripe Checkout subscription session creation
- signed Stripe webhook handling
- persisted customer/subscription/entitlement state
- entitlement helper for protected host surfaces
- setup/blocked states for missing configuration
- verification and receipt requirements
What the host app must already have
- authenticated user identity
- server-side route/action capability
- persistence layer or approved persistence decision
- environment/config pattern
Execution profile
guarded
Billing touches money, secrets, provider callbacks, persistence, and access control. The applying agent must assess the host, plan the graft, implement through phases, verify, and write a receipt.
Agent flow
flowchart TD
A[Read BUILDPRINT.md] --> B[Read capability.yaml]
B --> C[Check compatibility.md]
C --> D[Write .buildprint/host-assessment.md]
D --> E[Write .buildprint/capability-plan.md]
E --> F[Contract and config]
F --> G[Core integration]
G --> H[Host wiring]
H --> I[User/operator surface]
I --> J[Verify]
J --> K[Write .buildprint/capability-receipt.md]
Proof levels
flowchart LR
A[structure] --> B[fixture]
B --> C[sandbox]
C --> D[live]
Use the highest honest level. Do not claim sandbox or live proof without real Stripe checks.
Non-negotiables
- No source edits before host assessment and capability plan.
- No hard-coded secrets.
- No unsigned webhook trust.
- No paid entitlement from checkout redirect alone.
- No install success claim without persisted entitlement readback or explicit blocker.