Weave Code
Stripe Bundle Laravel Package
herdwatch/stripe-bundle
HerdWatch Stripe Bundle integrates Stripe payments into Symfony applications, with configurable API credentials, payment intent and checkout support, webhook handling, and reusable services for common billing workflows. It helps teams add secure card payments and subscription-ready Stripe flows with...
Herdwatch Stripe Bundle is a Laravel package that wraps Stripe's billing APIs in a clean, opinionated integration. It gives you fluent access to checkout sessions, subscriptions, and webhooks without boilerplate, so you can ship payment flows faster while keeping configuration explicit and testable. Built for typical Laravel conventions, it plugs into your existing models, routes, and service container.
- Ready-made checkout and subscription flows with sensible defaults
- Secure webhook handling with signature verification and event routing
- Publishable config and migrations for easy customization
- Eloquent-friendly billable model traits for customers and plans
- Artisan commands to scaffold and sync Stripe resources
Ideal for SaaS apps that want Stripe billing without reinventing the plumbing.
Frequently asked questions about Stripe Bundle
- Does herdwatch/stripe-bundle work with Laravel?
- No, not as a drop-in dependency. It is a Symfony bundle that targets the Symfony kernel, DI container compiler passes, Configuration trees, and Doctrine ORM, while a Laravel app runs on the Illuminate container, service providers, and Eloquent. Adopting it in Laravel is not a configuration exercise; it would require running a hybrid Symfony/Doctrine stack or forking the bundle to strip the framework coupling, and neither cost is justified by what the package offers.
- How do I install herdwatch/stripe-bundle with Composer?
- In a Symfony application it is installed via Composer and registered in bundles.php, then configured through the bundle's Configuration tree. There is no Laravel service provider, no publishable config file, and no auto-discovery, so a Laravel install would leave you with unused classes at best. The supplied data also contains no Packagist presence evidence, so confirm the package is actually distributable before relying on it.
- Which Laravel, PHP, Symfony, and Doctrine versions does it support?
- There is no documented support matrix in the available information. The relevant version ranges to pin down are Symfony, PHP, Doctrine ORM/DBAL, and stripe/stripe-php, and none of them are stated. Laravel version support is effectively not applicable, since the package does not target Laravel at all.
- Is herdwatch/stripe-bundle production ready and actively maintained?
- The public signals say no: zero GitHub stars, zero dependents, and a maturity score of 15.4/100, which is no production signal whatsoever. The bus factor is one, and the package looks like a byproduct extracted from an internal Herdwatch product rather than a supported library. The listed release date of 2026-07-24 is also anomalous and should be reconciled before any due diligence continues.
- Should I use laravel/cashier or herdwatch/stripe-bundle for Stripe subscriptions?
- For a Laravel codebase, use laravel/cashier plus stripe/stripe-php. Cashier is first-party, covers the subscription and billing surface, and integrates with Eloquent and the Laravel container out of the box. The bundle's only genuinely differentiated idea is mirroring Stripe objects into a local relational store, and that is a pattern you can reimplement natively rather than a reason to adopt the code.
- Does herdwatch/stripe-bundle verify Stripe webhook signatures and handle events idempotently?
- The provided information does not document webhook signature verification or idempotent event persistence, so both must be verified before any use. This is a core security requirement for any Stripe integration, not a nice-to-have. If you cannot confirm signature verification and idempotency, treat the webhook layer as unimplemented.
- Does herdwatch/stripe-bundle store card data in my database?
- The bundle persists Stripe objects such as customers, subscriptions, charges, and events through Doctrine. Whether it restricts itself to non-sensitive identifiers and metadata is unverified, and any path that lands PAN, CVC, or full card payloads in your database is an immediate PCI scope expansion. Confirm exactly which Stripe object types are mapped and that no payment instrument data is ever stored.
- Can I use its Doctrine entities and migrations inside a Laravel app?
- Not cleanly. The bundle ships or expects Doctrine entity mappings and migrations, which collides directly with Laravel's own migration chain and schema handling. In a Laravel application you would want native Eloquent models and standard Laravel migrations instead, which means discarding a large part of what the bundle provides.
- What happens when Stripe releases a new API version?
- Any Doctrine mapping of Stripe objects bakes in an assumed API shape, and Stripe regularly versions objects and deprecates fields, so a schema-mirroring library is structurally fragile against that drift. Ask the maintainer whether the Stripe API version is pinned and what the upgrade story is. Also ask whether persistence is one-way from Stripe to the database or bidirectional, because the failure mode on drift differs sharply between the two.
- How do I mirror Stripe customers and subscriptions locally in Laravel instead?
- Use stripe/stripe-php for SDK access, verify webhooks yourself, and write to native Eloquent models from queued jobs so billing state is queryable and joinable to your app data. Add laravel/cashier where subscription billing is the actual requirement. That gives you the bundle's one real idea, a queryable local projection of billing state, with zero foreign-framework surface and no PCI surprises.
Weaver
How can I help you explore Laravel packages today?