- Is miracode/stripe-bundle a Laravel package?
- No. Despite being described as Laravel-friendly, the package is built as a Symfony bundle: it registers through Symfony's Bundle class, uses a DI compiler pass, and relies on the Config component tree. Laravel has no registerBundles bootstrap and its container does not consume Symfony DI service definitions, so the container-level wiring that gives the bundle its value does not carry over. Treat it as a Symfony service, not a Laravel dependency.
- Can I install miracode/stripe-bundle in a Laravel 11 or 12 application?
- That is not recommended without a compatibility spike first. Laravel 11 and 12 pin Symfony 6 and 7 components, while this bundle declares its own symfony/* constraints; a bundle requiring older ranges such as ^4.4 or ^5.0 can hard-fail composer update or trigger a partial-update cascade that destabilizes the framework. Validate resolution in a scratch Laravel app before committing it to a roadmap.
- What does miracode/stripe-bundle actually do?
- It normalizes Stripe API key and environment configuration and exposes an injectable Stripe client through the service container, with some webhook-ready request handling. That is genuine but narrow leverage: it stops at the client boundary and does not own subscription lifecycle, invoicing, tax, or webhook idempotency. For a Symfony service on a compatible version range it is a defensible time-to-market convenience.
- How do I install miracode/stripe-bundle with Composer?
- Installation is a standard composer require miracode/stripe-bundle, followed by registering the bundle in your Symfony bundles configuration and supplying API keys and mode through the bundle's config tree. Setup is intentionally minimal, but you should first confirm the declared Symfony and PHP ranges resolve against your application's locked component set. If you are on Laravel, there is no equivalent registration step, which is the first sign the package is the wrong fit.
- Does miracode/stripe-bundle handle Stripe webhook signature verification?
- The package advertises webhook-ready request handling, but the supplied sources do not confirm whether it verifies Stripe signatures, manages idempotency keys, or handles replay protection. Those details matter more than the routing convenience, because an unverified webhook endpoint is a production liability. Inspect the webhook code and its tests before relying on it for anything beyond local experimentation.
- Does miracode/stripe-bundle support subscriptions, invoicing, and recurring billing?
- No. The bundle covers client wiring and configuration, not the subscription lifecycle, invoicing, or tax domain logic. That gap is exactly where laravel/cashier-stripe is stronger for Laravel applications, since it is first-party, maintained, and owns far more of the billing surface. If your requirement is conventional SaaS subscriptions, Cashier is the more direct answer.
- Does miracode/stripe-bundle wrap stripe/stripe-php or ship its own Stripe HTTP client?
- This is not confirmed by the available sources and it is one of the two unknowns that decide feasibility. A thin veneer over stripe/stripe-php is low risk and easy to reason about; a custom REST client is the more expensive long-term failure because it rots against Stripe's dated API versions. Check composer.json and the client implementation before adopting it.
- Is miracode/stripe-bundle actively maintained and safe for production?
- The project shows roughly 9 stars and 0 dependents, which is not a quality verdict but is a field-evidence signal: there are no downstream consumers surfacing edge cases and no issue history to mine for known failure modes. The bus factor is one, so opportunity here means unclaimed niche rather than undervalued asset, and adopting it transfers maintenance to you. MIT licensing and a forkable footprint bound the downside but do not reduce ownership cost.
- What Symfony and PHP versions does miracode/stripe-bundle require?
- The exact declared ranges are not confirmed in the supplied material, so read composer.json before planning anything. Constraint collision with your framework's pinned Symfony components is the most likely integration-time failure, especially on Laravel 11 or 12. Run a Composer resolution in a scratch project rather than assuming compatibility.
- What are the alternatives to miracode/stripe-bundle for Laravel payments?
- For Laravel, laravel/cashier-stripe is the first-party, maintained option and covers subscriptions, invoices, and webhook handling that this bundle does not. If Cashier does not fit, for example with Stripe Connect or marketplace payouts, wrap stripe/stripe-php directly behind your own small adapter interface. Use miracode/stripe-bundle as a reference implementation to read for Symfony, not as a dependency to adopt in a Laravel codebase.