Guide
Stripe Connect explained for non-developers
Updated 9 September 2026 · 7 min read
Stripe Connect is the part of Stripe that lets one company (a platform) sign up many other businesses (merchants) to take payments under their own Stripe accounts. Each merchant is verified individually and receives their own payouts, while the platform can automatically collect a fee from every payment it facilitates.
The problem Connect solves
If a software company simply collected everyone's money into its own Stripe account and paid businesses out later, it would be handling other people's funds — which in most jurisdictions means money-transmission licensing. Connect avoids this by giving every merchant their own account with their own verification and their own payouts.
The platform never holds the merchant's funds. It only takes a defined fee from each payment.
Who is responsible for what
The merchant is the seller of record. They own the customer relationship, the goods or service, refunds, and ultimately the disputes.
Stripe is the payment processor. It verifies the merchant, moves the money, and charges processing fees.
The platform provides software: onboarding flow, checkout pages, product catalogue, reporting. It charges for that software and can collect an application fee per payment.
How onboarding works in practice
The platform creates an account for the merchant and sends them to a Stripe-hosted onboarding link. The merchant enters business details, identity information and bank details directly with Stripe — the platform never sees or stores those documents.
Stripe reports back a status: whether charges are enabled, whether payouts are enabled, and what information is still outstanding. Good platform software surfaces that status plainly rather than leaving merchants guessing.
Application fees, and why they must be calculated server-side
When the platform creates a payment on the merchant's behalf, it can specify an application fee — a fixed amount that Stripe transfers to the platform automatically.
That amount must be calculated on the platform's own servers from the merchant's stored plan. If the fee were sent from the customer's browser, anyone could edit it to zero. This is a basic requirement, not an optimisation.
Direct charges versus destination charges
With direct charges the payment is created on the merchant's account: the merchant appears on the customer's statement, and the merchant bears Stripe's processing fee and dispute liability. This is the common model for software that serves independent businesses.
With destination charges the payment is created on the platform's account and funds are transferred onward. The platform's name shows on the statement and the platform carries more risk. It suits marketplaces where the buyer's relationship is with the marketplace, not the seller.
Frequently asked
- Does the merchant need their own Stripe account?
- Yes — Connect creates one for them as part of onboarding. They do not need to have signed up with Stripe beforehand.
- Who pays Stripe's processing fee under direct charges?
- The merchant does. The platform's fee is charged on top and is shown separately in Stripe's reporting.
- Can a platform see a merchant's identity documents?
- No. Documents are submitted directly to Stripe through its hosted flow. The platform only receives status information such as whether charges and payouts are enabled.