Weave Code
Kptive Payment Sips Bundle Laravel Package
lelivrescolaire/kptive-payment-sips-bundle
Symfony bundle integrating the Kptive SIPS payment library, adding Atos Worldline SIPS support to Symfony applications. It wires the payment services into the framework so you can handle SIPS payment requests and responses within your project.
At a glance
Frequently asked questions about Kptive Payment Sips Bundle
- Can I use lelivrescolaire/kptive-payment-sips-bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package. Laravel's container is PSR-11 but not Symfony's ContainerBuilder, so the bundle's extension, compiler passes, and tagged services will not auto-register. You can reuse the SIPS protocol logic only by extracting or wrapping it, not by installing it as a normal Composer dependency. Expect a port rather than a drop-in integration.
- How do I install lelivrescolaire/kptive-payment-sips-bundle with Composer?
- You would normally require it via Composer and register Kptive\PaymentSipsBundle in a Symfony kernel. That registration step does not exist in Laravel, and there is no Laravel service provider shipped with the package. Check the bundle's composer.json for PHP and Symfony constraints before attempting anything. For Laravel, installing it directly is not a supported path.
- Which Laravel and PHP versions does this SIPS bundle support?
- The bundle is archived and appears pinned to Symfony 2 and 3-era APIs, which generally conflicts with Laravel 10 and 11 on PHP 8.1 and above. Review the package's composer.json for exact PHP and Symfony constraints and check for removed extensions such as mcrypt. Do not assume compatibility with current Laravel releases. Budget for compatibility work if you fork it.
- How do I configure SIPS merchant ID, key version, and certificates in Laravel?
- The bundle expects Symfony configuration and dependency injection, so its native config tree will not load in Laravel. A Laravel port typically replaces that with a config/sips.php file driven by environment variables for merchant ID, key version, certificate path, and sandbox or production endpoints. Keep certificates outside version control and load them through a dedicated client service. Verify the exact credential fields against your acquirer contract.
- Does this bundle verify SIPS callback seals and signatures?
- The technical assessment flags this as unverified and security-critical, so you must audit the source to confirm whether it implements callback seal verification or only redirect form generation. Payment callback authenticity, amount formatting, and currency handling are exactly where stale code becomes a fraud or reconciliation incident. If verification is missing or unclear, implement it yourself against Worldline's current documentation. Never trust an unsigned callback in production.
- How do I handle SIPS payment return and callback routes in Laravel?
- The bundle wires Symfony routes and likely Twig templates, neither of which apply to Laravel. You would map return and callback URLs to Laravel controllers, verify the seal before touching order state, and model success, cancel, declined, pending, and duplicate callbacks explicitly. Replace any Twig auto-submit form with a Blade partial or a JSON endpoint your frontend posts. Queue reconciliation work rather than doing it inline in the callback.
- Is lelivrescolaire/kptive-payment-sips-bundle still maintained?
- No. It is archived, with zero stars and zero dependents, meaning no security patches, no protocol updates, and no PHP or Symfony compatibility work. There is also no community evidence that anyone has integrated it into Laravel successfully. Treat it as a reference implementation rather than a dependency you can rely on for payments.
- What are the alternatives to this bundle for Worldline SIPS payments in Laravel?
- The realistic options are to fork and port the protocol core into a first-party Laravel package, run the bundle in a thin Symfony sidecar that Laravel calls over HTTP, or reimplement against Worldline's current SIPS documentation. Benchmark against any maintained Worldline first-party SDK before committing. For a single acquirer integration, a small first-party package is usually the best cost and risk trade.
- Does this bundle support Worldline SIPS PayPage or the newer Worldline Online Payments API?
- Unclear, and that matters. The bundle targets ATOS SIPS, which has been rebranded and evolved under Worldline into SIPS PayPage, SIPS Office, and newer Worldline Online Payments APIs. An archived bundle may target a deprecated connector version with an unclear deprecation timeline. Confirm your actual acquirer contract before assuming the bundle is protocol-relevant.
- How do I test SIPS payments in Laravel without hitting production?
- The bundle's original Symfony test setup will not translate directly, so you will likely need to fake the client behind a SipsGateway contract in Laravel. Use sandbox credentials and endpoints from your acquirer, and write tests for seal verification, amount formatting in cents, currency handling, and duplicate callbacks. Do not rely on the archived package's own tests as coverage for your integration. Payment tests should fail closed.
Weaver
How can I help you explore Laravel packages today?