connectlisted

Use for Stripe Connect — platforms and marketplaces that onboard third-party sellers/providers, route money to them, and take a cut. Covers connected-account creation (controller properties vs legacy standard/express/custom types vs Accounts v2), the three charge topologies (direct / destination / separate charges and transfers), application fees, onboarding (Stripe-hosted account links vs embedded Connect components), KYC/verification requirements, and payouts to connected accounts. Triggers — "Connect", "platform", "marketplace", "connected account", "split funds", "split a payment", "pay out sellers/drivers/hosts/providers", "application fee", "platform fee", "take rate/commission", "Stripe-Account header", "acct_", "on_behalf_of", "transfer_data", "destination charge", "direct charge", "separate charges and transfers", "transfer", "account link", "account onboarding", "embedded onboarding", "account session", "payout to seller", "KYC", "requirements/currently_due", "account.updated". API version pinned 20
Florkin/claude-stripe-skills · ★ 0 · API & Backend · score 70

Install: claude install-skill Florkin/claude-stripe-skills

# Stripe Connect Building payments for a **platform / marketplace**: you (the platform) onboard third-party sellers, service providers, or creators (**connected accounts**), move money to them, and typically keep a commission. Connect is orthogonal to *how* the payment is accepted — you still use PaymentIntents + a payment surface (see **stripe-suite:payments**). Connect adds three things on top: **who the account is**, **how funds are routed and split**, and **who is liable**. **API version pinned: `2026-06-24.dahlia`.** New here? Route through **stripe-suite:integration** first. ## When to use / decision tree ### 1. Which account model? **Stripe's current guidance (verified 2026-07, primary sources below):** the legacy `type` param (Standard / Express / Custom) is **obsolete** — don't start new integrations on it. Stripe's stated direction for new work is **Accounts v2** (role-based), *but* v2 is currently surfaced under `2026-06-24.preview`, **not** the stable pinned `2026-06-24.dahlia` — still preview-gated. The three models at a glance (field-level detail in `reference/accounts-and-onboarding.md`): ``` Legacy `type` param (standard | express | custom) ── OBSOLETE — existing integrations only, don't start here │ migration to controller props is optional & backward compatible ▼ Controller properties (v1, POST /v1/accounts, no `type`) ◄── DEFAULT for new work (GA on the pinned version) │ set fees.payer / losses.payments / requirement_collec