Stripe is one of the two provider integrations currently implemented in the repository.
What the integration covers
The current codebase includes Stripe paths for:
- checkout session creation
- billing portal session creation
- webhook signature verification
- webhook normalization
- refunds
- catalog synchronization
Configuration
Stripe wiring is built around:
- API key
- webhook secret
- environment selection
The provider layer can be created from explicit config or environment-backed config, depending on how your application assembles Effect layers.
What Purchase abstracts
Your app should not need to directly translate:
checkout.session.completed- invoice state transitions
- subscription event variants
- refund status variants
The Stripe adapter maps those into Purchase workflow and event categories.
Operational note
Stripe is usually the fastest way to exercise the full workflow surface during development because the repo already includes live-provider harnesses and generated webhook fixtures for it.