> ## Documentation Index
> Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe Connect

> Web payments settle directly to your Stripe account. Recurr's platform fee is taken as an application fee on each charge.

Migration uses **Stripe Connect Standard** — a Stripe account in your name, with Recurr as the platform that takes a fee per transaction. **You are the Merchant of Record on every subscription**: the named party on the subscriber's card statement, the legal counterparty, and the entity Stripe pays out. Recurr never sits in the legal payment chain.

## What this means in practice

* **You own the Stripe account.** It's in your company's name, with your tax/legal/banking details. You have a Stripe Dashboard login, full visibility into every charge, and you can leave Recurr at any time without losing access to the account or its data.
* **Web subscription payments settle to you.** Subscribers are charged on web; Stripe deposits the funds into your bank account on Stripe's standard schedule (T+2 by default).
* **Recurr takes its fee per charge.** The Recurr platform fee (3.5%, plus a 2.5% migration performance fee during the migration year on migrated subscribers) is taken as an `application_fee` on each charge. It appears as a line item on your Stripe Dashboard.
* **Stripe processing fees pass through.** Stripe's standard rates (\~2.9% + \$0.30 in the US, varies by region and card type) apply on top, charged by Stripe.

## Setup

<Steps>
  <Step title="Stripe Connect onboarding">
    During the pilot setup, Recurr generates a Stripe Connect onboarding link. You complete Stripe's standard flow — company details, banking, identity verification.
  </Step>

  <Step title="Account activation">
    Stripe verifies the account; activation typically lands within 1–3 business days. Pilot waves don't ship until the Connect account is live.
  </Step>

  <Step title="Webhook + reporting wiring">
    Recurr connects to the Connect account via standard Stripe APIs. No custom integration on your side.
  </Step>
</Steps>

## What's visible to you

In your Stripe Dashboard:

* Every charge, with the gross amount, the Stripe fee, and the Recurr application fee broken out
* Subscriptions, customers, and payment methods (encrypted card details)
* Refunds, disputes, and chargebacks (subject to your standard Stripe policies)
* Tax reports + payout schedules

In Recurr's dashboard:

* Same data, organized around migration cohorts and waves
* Migration-specific reporting (cohort migration rate, holdout deltas, churn comparisons)
* Operational alerts (failed payments, disputes, dunning state)

## What if you already have a Stripe account?

If you have an existing Stripe account that handles your existing web revenue (e.g., a refunds/support channel, occasional one-off charges), the migration uses a **separate Stripe Connect account** rather than your existing one. Reasons:

* Connect Standard accounts are designed for the platform-fee model
* Operational separation between migration revenue and other revenue keeps reporting clean
* Cancellation/leaving Recurr is cleaner with a separate account

The two Stripe accounts can both be in your name, both deposit to the same bank account if you want — they just serve different purposes.

[Branded checkout →](/integration/branded-checkout)