- Is kmj/paypalbridgebundle a Laravel package?
- No. It is a Symfony2 bundle built around AppKernel registration, a DI extension, and a Configuration tree, none of which Laravel provides. Laravel has no bundle registry or Symfony compiler passes, so the bundle's reusable surface for a Laravel app is effectively zero.
- Can I install kmj/paypalbridgebundle with Composer in a Laravel project?
- Composer will typically refuse the install because the bundle's Symfony2 constraints do not resolve against illuminate/* packages and its PHP floor conflicts with PHP 8.1+. Forcing it with --ignore-platform-reqs would leave you with an unsupported payments dependency, which is a bad trade in a checkout path.
- Which Laravel and PHP versions does this bundle support?
- None officially. The bundle targets Symfony 2.8, which reached end of life in November 2018, so it has no PHP 8 support and no security patches. There is no Laravel version compatibility because it was never written as a Laravel package.
- What PayPal SDK does KMJ PayPalBridgeBundle depend on?
- It wraps paypal/rest-api-sdk-php, the older PayPal REST SDK that PayPal has retired in favor of the OpenAPI-generated paypal/paypal-server-sdk. Building new Laravel work on a retired SDK in thenpayment path is a non-starter for most teams. Check the repository's composer.json before assuming otherwise.
- Is kmj/paypalbridgebundle safe to use in production for payments?
- It carries high technical risk: an EOL Symfony 2.8 base, a deprecated PayPal SDK, six GitHub stars, and zero dependents. Payments are the highest-blast-radius place to accept an unsupported dependency. If a compliance review rejects EOL dependencies, the decision is already made.
- How do I add PayPal checkout to a Laravel app instead?
- Use paypal/paypal-server-sdk directly inside a Laravel service provider that binds a configured client into the container. Read credentials from config/services.php and .env, and expose injectable gateway classes rather than a bundle. This idiomatic pattern is roughly a one-day build for a basic checkout flow.
- What is the best Laravel alternative to this Symfony bundle for PayPal?
- A thin service provider plus a PayPalGateway interface backed by paypal/paypal-server-sdk. Putting the gateway behind an internal PaymentGateway contract also lets you swap PayPal for Stripe or Adyen later. That optionality is worth the small upfront effort.
- How should I handle PayPal IPN or webhooks in Laravel?
- Register a route and controller in Laravel, verify the PayPal webhook signature with the modern server SDK, and dispatch a queued job for order fulfillment. The bundle's IPN handling is Symfony2-specific and not reusable in Laravel. Always make webhook handlers idempotent.
- Can I migrate a Symfony2 app using this bundle to Laravel?
- You can, but treat it as a reimplementation, not a port. The bundle's service definitions and Configuration tree do not carry over; you would rebuild the client factory in a Laravel service provider and swap the retired REST SDK for paypal/paypal-server-sdk. Plan the framework upgrade and the payments SDK swap together.
- How do I test PayPal checkout in Laravel without using this bundle?
- Bind a fake implementation of your PaymentGateway interface in the test container and assert that your controller calls it. For integration tests, use PayPal sandbox credentials with the modern server SDK and never hit live endpoints from CI. This is simpler than trying to boot a Symfony2 bundle inside Laravel tests.