- What is michael-rubel/laravel-stripe-integration used for?
- It is a Laravel convenience package for Stripe that provides config publishing, container bindings for the Stripe client, and wrappers for common API flows such as customers, charges or PaymentIntents, subscriptions, and webhooks. It is a boilerplate reducer over stripe/stripe-php, not a gateway-neutral payment abstraction. Use it when you want a single-gateway Laravel integration and are comfortable auditing the payment and webhook paths yourself.
- How do I install and configure laravel-stripe-integration?
- Install it with Composer, publish its configuration, and set your Stripe key, secret, and webhook signing secret in your environment or secret store. Then register the package's webhook route and verify it is reachable and signature-verified in your application. The package is technically easy to install; the harder work is building an idempotent, replay-safe, queued webhook ingestion path.
- Does this package support Laravel 10 and PHP 8.1?
- The evaluation describes it as fitting the Laravel 10 and PHP 8.1 to 8.2 generation, but you must check the package's composer.json for the exact php, laravel/framework, and stripe/stripe-php constraints. The 2.0.1 patch notes do not clarify the runtime Stripe SDK constraint, so do not assume compatibility from the release alone. Verify those ranges against your application before adoption.
- Should I use this package or Laravel Cashier for subscriptions?
- If subscriptions are your core use case, Laravel Cashier overlaps heavily with this package and is usually the more established choice. This package is better viewed as a thin convenience layer for common Stripe workflows rather than a full subscription billing system with dunning or reconciliation. Compare the features you need against Cashier before treating this package as the default.
- How does laravel-stripe-integration handle Stripe webhooks?
- It provides a pre-built entry point for webhook handling, but you still need to ensure the endpoint verifies Stripe signatures, de-duplicates events, handles out-of-order delivery, and queues processing. Those controls are required for any Stripe integration and are where real money errors such as double fulfillment or missed provisioning occur. Audit and likely extend the webhook path before using it in production.
- Is michael-rubel/laravel-stripe-integration safe for production payments?
- Treat it with caution on the card-data-adjacent path: the evaluation flags high security and payment-path risk, no disclosure process, and limited field testing. Version 2.0.1 fixed a payment method parameter defect, showing that payment request construction can contain functional bugs. You should keep Stripe.js or Elements client-side for PCI scope and audit secret handling, request construction, and webhook processing yourself.
- Can I test Stripe payments with this Laravel package?
- You can use Stripe test keys and test PaymentMethods or test clocks in your Laravel test environment, but the package itself does not remove the need for webhook and idempotency tests. Mock or fake Stripe API calls where possible and add integration tests for signature verification, duplicate events, and failed payment flows. Do not rely on the package's wrappers alone to prove production behavior.
- Does laravel-stripe-integration support multiple payment gateways or Stripe Connect?
- No, it is a single-gateway convenience layer over stripe/stripe-php and does not provide a gateway-neutral interface or marketplace/Connect payout splitting. If you need multi-PSP routing, Connect payout splits, or tax and invoicing workflows, those concerns sit outside this package or must be built on top of it.
- Is michael-rubel/laravel-stripe-integration actively maintained?
- The 2.0.1 release is a low-activity maintenance signal: it is a semver patch with no new features or architectural changes, and the project has very low contributor throughput. It moves the repository from possibly abandoned to not fully dormant, but it does not establish a release cadence, patch lane, or security disclosure channel. Plan for limited upstream support and possible in-house fixes.
- What are alternatives to laravel-stripe-integration?
- Alternatives include Laravel Cashier for subscription billing, direct use of stripe/stripe-php with a small in-house StripeService and webhook controller, or another maintained Laravel Stripe wrapper. If you only need one-off PaymentIntents, a focused in-house service of roughly 150 to 300 lines may be simpler than adopting this package. Evaluate lock-in, which is low here because the package is MIT licensed, against maintenance and security risk.