Skip to main content
When subscribers pay through Apple or Google, the store handles many operating details for you: payment collection, refunds through the store, tax handling, card disputes, receipts, and payout timing. When subscribers pay on web, those responsibilities move to your web billing stack.

​
The basic shift

​
Stripe default

Stripe is the default payment rail for Recurr customers. In this model, your company owns the Stripe account and the direct billing relationship. You configure tax, refunds, disputes, payment methods, and payouts through Stripe and your internal operating policies. Stripe provides products such as Stripe Tax, refund tooling, and dispute workflows that can support that operating model.

​
Paddle early access

Paddle can be considered where a merchant-of-record model is important. A merchant of record, or MoR, is the party legally responsible for selling to the customer in the covered transaction. Paddle positions itself as a merchant of record and includes checkout, payment methods, customer portal, and related billing capabilities in Paddle Billing. Recurr treats Paddle support as early-access scoping. It is not the default rail.

​
Where Recurr fits

Recurr does not replace your payment rail. Recurr operates the migration and growth layer on top of the rail:
  • Subscriber surfaces
  • Migration flows
  • Lifecycle motions
  • Kairos decisioning
  • Cohort reporting
  • Access continuity with your stack
The rail is yours. Recurr helps you move subscribers onto it and grow the book that runs through it.