Weave Code
Sylius Paybox Bundle Laravel Package
libre-informatique/sylius-paybox-bundle
Sylius bundle that integrates the Paybox payment gateway, letting stores offer Paybox as a checkout payment method. Handles gateway configuration and payment flow inside Sylius. Useful for French e-commerce projects that need Paybox support alongside existing Sylius payment options.
Paybox gateway for Sylius projects.
Frequently asked questions about Sylius Paybox Bundle
- Is libre-informatique/sylius-paybox-bundle a Laravel package?
- No. It is a Sylius bundle built on Symfony and the Payum gateway abstraction, with no Laravel service provider, no Laravel config surface and no laravel/framework Composer constraint. On Laravel its only real value is as a reference implementation of the Paybox protocol, which you would need to rewrite or replace with something like an Omnipay driver.
- How do I install the Paybox bundle in a Sylius project?
- Install it with Composer, enable the bundle in your Sylius application, then seed the Paybox credentials and gateway parameters and register it as a Sylius payment method. Because the package is small and has very low adoption, pin an exact version and validate the sandbox flow before touching production. Take the bundle class name and config keys from the repository itself, since they are not guaranteed to match the catalog entry.
- Which Sylius, Symfony, PHP and Payum versions does this bundle support?
- The declared support matrix is not stated in the available context, and small bundles like this commonly lag current Sylius, Payum and PHP 8.2+ releases. Check the composer.json constraints and any CI configuration in the repository before planning anything. Silent incompatibility is the most common failure mode for low-traffic bundles, so treat version support as unproven until you have run it against your stack.
- Does it support 3-D Secure v2 and SCA for EU cards?
- This is not confirmed in the available documentation, and it is the single most important question for a French or EU storefront. EU SCA and 3DS2 have been mandatory since 2021, so a bundle that only implements the legacy 3DS flow will see EU-issued cards declined at scale. Confirm whether the authentication result is validated server-side rather than trusted from the redirect before committing any engineering time.
- How are Paybox callbacks verified, and are forged requests rejected?
- Verification is expected to rely on Paybox HMAC signature generation and callback signature checking, which is the entire security model of a hosted-redirect flow. The available context shows no audit trail and no documented test suite, so you must review that code path yourself. Also check that amount and currency are re-checked against the order before any state transition, and that callbacks are handled idempotently.
- Can I reuse the Paybox protocol logic in a Laravel application?
- You can, but as an extraction task rather than an installation. The durable asset is the request parameter construction, HMAC signing, callback verification and status mapping; the Sylius and Payum wiring is thin and replaceable. The alternative is an Omnipay Paybox driver, but either path is a build task, so confirm the merchant contract path first.
- Which payment operations are covered: authorize, capture, refund, cancel, status?
- The available context flags partial refunds, separate authorize and capture, tokenization and recurring payments, multi-currency and idempotent callbacks as probable gaps at this package size. Inspect the Payum gateway factory and its action classes to see which operations are actually implemented. Missing refund or capture support is usually a launch blocker for production stores.
- Does it have a sandbox mode and what should I test?
- Paybox provides a test environment that you configure with test identifiers and HMAC keys, and the bundle should route to it once configured. Do not stop at the happy path: exercise the 3DS challenge, a decline, a cancel and a refund, and confirm the callback URL is registered with the acquirer. A sandbox that only proves the success path inflates confidence in a payment integration.
- Which Paybox product does it target, and do I need a merchant contract first?
- Paybox offers several products such as System, Direct, Direct Plus and Web GA with differing parameters and authentication behaviour, and the available context does not state which one this bundle implements. Match the bundle to the contract you intend to sign before starting a spike. The dominant cost here is commercial, not technical: merchant contract, site and rank allocation, HMAC key exchange, and callback URL registration.
- Is the package actively maintained, and what are the alternatives?
- Adoption signal is near zero, with only a couple of stars and no dependents, so there is no community to inherit bug fixes from and no downstream corpus proving production use. Treat it as unproven and review the code before it goes anywhere near a critical path. Alternatives are to write a thin Omnipay Paybox driver or implement the gateway directly against Paybox documentation inside Sylius.
Weaver
How can I help you explore Laravel packages today?