- Is t3xdeveloper/stripe-payment-jms a Laravel package or a Symfony bundle?
- Despite being described as a Laravel package, it is built on JMSPaymentCoreBundle, which is a Symfony bundle. Laravel does not natively load Symfony bundles or use the Symfony container and bundle conventions. Treat it as a Symfony-oriented payment bridge rather than an idiomatic Laravel integration.
- How do I install t3xdeveloper/stripe-payment-jms?
- You would install it with Composer using composer require t3xdeveloper/stripe-payment-jms. However, the package does not provide a Laravel service provider, facade, or publishable config, so installation alone will not wire it into a Laravel app. Expect to reimplement integration glue or use it only as a reference.
- Does t3xdeveloper/stripe-payment-jms support Laravel 10 or Laravel 11?
- There is no indication that it targets modern Laravel versions or provides Laravel-specific integration points. The package is built around a Symfony bundle and a legacy payment abstraction, not Laravel's container or Cashier conventions. Check composer.json constraints and expect compatibility problems on current Laravel releases.
- Does this package support Stripe PaymentIntents, SCA, and 3D Secure?
- The available context does not confirm support for PaymentIntents, SCA, or 3D Secure flows. Because the single release dates from March 2023 and likely pins an older stripe/stripe-php major, it may rely on legacy Charges semantics. Verify the Stripe object model and SDK version before considering it for any payments path.
- How are Stripe webhooks handled and verified in t3xdeveloper/stripe-payment-jms?
- The package does not document a Laravel-friendly webhook flow, queue integration, or idempotent processing. Webhook signature verification depends on the underlying Stripe SDK version and how you wire the endpoint yourself. Treat webhook handling as something you must design, verify, and test independently.
- Is t3xdeveloper/stripe-payment-jms production-ready?
- Risk is high: it has zero stars, zero dependents, a single maintainer, and a single 2023 release. There is no peer review or downstream bug reporting to validate it on a payment path. Adopting it realistically means forking and owning the code, not simply depending on it.
- Can I use t3xdeveloper/stripe-payment-jms with laravel/cashier or stripe/stripe-php?
- It is not designed to plug into Cashier or to act as a thin wrapper over stripe/stripe-php in a Laravel app. Mixing it with Cashier would duplicate payment abstractions and create conflicting flows. For Laravel, a thin internal adapter over stripe/stripe-php or Cashier is the more idiomatic choice.
- Does t3xdeveloper/stripe-payment-jms work with Symfony 6 or Symfony 7?
- It is described as Symfony 4/5-era and dependent on JMSPaymentCoreBundle, which is effectively legacy. Symfony 6 and 7 support is unlikely without forking and porting the bundle and its dependencies. Confirm the composer constraint matrix before spending time on a spike.
- What are good alternatives to t3xdeveloper/stripe-payment-jms for Stripe in Laravel?
- For Laravel applications, evaluate laravel/cashier or a small internal payment-provider wrapper around stripe/stripe-php. Both keep you on supported SDKs and idiomatic Laravel patterns. The useful idea to preserve from this package is the PaymentProvider seam, not the Symfony bundle itself.
- How do I test t3xdeveloper/stripe-payment-jms, and does it have CI or test coverage?
- The context provides no evidence of CI, test coverage, or a documented testing strategy. Stripe flows require mocked API responses, webhook signature tests, and idempotency checks that you would likely need to build yourself. Before adopting, confirm the package's test suite and run a bounded spike against Stripe test mode.