Software as a Service (SaaS) and marketplace businesses use Stripe Connect to route payments between themselves, customers, and connected accounts. You can use Connect to route payments or payouts and use Stripe Billing to support your recurring revenue model.
You can create subscriptions for connect accounts, which supports several approaches for collecting payments. You can create subscriptions for your connected account’s customers using direct or destination charges, for your end customers to directly transact with your platform, and to charge your connected accounts a fee for using your platform.
The following use cases describe how to use Stripe Billing to create subscriptions from end customers to connected accounts, to bill platform end customers, and to bill connected accounts.
|Create subscriptions from the end customer to the connected account||Create subscriptions for end customers to your connected accounts, which supports several approaches for collecting payments. In this example, Prices reside on the connected account.|
|Create subscriptions to bill platform end customers||Marketplaces can directly offer membership subscriptions without involving your connected account. In this example, Prices reside on the platform.|
|Create subscriptions to bill connected accounts||Platforms can create subscriptions for their connected accounts. In this example, Prices reside on the platform.|
Using subscriptions with Connect has these restrictions:
- Your platform can’t update or cancel a subscription that it didn’t create.
- Your platform can’t add an
application_fee_amountto an invoice that it didn’t create, nor to an invoice that contains invoice items the platform didn’t create.
- Subscriptions aren’t automatically cancelled when you disconnect from the platform. You must cancel the subscription after disconnection. You can use webhooks to monitor connected account activity.