Weave Code
Paybox Bundle Laravel Package
lexik/paybox-bundle
LexikPayboxBundle integrates the Paybox payment gateway into Symfony applications, simplifying payment request generation, callback handling, and response verification through configurable services and ready-to-use controllers.
LexikPayboxBundle eases the implementation of the Paybox payment system
Frequently asked questions about Paybox Bundle
- Is lexik/paybox-bundle a Laravel package?
- No. lexik/paybox-bundle is a Symfony bundle for integrating the Paybox payment gateway, not a Laravel package. It assumes Symfony bundle registration, service-container wiring, configuration trees, routing, and event dispatch, so Laravel package discovery and the Laravel HTTP kernel do not map cleanly to it. Treat it as a legacy Symfony integration and Paybox protocol reference, not as a Laravel dependency.
- Can I install lexik/paybox-bundle in a Laravel application with Composer?
- Composer may resolve the package, but installing it does not give you a working Laravel integration. The bundle expects Symfony conventions such as bundle registration, dependency injection configuration, and Symfony routing, none of which Laravel provides natively. Do not install it into a Laravel app without a time-boxed proof of concept and explicit ownership of an archived Symfony dependency.
- Does lexik/paybox-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel support for this bundle. It is a Symfony bundle that was last released in 2019 and has very low adoption, so you should not assume compatibility with modern Laravel or current PHP versions. Validate Composer constraints, Symfony component versions, PHP support, HTTP client behavior, routing, and event dispatch before committing to it.
- What Paybox functionality does lexik/paybox-bundle actually provide?
- The bundle simplifies Paybox payment request generation, callback handling, and response verification through configurable services and ready-to-use controllers. However, the Paybox or Verifone product and API version matter: Paybox Direct, System, Express, and hosted flows have different requirements. Confirm your contracted product and required flows such as 3-D Secure, SCA, refunds, partial captures, multi-currency, or recurring payments before relying on the bundle.
- Is lexik/paybox-bundle maintained and safe for production payment processing?
- The package is archived, was last released in 2019, and shows very low adoption with zero dependents. There is no credible upstream security patching path and no current PHP or Laravel compatibility guarantee, so technical risk is high. Payment code also requires PCI review, fraud controls, idempotency, reconciliation, and audit readiness, which this bundle does not solve on its own.
- How do I handle Paybox callbacks in Laravel if I use this bundle?
- You would not get Laravel-native callback handling from the Symfony bundle. A safer approach is to define a Laravel payment interface or port and implement Paybox behind it using current official Paybox or Verifone documentation. If you reuse the bundle, extract callback parsing and signature verification into framework-agnostic code, then add Laravel routes, idempotency checks, and reconciliation around it.
- What is the best alternative to lexik/paybox-bundle for a Laravel application?
- Prefer an official Paybox or Verifone SDK, a maintained PSP integration, or a hosted checkout flow that reduces PCI scope. If historical Paybox behavior is required, fork the MIT-licensed bundle and extract only request building, HMAC or signature verification, callback parsing, and response mapping into a small framework-agnostic library. Then wrap that library in a Laravel-native adapter with tests and operational monitoring.
- Can I reuse the Paybox request signing and response verification code from lexik/paybox-bundle?
- The MIT license generally permits reuse, but the code is tightly coupled to Symfony services, configuration, and controllers. Extract only the useful Paybox protocol pieces, such as request building, HMAC or signature verification, callback parsing, and response mapping, into a small library. Security-review that extracted code against current official Paybox or Verifone documentation before using it in production.
- How should I test a Paybox integration in a Laravel app?
- Use the Paybox sandbox and current official documentation to validate the contracted API version and required payment flows. Add automated tests for success, decline, timeout, duplicate callback, refund, partial capture, and signature-failure paths. Also test idempotency and reconciliation behavior before any canary rollout, and avoid passing live card data through your application unless your PCI scope is fully understood.
- What PHP and Symfony versions does lexik/paybox-bundle require?
- The bundle targets older Symfony conventions and was last released in 2019, so you should not assume support for PHP 8.x or current Symfony and Laravel versions. Check its Composer constraints carefully and expect potential conflicts with modern Laravel dependencies. Treat any compatibility claim as unverified until you have completed a sandbox-backed proof of concept.
Weaver
How can I help you explore Laravel packages today?