What Stripe handles
Stripe remains the system for:- Payment collection
- Subscription billing objects
- Payment methods
- Payouts
- Refunds
- Disputes
- Tax configuration where Stripe Tax is used
- Balance and transaction reporting
What Recurr handles
Recurr handles:- Migration messaging and subscriber surfaces
- Web checkout flow design
- Cohort operations
- Kairos decisioning
- Lifecycle motions
- Reporting around migration and Oikos outcomes
- Access continuity with the customer’s stack
Why customer-owned Stripe matters
The billing relationship is structurally yours. If you leave Recurr, the Stripe account, customers, subscription records, and payment data are still in your operating stack. Recurr should make the web book easier to operate, not make the billing relationship harder to own.Alternative rails
Paddle can be scoped where merchant-of-record coverage or existing Paddle infrastructure makes it a better fit. That path is handled as early access.What gets confirmed before the pilot
Before the pilot, you and Recurr confirm:- Whether Stripe or Paddle is the right rail
- How any existing web billing setup connects to Recurr
- How tax is handled
- How refunds and disputes are governed