Weave Code
Stripe Bundle Laravel Package
paymentsuite/stripe-bundle
A Symfony bundle that integrates Stripe payments into your application, providing ready-made services and configuration for charges, subscriptions, and webhook handling so you can accept payments with less boilerplate.
[READ-ONLY] Subtree split of the PaymentSuite Stripe component
Frequently asked questions about Stripe Bundle
- Is paymentsuite/stripe-bundle a Laravel package?
- No. It is a Symfony bundle and subtree split from PaymentSuite, not a Laravel-native package. It expects Symfony bundle registration, a DI container extension, event dispatcher, routing, and PaymentSuite core abstractions, so Laravel's container, package discovery, and configuration model do not map directly.
- Can I install paymentsuite/stripe-bundle in Laravel 10 or 11?
- A direct install in Laravel 10 or 11 is likely to fail because the package carries old Symfony and PHP constraints and has no Laravel package discovery. Even if Composer resolves it, you would need an adapter layer to bridge Symfony services into Laravel. Expect conflicts with PHP 8+, modern Laravel, Symfony 5/6/7, and current stripe-php.
- Does paymentsuite/stripe-bundle support Payment Intents and SCA/3DS2?
- It is very unlikely. A 2014 Stripe integration predates PaymentIntents, SCA/3DS2, SetupIntents, modern webhook signing, idempotency keys, and current Stripe API versioning. It probably depends on an old stripe-php SDK, so payment-correctness and compliance would require a rewrite rather than a configuration change.
- How do I handle Stripe webhooks with paymentsuite/stripe-bundle in Laravel?
- The bundle has Symfony-era webhook handling with signature verification, but its routing and event listeners do not map to Laravel's HTTP kernel. In Laravel you would need to reproduce the webhook route, translate configuration, and bridge Symfony services. Verify modern Stripe signature verification and idempotency requirements before relying on it; a Laravel controller with queued jobs and the official SDK is usually safer.
- What PHP and Symfony versions does paymentsuite/stripe-bundle require?
- The provided context does not list exact Composer constraints, but the last release was 2014-04-19 and the code follows Symfony 2-era conventions. Expect old Symfony 2 components that are end-of-life and conflicts with PHP 8+, Symfony 5/6/7, and modern stripe-php. Check the composer.json and PaymentSuite core version before any spike.
- Is paymentsuite/stripe-bundle maintained?
- No. The package is read-only, has 0 dependents, 10 stars, and no release since 2014-04-19. You should also check whether the upstream PaymentSuite monorepo is active, but this subtree should be treated as abandoned. Adopting it means owning a fork indefinitely.
- What are alternatives to paymentsuite/stripe-bundle for Laravel Stripe payments?
- For Laravel, use the official stripe/stripe-php SDK behind a thin service provider, configuration file, webhook controller, and queued jobs. Laravel Cashier is a good fit when its subscription billing model matches your product. Both options support modern PaymentIntents, SCA/3DS2, webhook signing, and idempotency better than this legacy bundle.
- Can paymentsuite/stripe-bundle handle subscriptions and recurring billing in Laravel?
- It advertises subscription and recurring billing helpers, but they are built on Symfony/PaymentSuite abstractions and an old Stripe SDK. Laravel Cashier or a custom integration with the official SDK is more reliable for invoicing, retries, SCA, and proration. Any evaluation must map its events and responses into your domain and test failure paths.
- How should I test paymentsuite/stripe-bundle before using it in production?
- Do not plan a direct production dependency. If you must evaluate it, isolate it behind an adapter, run Stripe test-mode flows, and verify webhook signing, idempotency, retries, SCA/3DS2, refunds, and reconciliation. Confirm dependency constraints and PaymentSuite core support first, because the likely outcome is a rewrite of the integration layer.
- Can I migrate from paymentsuite/stripe-bundle to Laravel Cashier or the Stripe SDK?
- Yes, but do it incrementally. Inventory payment flows, webhooks, refunds, and reconciliation, then spike a Laravel-native Stripe integration behind an internal gateway interface. Dual-run and fallback where possible, migrate webhooks and payment methods step by step, and decommission the bundle after audit and rollback criteria are met.
Weaver
How can I help you explore Laravel packages today?