Skip to main content
Moving subscribers to web billing gives the app a direct commercial relationship. It also makes billing operations more visible. This page is educational. It is not tax, legal, or accounting advice.

Billing operations

With Stripe, you own the account and configure the billing setup. Stripe provides payment, subscription, refund, dispute, and tax tooling. Recurr operates subscriber migration and Oikos motions on top of the rail. With Paddle, the model can differ because Paddle acts as merchant of record for supported transactions. Paddle support in Recurr is early-access and scoped per customer.

Tax

On the stores, Apple or Google generally handles tax collection and remittance for store transactions. On web, tax depends on your rail and operating model:
  • Stripe customers typically configure tax directly, often through Stripe Tax or an external tax provider.
  • Paddle customers may use Paddle’s merchant-of-record model where Paddle is responsible for supported tax handling.
For more detail, see tax on web billing.

Refunds

Refund policy remains a business decision. On Stripe, refunds are issued through Stripe. Stripe notes that original processing fees are not returned when a payment is refunded. See Stripe’s refund documentation. On Paddle, refund behavior follows the Paddle setup and merchant-of-record model.

Disputes

Disputes are part of direct billing. Stripe disputes have response windows and evidence requirements. Stripe documents dispute response flows in its dispute response guide. Recurr’s role is to preserve the subscriber and event context around a transaction so the customer can understand what happened and respond through the rail.

What Recurr helps with

Recurr helps customers prepare:
  • Subscriber-facing billing language
  • Help-center content
  • Cancellation guidance
  • Support macros
  • Reporting context
  • Cohort-level refund and dispute monitoring
The rail remains the source of truth for payments.