Connect の SaaS プラットフォームとマーケットプレイスの概要

Connect allows you to offer payment processing and other embedded B2B services to third parties, known as connected accounts. Connect primarily supports the following types of business models: SaaS platforms and marketplaces.

While a wide variety of integrations are possible, we provide detailed, step-by-step guidance for building a basic SaaS platform or marketplace. You can use one of these examples as is, or as a starting point for building a custom integration tailored to your business.

SaaS platforms

Your platform provides services to connected accounts, including the ability to collect payments directly from their customers. An example could be an e-commerce platform that hosts online storefronts for independent sellers, such as Shopify.

• Connected accounts act as the merchant of record (MoR), responsible for providing goods and services to their customers.
• Your platform can collect per-payment application fees and fees unrelated to payments, such as monthly subscriptions. You can either refer connected accounts to Stripe through a referrer model or resell Stripe products and services to them through a reseller model.
• Your platform doesn’t pay any Connect-related fees as long as Stripe sets payment pricing and directly charges fees to connected accounts.
• You can choose to be responsible for covering connected accounts’ negative balances. However, we recommend that you have Stripe take responsibility through Stripe Managed Risk.

SaaS platform flow of funds

The following diagram illustrates the flow of funds in a basic SaaS platform. A customer makes a purchase from a connected account, and might not be aware that their transaction involves any other entity. In turn, the connected account purchases services from both Stripe and the platform.

^*Platform fees can include application fees and subscription fees.

Example SaaS platform Connect integration

For an example of a Connect integration that implements a SaaS platform, see Furever, a demo SaaS platform that provides payment software for pet grooming businesses.

Marketplaces

Your platform processes payments for connected accounts and distributes funds to them. Examples could be a website selling goods from independent vendors, such as Etsy, or a food ordering app that splits payments between delivery drivers and restaurants, such as DoorDash.

• プラットフォームは通常、 マーチャントオブレコード (MoR) であり、連結アカウントが顧客に提供する商品やサービスに対して法的に責任を負います。
• Your platform collects per-payment application fees from connected accounts. You can also resell Stripe products and services to connected accounts through a reseller model.
• プラットフォームは、連結アカウントとの間の資金フローを制御します。1 回の決済から複数の連結アカウント間で資金を分割できます。
• In addition to payment processing fees, your platform pays Stripe a monthly fee per connected account and fees for payouts to connected accounts.
• Your platform is ultimately responsible for covering any connected accounts’ negative balances.

Marketplace flow of funds

The following diagram illustrates the flow of funds in a basic marketplace. A customer makes a purchase from the platform, but can be aware of connected accounts that participate in fulfillment. The platform pays Stripe for payment processing services and pays the connected account for goods or services that it provides to the customer.

^*The platform withholds fees from the connected account’s funds to cover its Stripe fees and other monetization.

Example marketplace Connect integration

For an example of a Connect integration that implements a marketplace, see Rocket Rides, a demo marketplace that connects independent airplane pilots with customers.

Key business model differences

Use the following table to determine the best integration for your business.

Integration options

You can configure a number of settings that determine the level of control that each party has over various elements of your integration. Most of them have recommended or required options, depending on whether your integration is a SaaS platform or a marketplace. For example, we recommend that marketplaces pay Stripe fees, and require that they take responsibility for negative connected account balances. We also recommend using Stripe-provided embedded onboarding components if Stripe-hosted onboarding doesn’t meet your needs. The documentation and onboarding flow provide guidance about the best options for your integration.

The main settings include:

• Fee pricing options:
  • Stripe collects its fees from connected accounts, without direct involvement by your platform. Your platform can collect additional fees from connected accounts separately.
  • Stripe collects its fees from your platform, with your platform determining and collecting all fees from connected accounts. Connected accounts usually pay no fees directly to Stripe.
• Account UX options:
  • 連結アカウントは、Stripe ダッシュボードの全機能を使用し、かなりのレベルの管理を行います。
  • Connected accounts use a limited (Express) Stripe Dashboard, with your platform maintaining a significant level of control over them.
  • Connected accounts use a custom web application that you build using Connect embedded components or the Stripe API.
• Loss liability options:
  • Stripe is responsible for connected accounts’ negative balances.
  • Your platform is responsible for connected accounts’ negative balances. (Marketplaces must choose this option.)
• Account requirement collection options:
  • Stripe is responsible for collecting and verifying required business information from connected accounts, including when requirements change.
  • Your platform is responsible for collecting required business information from connected accounts and submitting it to Stripe, including when requirements change.
• Account onboarding options:
  • Connected accounts onboard to your platform through a Stripe-hosted flow.
  • Connected accounts onboard to your platform through a custom flow that you provide, usually built using customizable Stripe-provided components embedded in your platform application.