- How do I install shapin/stripe in a Laravel application?
- Install it with Composer using composer require shapin/stripe. Laravel service-provider auto-discovery registers the package, then you publish the config file and set your Stripe API keys as environment variables. Finish with a sandbox round-trip such as creating a customer and a PaymentIntent before relying on it.
- Which Laravel and PHP versions does shapin/stripe support?
- The package does not publish a clear compatibility matrix in the available information, so check its composer.json constraints before installing. With very low adoption and a minimal health score, expect possible dependency conflicts at your next Laravel or PHP upgrade. Pin versions and test upgrades deliberately rather than assuming upstream maintenance.
- How does shapin/stripe handle Stripe webhooks?
- It advertises webhook handling with event routing, which can reduce boilerplate for receiving Stripe lifecycle events. You still need to verify Stripe signatures and confirm the wrapper follows current Stripe webhook behavior. Read the source before production because webhook failures directly affect billing state.
- Is shapin/stripe a good alternative to Laravel Cashier?
- For production billing, no. Cashier is vendor-backed and widely used for subscription and portal ergonomics, while shapin/stripe is best understood as a thin wrapper with no meaningful usage signal. Use the official Stripe PHP SDK directly or Cashier behind your own payment interface.
- Do I need to install stripe/stripe-php separately when using shapin/stripe?
- It likely depends on or wraps the official Stripe PHP SDK, but verify that in composer.json and the source. If it wraps stripe/stripe-php closely, migration and risk are manageable. If it reimplements Stripe HTTP calls itself, stop and use the official SDK instead.
- How do I configure API keys and models in shapin/stripe?
- Configuration is publishable and typically uses environment variables for the Stripe publishable and secret keys. The config also lets you map application models used by the billing helpers. Keep secrets out of version control and confirm which config keys the installed version actually reads.
- Can shapin/stripe handle subscriptions and recurring billing?
- The package claims support for subscriptions, recurring billing, and one-off charges through fluent helpers. However, there is no third-party confirmation of correctness under real payment traffic. Evaluate subscription lifecycle, proration, and webhook-driven state changes carefully before adopting it.
- Is shapin/stripe safe to use for production payment processing?
- Treat it as high risk on the payment path. It has around 4 stars, zero dependents, a single maintainer, and unknown provenance as a possible private fork. A security review of API key handling, webhook signatures, and card-adjacent code is mandatory before production use.
- How can I test shapin/stripe without charging real customers?
- Use Stripe test-mode keys and exercise a sandbox flow that creates a customer and a PaymentIntent. You can also mock the facade or service-container binding in Laravel tests. Test webhook signature verification and failure paths, not just successful charges.
- What are the best alternatives to shapin/stripe for Laravel billing?
- The safest options are stripe/stripe-php wrapped in a small first-party adapter, or laravel/cashier when subscription and billing-portal ergonomics matter. Both give you vendor-backed maintenance and a clear upgrade path. Adopt shapin/stripe only if source review shows a current thin wrapper and a measurable win over those options.