- Can I use sylius/payum-bundle in a Laravel application?
- No. It is a Symfony bundle built for Sylius and depends on Sylius core bundles, the resource registry, payment entities, and the Sylius state machine. Laravel has no bundle system or service-provider path that can satisfy those dependencies without installing Sylius itself. For Laravel, use payum/payum core directly or a Laravel-native payment package.
- What does sylius/payum-bundle actually do?
- It connects Sylius payment methods to Payum gateways so store admins can configure payment providers and process capture, authorize, and related operations through a consistent API. It supplies gateway factories, actions, and integration with Sylius Payment and order workflows. It is not a standalone payment library; it is the Sylius integration layer for Payum.
- Does sylius/payum-bundle support Laravel 10 or 11?
- No, the package does not target Laravel versions. It targets Symfony and Sylius versions, and its compatibility is tied to the Sylius release train. Laravel 10 or 11 applications cannot install it as a working payment dependency. Look at Laravel Cashier, Omnipay, or payum/payum if you need multi-gateway abstraction.
- What is the Laravel alternative to sylius/payum-bundle for multiple payment gateways?
- Use payum/payum core with an Eloquent StorageInterface implementation if you need authorize, capture, and refund pipelines across many providers. For simpler hosted-checkout needs, Laravel Cashier or Omnipay with vendor SDKs usually has less surface area. There is no direct Laravel port of this bundle.
- How do I install sylius/payum-bundle?
- In a Sylius application it usually arrives transitively with sylius/sylius, but you can require it with composer require sylius/payum-bundle. You then register gateway factories and configure sylius_payum gateways in Symfony configuration. Installing it in Laravel is not supported.
- Is sylius/payum-bundle maintained and safe for production?
- Code risk is low: it is small, stable, MIT-licensed, and used inside Sylius deployments. Maintenance follows Sylius core because this is a read-only subtree split with no independent issue tracker or release cadence; fixes and security patches arrive through Sylius releases. Treat it as supported but transitional while Sylius develops its PaymentRequest abstraction.
- Can I use Payum with Laravel without Sylius?
- Yes. payum/payum core is framework-agnostic and provides gateway factories, action pipelines, token-based payment links, and pluggable storage. You must implement StorageInterface against Eloquent and rebuild credential encryption, gateway configuration UI, payment state transitions, and token lifecycle yourself. That is a multi-week build, not a simple install.
- Does sylius/payum-bundle support authorize, capture, and refund?
- It exposes Payum's capture, authorize, and related payment operations through Sylius payment methods and gateway configuration. Refund and other operations depend on the specific Payum gateway factory and its actions. Check the gateway factory you plan to use for supported operations such as partial refunds or SCA and 3DS2.
- How do I configure payment gateways with sylius/payum-bundle?
- Configure gateways under sylius_payum in Symfony configuration and register or extend Payum gateway factories where needed. Sylius stores gateway settings and encrypted credentials through its PaymentMethod and GatewayConfig model, exposed in the admin. In Laravel you would have to design equivalent configuration and credential storage yourself.
- Is sylius/payum-bundle deprecated or being replaced in Sylius?
- Sylius has been introducing its own PaymentRequest abstraction and is moving away from Payum long term, so this bundle is best treated as a supported but transitional bridge. Confirm deprecation status against the Sylius major version you target. It remains the Payum integration path for current Sylius releases but is not a forward-looking Laravel dependency.