Weave Code
Payum Stripe Bundle Laravel Package
flux-se/payum-stripe-bundle
Integrates the Stripe payment gateway into Symfony applications via Payum, providing gateway factory configuration and actions for handling Stripe payments, captures, and refunds through a unified API.
Payum Stripe gateways bundle
Frequently asked questions about Payum Stripe Bundle
- Is flux-se/payum-stripe-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle that wires the Payum Stripe gateway into Symfony's dependency injection container and configuration tree. It ships no Laravel service provider, no publishable config, and no framework-agnostic gateway factory. In a Laravel application only the underlying payum/stripe package is directly consumable.
- Can I install flux-se/payum-stripe-bundle in a Laravel application?
- Composer will install it, but the bundle itself is unusable in Laravel because it depends on Symfony's DI extension and config tree. You would have to register the gateway factory and all Payum services yourself. Treat it as a reference implementation for how to wire Payum to Stripe, not as a Laravel dependency.
- How do I integrate Payum Stripe into Laravel without the Symfony bundle?
- Bind payum/payum and payum/stripe manually: register a StripeCheckoutSession gateway factory, implement Payum's StorageInterface for tokens against Eloquent, and write your own Payment and Capture controllers. This is a multi-day spike, not an afternoon. The payoff is a framework-agnostic payment abstraction with a hosted Checkout redirect that keeps PCI scope at SAQ A and delegates SCA/3DS to Stripe.
- What Laravel, Symfony, and PHP versions does this package support?
- There is no Laravel version support because it is not a Laravel package. Version 3.0.1 adds Symfony 8 support, which requires PHP 8.4, implying the constraint matrix has moved forward. Confirm whether older Symfony and PHP branches in your matrix are still tested or whether 3.0.x has narrowed the supported range.
- Does this package support Stripe Checkout Sessions and SCA/3DS?
- The bundle exposes Payum's authorize, capture, and status workflows through a StripeCheckoutSession gateway factory, which uses hosted Checkout Sessions so SCA and 3DS are handled by Stripe. One-time card payments and standard Stripe flows are the stated scope. Whether setup and subscription Checkout modes are supported is not documented in the provided context and should be verified against the source.
- How do I configure Stripe API credentials with this bundle?
- In Symfony you define credentials and gateway services under the payum_stripe configuration key, which the bundle's DI extension turns into Payum services. In Laravel there is no equivalent config tree, so you instantiate the gateway factory with your Stripe secret and publishable keys manually. Keep both keys in environment variables and never commit them.
- Does the bundle handle Stripe webhooks and signature verification?
- This is flagged as an open question: it is unclear whether webhook signature verification is implemented in the bundle or expected of the host application. Validate this before you rely on webhooks for order fulfillment. If you integrate Payum manually in Laravel, you own the webhook endpoint and the signature check.
- Does flux-se/payum-stripe-bundle support refunds and partial refunds?
- Payum's abstraction includes capture and refund actions, but the provided context does not confirm partial refund support in this bundle. Edge cases such as partial refunds, session expiry, and duplicate webhook delivery have little peer validation given low stars and near-zero dependents. Test refund flows explicitly in Stripe test mode before going live.
- Is this package a fork of the Sylius PayumStripeBundle and is it still maintained?
- Yes, the repository is Sylius/PayumStripeBundle and flux-se/payum-stripe-bundle is the Composer name of the fork evaluated here. Version 3.0.1 shipping Symfony 8 support promptly suggests the fork actively tracks Symfony's release cadence, a narrow but real maintenance signal. Being a patch release with no behavioral changes, it says nothing new about bus factor or payment-behavior gaps.
- What are the alternatives for Stripe payments in Laravel?
- Laravel Cashier or a thin service around stripe/stripe-php with Stripe Checkout delivers the same SCA and PCI outcomes with far less abstraction. Choose Payum only if you deliberately want a framework-agnostic payment abstraction or your platform is already Symfony or Sylius based. The bundle itself is best used as a reference for wiring Payum to Stripe, not as a production dependency in Laravel.
Weaver
How can I help you explore Laravel packages today?