stripe-connect

What This Skill Does

The stripe-connect skill provides comprehensive integration capabilities for platforms and marketplaces to handle multi-party payment flows. It facilitates the onboarding of vendors, the management of Connected accounts, and the complex routing of payments. The skill is specifically architected to address the unique challenges of Stripe Connect, including choosing between Direct, Destination, and Separate Charges & Transfers. It includes critical guidance on configuring webhooks correctly, particularly the often-misunderstood requirement for dual-endpoint setups when utilizing Direct Charge patterns.

Installation

You can install this skill directly using the OpenClaw command-line interface. Run the following command in your project terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-stripe-connect

Use Cases

• Marketplaces: Facilitate payments where sellers or service providers are the primary recipients.
• SaaS Platforms: Implementing platform fees or rev-share models for vendor-provided services.
• Vendor Onboarding: Automated management of account verification statuses and requirements gathering.
• Multi-party Payment Flows: Splitting payments between the platform and multiple vendors securely.

Example Prompts

1. "Help me implement a Direct Charge checkout flow for my marketplace that properly charges a 10% platform fee."
2. "I'm having trouble with my webhooks not firing for Stripe Connect; can you review my endpoint setup and explain the Direct Charge webhook gap?"
3. "Show me the TypeScript code to initiate a Stripe Connect payment where the platform collects a fee while the vendor receives the balance."

Tips & Limitations

• Webhook Strategy: Always verify which charge pattern you are using. If you use Direct Charges, you must maintain separate webhook listeners for your Platform and the Connected accounts. Misconfiguration here is the most common cause of missing payment events.
• Account Status: Always check the account capability requirements on your Connected accounts before initiating payouts. Use the account.updated webhook event to track when a seller is ready to receive funds.
• Security: Never hardcode your STRIPE_SECRET_KEY or STRIPE_WEBHOOK_SECRET. Use secure environment variables.
• API Versioning: Ensure your integration is compatible with the latest Stripe API versions, as Connect features often receive breaking changes more frequently than standard payments.