Stripe Connect API logo

Stripe Connect API

Stripe Connect API

Stripe Connect is multi-merchant payments for marketplace / SaaS platforms — create per-merchant subaccounts, auto-split, compliance KYC, bank transfers.

Visit site ↗Documentation ↗Health checked 9h ago
Use it when

Deep Stripe ecosystem integration (manage normal payments + Connect split in one account)

Watch for

Connect fees additional to Stripe standard rates

First check

Enable Connect in Stripe Dashboard. POST /v1/accounts to create connected account → Onboarding link for merchant KYC completion → Use application_fee_amount when charging to take fee.

Auth
api_key
CORS
?
HTTPS
Yes
Signup
?
Latency
304 ms
Protocol
REST
Pricing
paid

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 304ms
01

About this API

Stripe Connect is Stripe's product designed for marketplace / platform businesses. Core scenario: you built an Etsy-style marketplace; buyers pay your site; you need to split money to specific sellers — not by first collecting everything into your account then wire-transferring to sellers (regulatory complexity, money transmitter licensing requirements), but by letting Stripe handle "agent collection" (money goes directly to corresponding connected account; you only take application fee as platform commission). Three account types: Standard (sellers have own Stripe dashboard, flexible but complex onboarding), Express (most common, Stripe provides simplified onboarding UI), Custom (you design onboarding but bear more compliance responsibility). Direct competitors: Adyen for Platforms, PayPal Marketplaces. Stripe Connect leads on developer experience.

02

What you can build

  • 1Marketplaces (Etsy model: buyer pays, money split to sellers)
  • 2SaaS platforms (your customers use your product to collect from their users)
  • 3Ride-hail apps settling drivers
  • 4Gig economy platforms
03

Strengths & limitations

Strengths

  • Deep Stripe ecosystem integration (manage normal payments + Connect split in one account)
  • Auto KYC/KYB (compliance burden shifts to Stripe)
  • Payouts support local clearing rails

Limitations

  • Connect fees additional to Stripe standard rates
  • Full Connect onboarding is complex (each merchant needs full KYC)
  • Some countries don't support platform models legally
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://stripe.com/connect/<endpoint> \
  -H "Authorization: Bearer $API_KEY"
# Some providers use X-Api-Key instead — verify in the docs.
05

Getting started

Enable Connect in Stripe Dashboard. POST /v1/accounts to create connected account → Onboarding link for merchant KYC completion → Use application_fee_amount when charging to take fee.

06

FAQ

Express or Custom?+

90% of projects use Express (simplest). Custom suits "I want full UI control" big customers but compliance responsibility doubles.

How is application_fee collected?+

Pass application_fee_amount (cents) when creating a charge — Stripe auto-deducts from payment to your platform account.

07

Technical details

CORS: ?HTTPS: YesSignup: ?Open source: No
Auth type
api_key
Pricing
paid
Rate limit
100 req/秒(标准)
Protocols
REST
SDKs
python, javascript, typescript, php, ruby, java, go, csharp
Response time
304 ms
Last health check
5/12/2026, 7:38:28 AM
08

Tags