laravel-stripe-connect_skill

This skill helps you implement Laravel Stripe Connect for multi-vendor marketplaces, enabling onboarding, payouts, and split payments with guidance.

TypeScript

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill fusengine/agents --skill laravel-stripe-connect

SKILL.md7.9 KB

Overview

This skill helps build marketplaces and platforms using Stripe Connect in Laravel and TypeScript contexts. It guides seller onboarding, payment flows (destination charges, transfers), commission handling, payouts, and webhook-driven reconciliation. The content focuses on practical code patterns, architecture, and operational rules to reduce liability and implementation errors.

How this skill works

The skill inspects existing payment models and suggests Connect-specific components: seller account storage, onboarding links, payment intent creation with transfer_data, and webhook handlers for account and payout events. It enforces critical rules like KYC checks, negative-balance handling, idempotent payment creation, and persisting stripe_account_id. It also recommends agent-driven workflows for research, codebase exploration, and automated validation.

When to use it

Implementing multi-vendor marketplaces where funds flow to sellers
Onboarding sellers and running KYC before payouts
Charging customers while collecting platform commissions
Handling split payments, destination charges, or transfers between accounts
Building payout flows and webhook-driven reconciliation

Best practices

Prefer Express accounts for most marketplaces unless you need full UI control
Always persist stripe_account_id and update seller onboarding status via webhooks
Enforce webhook signature verification and handle account.updated events
Use idempotency keys for payment creation and store transaction records locally
Test extensively with Stripe test mode, CLI, and test clocks; never enable payouts pre-KYC

Example use cases

E-commerce marketplace collecting a platform fee on each sale and transferring remainder to seller via destination charge
On-demand services onboarding drivers/providers with Express accounts and paying them out weekly
SaaS platform that distributes creator revenue while retaining commissions and managing refunds
Implementing refunds and dispute handling workflows that check seller balance and platform liability
Automated onboarding flow: create account, generate onboarding link, redirect seller, validate via account.updated webhook

FAQ

Choose Standard if sellers handle support and Stripe UI is fine. Choose Express for a good balance of platform control and Stripe-managed UI. Choose Custom only if you need full control and accept extra compliance overhead.

How should I handle refunds if a seller has negative balance?

Detect negative balances and either require the seller to top up, absorb the loss as platform liability, or offset future payouts. Implement checks before enabling payouts and document liability per account type.