- Can I use jms/payment-paypal-bundle in a Laravel application?
- Direct runtime integration is not recommended. The package is a Symfony bundle built around JMS Payment Core, Symfony dependency injection, configuration, and event dispatching, and Laravel does not boot Symfony bundles. Selective reuse of specific PHP classes behind an internal PayPalGateway interface is possible, but the bundle should not become a core Laravel dependency.
- Does jms/payment-paypal-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel support. Release 1.2.0 adds Symfony 4 support and sets a PHP 5.6 minimum, but modern Laravel releases require PHP 8.x and Illuminate components rather than a Symfony kernel runtime. There is no Laravel service provider, facade, publishable configuration, or queue integration, so expect Composer and runtime incompatibility.
- What PayPal payment flows does jms/payment-paypal-bundle support?
- The bundle is intended to add PayPal support to JMS Payment Core and is best treated as a legacy Express Checkout integration accelerator. The available context does not indicate support for current PayPal REST Orders v2, webhooks, subscriptions, refunds, or card-entry flows. Release 1.2.0 appears to be a Symfony compatibility update rather than a PayPal API refresh, so confirm required flows before relying on it.
- How do I install jms/payment-paypal-bundle with Composer?
- You would normally install it with Composer in a Symfony application that also uses JMS Payment Core. In Laravel, installation may resolve some PHP classes but will not provide a working Laravel integration or service wiring. Run a compatibility spike first and expect dependency conflicts, especially around Symfony 4 components and the PHP version floor.
- Is jms/payment-paypal-bundle compatible with PHP 8?
- The release notes cited indicate a PHP 5.6 minimum and no declared support for PHP 7.4 or PHP 8.x. That is a hard blocker for modern Laravel applications, which require newer PHP versions. Treat the package as legacy unless you verify compatibility in an isolated spike and accept the maintenance risk.
- How do I configure PayPal credentials in jms/payment-paypal-bundle?
- Configuration is handled through Symfony bundle configuration and dependency injection, not through Laravel config publishing. Laravel does not consume the bundle's service aliases or configuration, so credentials would need to be managed in Laravel-native config and passed into an isolated adapter. Do not expect a publishable config file or Laravel-style environment setup from this package.
- Is jms/payment-paypal-bundle maintained and production-ready?
- Release 1.2.0 is a small positive maintenance signal because it adds Symfony 4 support, auto-wiring aliases, and a higher PHP floor. However, Symfony 4 is end-of-life, the PHP minimum remains 5.6, and there is no indication of refreshed PayPal API coverage, test coverage, or security posture. For Laravel production use, the technical risk remains high.
- What are alternatives to jms/payment-paypal-bundle for Laravel PayPal integration?
- Use a Laravel-native PayPal package or wrap the official PayPal REST SDK behind your own PayPalGateway interface. Prefer an implementation that supports current PayPal Orders v2, webhooks, refunds, and subscriptions as needed, with tests and active maintenance. The Symfony bundle is better used as reference material for legacy Express Checkout semantics than as a Laravel payment architecture.
- Can I test jms/payment-paypal-bundle against the PayPal sandbox?
- There is no indication in the provided context of refreshed tests, fixtures, or sandbox regression coverage. You would need to create your own compatibility spike with PayPal sandbox credentials and verify that its Express Checkout calls still work against current PayPal APIs. Treat any existing tests as insufficient until proven otherwise.
- Does jms/payment-paypal-bundle support PayPal webhooks, subscriptions, or REST Orders v2?
- The available context does not indicate support for PayPal webhooks, subscriptions, or REST Orders v2. The bundle is associated with legacy Express Checkout through JMS Payment Core, and release 1.2.0 appears not to touch the PayPal API surface. If your business requires modern PayPal products, assume this package does not cover them without explicit validation.