- Can I use ruudk/payment-stripe-bundle in a Laravel application?
- No. It is a Symfony2 bundle built around Symfony's bundle, dependency injection, and event system plus JMSPaymentCoreBundle, none of which has a Laravel equivalent. Running it in Laravel would mean a hybrid Symfony/Laravel stack or porting the thin Stripe gateway class out of its Symfony wiring, at which point you have written a custom integration. For Laravel, use stripe/stripe-php or Laravel Cashier instead.
- Is there a Laravel version of this Stripe payment bundle?
- There is no maintained Laravel version. The package is a Symfony2 bundle, archived, with 7 stars and 0 dependents. Laravel's idiomatic path is the official stripe/stripe-php SDK or Laravel Cashier for subscriptions and invoicing.
- How do I install ruudk/payment-stripe-bundle with Composer?
- You would add it via Composer and register the bundle in a Symfony AppKernel, then configure Stripe API credentials and the gateway service. That process assumes the Symfony2 container and JMSPaymentCoreBundle, so it does not map to Laravel's Composer and service-provider workflow. In a Laravel app, installation is not meaningful without a port.
- Which Laravel and PHP versions does this package support?
- The bundle targets Symfony 2.x-era constraints, roughly PHP 5.5 to 7.0, and legacy stripe/stripe-php versions from around 2015 to 2016. It was not built for Laravel at any version. Assume no compatibility with current Laravel or PHP runtimes and verify composer.json before any spike.
- What Stripe API features does this bundle support, such as Payment Intents, SCA, or subscriptions?
- It wraps the legacy Stripe PHP library for charges, customers, and refunds into JMSPaymentCore's plugin contract, predating Payment Intents. It has no Payment Intents or SCA/3DS2 support, which are mandatory for European cards under PSD2. Modern Laravel projects should use the official SDK for those capabilities.
- How does this bundle compare to laravel/cashier or stripe/stripe-php for Laravel?
- They are not really comparable. laravel/cashier and stripe/stripe-php are Laravel-first or framework-agnostic modern SDKs with Payment Intents, SCA, webhooks, and active maintenance. This bundle is a Symfony2 reference implementation with an abandoned transitive dependency tree.
- Is ruudk/payment-stripe-bundle still maintained and safe for production?
- No, it is not safe to adopt. It has had no maintenance since 2016, so there is no CVE response or dependency patching, and the archived Symfony and Guzzle tree from that era carries known advisories. Treat it as a historical reference, not a production dependency.
- How would I migrate from this Symfony bundle to Laravel's official Stripe SDK?
- Use a strangler pattern: inventory charges, refunds, customer creation, and webhook handlers, then map each to the equivalent Payment Intents, Refunds, and Customers calls. Introduce stripe/stripe-php pinned to a current API version behind an internal PaymentGateway interface you own, and port call sites one at a time. Keep the old path live only for in-flight transactions and decommission JMSPaymentCore after reconciliation confirms zero traffic over a full billing cycle.
- What are the dependencies of this bundle and why do they block Laravel integration?
- Its blocking dependencies are JMSPaymentCoreBundle, which is itself abandoned, legacy stripe/stripe-php versions that predate Payment Intents, and Symfony 2.x-era container, event dispatcher, and PHP constraints. Each one requires significant rework on its own, and together they are prohibitive for a Laravel integration. The bundle's real value is only a reference gateway adapter.
- Does this bundle handle webhooks, refunds, and idempotency correctly?
- It may include webhook handling from that era, but signature verification and idempotency semantics likely do not meet current expectations. The bundle predates Payment Intents and SCA, and there is no maintenance to address Stripe API drift. Treat any existing handlers as legacy and rebuild them on the official SDK with current webhook verification and idempotency keys.