- How do I install rap2hpoutre/laravel-stripe-connect?
- In principle you add rap2hpoutre/laravel-stripe-connect to your composer.json and, on Laravel 5.5+, the service provider is auto-discovered, then you publish the config file and set your Stripe client_id and secret. In practice the package's last release was January 2018 and its constraints target Laravel 5.x on PHP 7.0–7.2, so installation will fail dependency resolution on modern Laravel and PHP versions. Most teams instead copy the controller, routes, and config into their own app and adapt them.
- Does laravel-stripe-connect work with Laravel 9, 10, or 11?
- No, not as a Composer dependency. The package is archived and its illuminate/* and stripe/stripe-php constraints predate Laravel 9, so Composer will refuse to resolve it on PHP 8.1+. Forcing it with --ignore-platform-reqs only gets you an unmaintained code path built against a pre-7.x Stripe SDK and removed Laravel helpers. If you need the behavior, vendor the ~few hundred lines into app/ and update them.
- Is rap2hpoutre/laravel-stripe-connect still maintained?
- No. The repository is archived, the last release was 2018-01-25, and there is a single maintainer with no upstream activity. There are no security patches, no Stripe API version updates, and no PHP 8 fixes. The one unambiguous positive is the MIT license, which makes forking and inlining the code legally clean.
- How does the Stripe Connect OAuth flow work in this package?
- The package registers an onboarding route, redirects the user to Stripe's Connect authorize URL with your client_id, and handles the callback that returns a code and stripe_user_id, which it persists against the configured user model. That is the 2017-era Standard-account OAuth pattern based on client_id plus stripe_user_id. It is not Stripe's current recommended Connect Onboarding flow using Account Links for Express and Custom accounts. Verify the flow still matches the account type you plan to use before adopting it.
- Does this package protect the Stripe Connect OAuth callback with a state parameter?
- This must be verified in the source rather than assumed, because Stripe added the state parameter to the Connect authorize URL well after the package's last release. If the authorize URL is built without a per-session, single-use state value that is validated on callback, the flow is exposed to CSRF-style account-linking attacks where an attacker binds their Stripe account to a victim's app account. This is the highest-severity item in the package and the first thing to audit if you vendor it.
- Does laravel-stripe-connect support Express or Custom connected accounts?
- It targets the Standard-account OAuth model with client_id and stripe_user_id, which is the older Connect pattern. Express and Custom accounts are onboarded today through the Account Links API rather than OAuth, and that path is not part of this package. If your platform needs Express or Custom accounts, use the official stripe/stripe-php SDK directly and treat this repo as reference only.
- How do I charge a connected account with this package?
- The package provides thin helpers around the Stripe PHP SDK for creating charges on behalf of a connected user, relying on the stored connected account identifier. For Standard accounts today, platforms typically use their own secret key with the Stripe-Account header instead of persisting a connected-account OAuth token. Because the package predates Stripe's current APIs and SDK versions, expect to rewrite the charge calls against a current stripe/stripe-php release.
- Does it handle Stripe Connect webhooks like account.updated or account.application.deauthorized?
- No. The package covers only the onboarding entry point and callback, and it does not own webhook handling, account lifecycle events, disconnect and re-onboard flows, re-authentication after revocation, or the access_denied case on the callback. All of that is your responsibility to build. Since those events are essential for a production marketplace, plan for the package to be a small starting point rather than a complete integration.
- Is there a maintained alternative to laravel-stripe-connect?
- Use the official stripe/stripe-php SDK directly; Connect onboarding via Account Links, the Stripe-Account header, and webhook handling are all first-class there and stay current with Stripe API versions. Laravel Cashier covers subscriptions and billing but not marketplace Connect onboarding, so it is not a drop-in replacement. Given the package's few hundred lines of glue, writing the onboarding controller yourself is usually faster than adapting an archived dependency.
- What PHP and Stripe SDK versions does laravel-stripe-connect require?
- Its Composer constraints pin illuminate/* and laravel/framework to the 5.x line, PHP to roughly 7.0–7.2, and the Stripe PHP SDK to the 5.x or 6.x era. Running it on PHP 8.1+ with a current stripe/stripe-php release means both the framework glue and the SDK calls need remediation. Check composer.json in the archived repository for the exact constraints before planning any reuse.