Stripe Connect Multi-Party Marketplace & Payouts Playbook

Architect multi-vendor platforms with Stripe Connect: controller properties, destination vs direct charges, application fees, and automated KYC onboarding

---
name: stripe-connect
description: Architect multi-vendor platforms with Stripe Connect: controller properties, destination vs direct charges, application fees, and automated KYC onboarding links. Use when working with Stripe Connect, Marketplace Payouts, KYC Onboarding, Split Payments.
triggers:
  - stripe connect
  - stripe connect
  - marketplace payouts
---

# Stripe Connect Multi-Party Marketplace & Payouts Playbook

## 1. When to Use This Skill
Load `skill-stripe-connect` whenever an engineering or operations task involves **Stripe Connect, Marketplace Payouts, KYC Onboarding, Split Payments**. Specifically:
- Architect multi-vendor platforms with Stripe Connect: controller properties, destination vs direct charges, application fees, and automated KYC onboarding links.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** Stripe Connect, Marketplace Payouts, KYC Onboarding, Split Payments
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://github.com/stripe/agent-toolkit`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **Stripe Connect**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
stripe accounts create --type=express
stripe transfers list
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide