- What does lanos/laravel-cashier-stripe-connect do?
- It extends Laravel Cashier with Stripe Connect support so a platform can onboard connected accounts, accept payments on their behalf, and manage payouts. Instead of Cashier's single platform customer identity, your billable model can also carry a connected-account identity. That makes it relevant for marketplaces, multi-vendor apps, and platforms paying creators or service providers. It is designed as a drop-in layer on top of Cashier rather than a standalone billing package.
- How do I install laravel-cashier-stripe-connect with Composer?
- Install it with Composer alongside Laravel Cashier, then publish the package's config and migrations using vendor:publish and add the provided trait to your billable model. Because it is a drop-in extension, the setup mirrors a normal Cashier install: Stripe keys, migrations, and the Billable trait. Check the README and composer.json for the exact provider, trait, and publish tags before wiring it into an existing app. Verify the migrations are additive and reversible before running them against a real database.
- Which Laravel, PHP, and Cashier versions are supported?
- The package sits on top of Cashier and reaches into Cashier internals such as the Billable trait, StripeClient resolution, and the webhook controller, so version support matters more than usual. Verify the tested matrix in the repository's composer.json and CI config rather than assuming parity with the latest Cashier release. Cashier 13, 14, and 15 introduced breaking changes, and a package patching internals will typically lag those majors. Pin Cashier and stripe/stripe-php explicitly in composer.json and test upgrades in a branch.
- Do I need Laravel Cashier installed to use this package?
- Yes. The package is explicitly an extension of Laravel Cashier and assumes Cashier is already handling your platform billing, typically Stripe Billing subscriptions. If you only need one-off Stripe Connect payments and have no subscription billing, the plain stripe/stripe-php SDK is a simpler and more durable dependency. Adding Cashier plus this package purely for Connect is over-engineered for that case.
- Which Stripe Connect charge patterns does it support?
- Stripe Connect has three common money-movement patterns: direct charges on the connected account, destination charges from the platform with an application fee, and separate charges and transfers. The package targets these Connect flows, but you should confirm in the source which patterns are actually implemented before designing your checkout around one. Pilot a single account type and a single charge pattern end to end before broadening. Money movement details such as fees, refunds, disputes, partial reversals, and idempotency deserve your own tests.
- How do Stripe Connect webhooks work with Cashier's webhook route?
- Cashier's default webhook endpoint handles platform events, while Connect events arrive tagged with an account field and usually need either a second endpoint or a delegating controller. Confirm which events the package handles, such as account.updated, capability.updated, payout.*, and connected charge events, and verify signature verification on the Connect endpoint separately. Many integrations add an explicit route for Connect traffic rather than overloading Cashier's controller. Getting this topology right early avoids silent failures in onboarding and payout state.
- Does it handle Stripe Connect onboarding and Account Links?
- Onboarding is central to any Connect integration, so look for Account Link generation with refresh and return URLs, plus handling of requirements.due and capability changes on the connected account. The package exists to make that connected-account lifecycle manageable from your billable model. Check the source and README for exactly which onboarding pieces are included versus left to you. Account type selection, Express versus Standard versus Custom, is a platform decision you still have to make.
- How do I test laravel-cashier-stripe-connect in CI?
- Connect testing needs Stripe test-mode connected accounts and the Stripe CLI's Connect forwarding, which adds CI complexity compared with standard Cashier tests. Use a dedicated Stripe test platform account rather than your production account when sandboxing. Determine whether the package's own suite mocks Stripe or relies on live test mode, and plan to write integration tests for onboarding, charges, and payout flows yourself. Feature-flag the Connect charge path so checkout can fall back to your legacy flow while you validate.
- Is this package safe to use in production?
- Treat it as a reference implementation to vendor or fork rather than a black-box dependency. It has a small star count, no dependents, a single maintainer, and no independent production signal, so supply-chain risk is material. The dominant technical risk is coupling to Cashier internals that change across majors, followed by Stripe API drift in the Connect Accounts model. Review the code, pin to a reviewed commit, and keep an upgrade path you control.
- What are alternatives to laravel-cashier-stripe-connect?
- If you need both subscription billing and seller payouts, Cashier plus a small, reviewed Connect layer is the idiomatic Laravel approach, and this package is a reasonable starting point. If you only need one-off Connect payments, use stripe/stripe-php directly without Cashier. If your platform is on Paddle or Chargebee, or your billing is not Stripe-based, this package does not fit at all. Some teams also implement Connect in-house against the Stripe SDK for full control over webhooks and money movement.