- How do I install laravel-cashier-stripe-connect in a Laravel app?
- Install it with Composer using composer require expdev07/laravel-cashier-stripe-connect. It is designed as a drop-in on top of Laravel Cashier, so you should already have Cashier configured with your Stripe keys and the Billable trait on your models. Expect to publish any package config and run a migration if one ships with it, then confirm the Cashier version constraint resolves before writing code. The install itself is mechanically easy; the Stripe Connect account lifecycle around it is the larger effort.
- Does laravel-cashier-stripe-connect work with Laravel 10 or Laravel 11?
- The most recent release is from April 2022 and supports Laravel 9, with no evidence of Laravel 10 or 11 support. Because the package also pins a Cashier range, which in turn pins a Stripe PHP SDK range, a framework upgrade can deadlock the dependency chain. Treat the framework version as the gating question and test Composer resolution in a branch before committing to the package.
- What Laravel and Cashier versions does this package support?
- The metadata shows Laravel 9 support on the latest release, and the package constrains a range of Laravel Cashier versions. Cashier then constrains the Stripe PHP SDK, so effective compatibility is a three-way constraint chain rather than a single requirement. Check the actual composer.json constraints against your installed Cashier version before adoption, because one mismatch can block the install.
- Does laravel-cashier-stripe-connect replace Laravel Cashier?
- No. It is a thin extension that adds Stripe Connect semantics to Cashier's billable models, so it inherits the Billable trait, customer and subscription columns, migrations, webhook controller conventions, and Cashier's Stripe SDK pin. That makes it additive and low-friction if you already run Cashier, but adopting it means adopting Cashier's schema and billing model as a package deal if you do not.
- How do I create destination charges and application fees with this package?
- The package exposes Stripe Connect concepts such as destination charges, application fees, and platform-controlled transfers through the Cashier API you already use. In practice you check that the connected account has the required capabilities before charging, then create the charge with the fee and transfer intent expressed through the package. Reconcile fees and transfers against Stripe's own records, because a convenience wrapper can obscure where the money math actually happens.
- Does this package handle Stripe Connect onboarding and KYC for connected accounts?
- You should assume it does not own that state for you. A two-sided marketplace still needs connected-account identity, hosted onboarding and re-onboarding after requirement changes, capability checks, fee configuration, and payout reconciliation. The package adds ergonomics on top of Cashier, but your application remains the owner of the account-to-seller mapping and any ledger of record.
- Is laravel-cashier-stripe-connect safe to use in production?
- It carries meaningful risk for a dependency that touches money movement. The last release was April 2022, the package has roughly 62 stars and a single-release history, and there is no changelog detail to infer test coverage, webhook completeness, or idempotency behavior. Low adoption and single-maintainer risk mean few eyes on correctness bugs, so plan for the possibility of forking and build reconciliation regardless.
- Is laravel-cashier-stripe-connect still maintained?
- The evidence points to low maintenance activity: the latest release is from April 2022 and its notable change is Laravel 9 support. A small issue base can look quiet but may simply reflect low usage rather than stability. Treat it as single-maintainer software and budget for pinning, patching, or forking if you adopt it.
- What are the alternatives to this package for Stripe Connect in Laravel?
- The main alternative is using Laravel Cashier plus the official Stripe PHP SDK directly, following Stripe's Connect documentation for accounts, onboarding, destination charges, and transfers. That is more code but removes a third-party abstraction and its version constraints. Forking this package is another option if you want the Cashier-style ergonomics and are prepared to maintain the Connect lifecycle yourself.
- Which Stripe webhooks do I need to handle for connected accounts?
- At minimum plan for account.updated and capability.updated so you can gate charges on the connected account's current status and outstanding requirements. You will also need the charge, refund, transfer, and payout events your marketplace relies on for reconciliation. The package's webhook coverage is not documented, so verify which events it routes through Cashier's webhook controller and fill the gaps yourself.