Skip to content
Tutorials Center
My learning

Topics

Lesson 25 of 38 ยท Connect and Marketplaces

Stripe Connect and Account Types

Understand what Stripe Connect is for, how platforms and connected accounts relate, how Standard, Express and Custom accounts differ, and which model fits a marketplace.

Up to now, the money went to one business: yours. Many products are different. A marketplace takes a payment from a buyer and passes most of it to a seller. A ride app pays drivers. A SaaS platform lets its customers charge their customers. Moving money between three parties, with tax forms, identity checks and payouts to bank accounts, is a heavy legal burden if you do it alone.

Stripe Connect is Stripe's product for this. Your business is the platform. Each seller is a connected account. Stripe handles identity verification (KYC), bank payouts and much of the compliance, and you decide how funds flow and what fee you keep. As elsewhere in this track, the sandbox cannot call Stripe, so we model the objects with plain JavaScript and show real API calls read-only.

The cast

Three parties in every sale

Customer Pays for the goods
Connected account The seller who earns
Platform You, taking a fee
1 / 2

Three account types

Standard Express Custom
Seller sees a Stripe Dashboard Full Dashboard Light Express Dashboard None; you build it
Who onboards the seller Stripe-hosted flow Stripe-hosted flow You collect data via API
Who handles support and disputes Seller and Stripe Mostly you You
Effort to build Lowest Medium Highest
Branding control Low Medium Full

Stripe is also moving to a newer model where you configure responsibilities on a single Account object rather than choosing one of three labels, but the trade-off is the same: the more control and branding you want, the more responsibility lands on you.

Choose Standard when sellers are independent businesses that already want their own Stripe relationship, for example a platform that integrates existing Stripe users. Choose Express for most marketplaces and gig platforms: quick onboarding, a ready-made payout dashboard. Choose Custom only when you must own the whole experience and are prepared to handle compliance questions.

Node.js Picking an account type

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Direct, destination and separate charges

How the customer's payment relates to the seller is another choice, covered in detail in Destination Charges and Fees:

  • Direct charges: the charge is created on the connected account. The seller is the merchant of record and appears on the statement. Common with Standard.
  • Destination charges: the charge is created on the platform, and funds are automatically transferred to the seller. The platform is the merchant of record.
  • Separate charges and transfers: you charge first and move money later, to one or many sellers. Useful for carts with several sellers.

How the objects relate

flowchart LR
  C["Customer card"] -->|"PaymentIntent"| P["Platform balance"]
  P -->|"Transfer"| A["Connected account balance"]
  A -->|"Payout"| B["Seller bank account"]
  P -->|"application fee"| F["Platform keeps"]

A destination-style flow: charge, transfer, payout.

Every connected account has an id starting acct_. You pass it in API calls: either as a Stripe-Account header (act as that account) or as a transfer_data[destination] parameter.

Node.js A tiny model of connected accounts

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with node:readline or process.stdin), it gets the next line from this box.

Creating an account (read-only)

JavaScript
// Read-only: needs the "stripe" npm package and your secret key
const account = await stripe.accounts.create({
  type: 'express',
  country: 'US',
  email: '[email protected]',
  capabilities: { card_payments: { requested: true }, transfers: { requested: true } },
});
console.log(account.id); // acct_...

Capabilities such as card_payments and transfers are permissions the account must be verified for. Until Stripe has enough information, a capability stays inactive, which is why onboarding comes next.

Connect availability depends on country, and the exact feature set changes over time. Check Stripe's current documentation for the countries and account types you plan to support.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In Stripe Connect, who is the "platform"?

    The platform is the business that builds the product and owns the Connect integration.
  2. 2. Which account type gives the seller a light Stripe-hosted dashboard with quick onboarding, ideal for many marketplaces?

    Express offers hosted onboarding and a lightweight dashboard while you keep control of the experience.
  3. 3. Which type puts the most compliance and support responsibility on you?

    With Custom you build the onboarding and dashboard and handle seller support and verification data.
  4. 4. What is a capability such as card_payments?

    Capabilities must be requested and activated after Stripe has verified the account.

Summary

  • Connect lets a platform take payments on behalf of sellers (connected accounts).
  • Standard, Express and Custom trade control against responsibility.
  • Direct, destination and separate charges describe how funds flow.
  • Accounts must complete verification before their capabilities become active.

Next: Onboarding Connected Accounts