Weave Code
Ogone Bundle Laravel Package
snowcap/ogone-bundle
Snowcap Ogone Bundle integrates the Ogone (Ingenico) payment gateway into Symfony applications, handling payment requests, redirects, and transaction feedback with configurable credentials so you can accept online payments quickly.
Snowcap OgoneBundle integrates the Ogone (Ingenico) payment gateway into Symfony applications. It wraps the e-commerce payment flow—redirecting customers to Ogone, generating secure SHA signatures, and handling the asynchronous feedback request—so you can accept card payments without wiring the protocol yourself.
- Configurable PSPID, language, and currency
- Automatic SHA-1 signature generation and verification
- Feedback/notification endpoint for order confirmation
- Support for test and production Ogone environments
- Twig-friendly form/redirect helpers
Frequently asked questions about Ogone Bundle
- Is snowcap/ogone-bundle compatible with Laravel?
- No. snowcap/ogone-bundle is a Symfony2 bundle, not a Laravel package. It relies on AppKernel registration, a DI Extension with a Configuration tree, and Symfony's EventDispatcher/HTTP kernel, so a Laravel app would need a ServiceProvider wrapper and removal of the bundle wiring.
- Can I install snowcap/ogone-bundle with Composer in a Laravel app?
- You can require it with Composer, but it will not work as an install-and-go dependency in Laravel. There is no Laravel ServiceProvider or config publishing, and the bundle expects Symfony kernel and container mechanisms. Treat the repository as a reference implementation, not a package to drop into a Laravel checkout.
- Does snowcap/ogone-bundle support PHP 8 and Laravel 10 or 11?
- Assume no. The bundle was released in December 2015 targeting PHP 5.x and Symfony 2.x, with no evidence of maintenance since. On PHP 8.x and Laravel 9/10/11 you should expect incompatibilities such as dynamic property assumptions, removed functions, and old autoloading or PHPUnit setup.
- Does this Ogone bundle support 3DS2 or SCA?
- Almost certainly not. The bundle predates the EU SCA/3DS2 requirements that took effect in 2019–2021, and a 2015-era wrapper is very unlikely to implement the 3DS2 challenge flow. For EU card payments this is a hard compliance blocker, so you should integrate Worldline's current SDK or API instead.
- Is snowcap/ogone-bundle still maintained?
- No. It has roughly 4 stars, 0 dependents, and no release in about nine years, which means no CVE response and no tracking of gateway API changes. Running unpatched third-party code in a cardholder-data-adjacent path shifts the entire security and correctness burden onto your team.
- What is snowcap/ogone-bundle used for?
- It is a Symfony bundle for integrating the Ogone (now Ingenico/Worldline) payment gateway into e-commerce checkout flows. Its useful logic builds hosted-payment-page form fields, computes the SHA signature over the field set, and parses or validates the gateway response. The bundle wiring itself is Symfony-specific and not reusable in Laravel.
- How hard is it to port snowcap/ogone-bundle to Laravel?
- A focused port is roughly a one-to-two week effort: fork the repo, remove Symfony coupling, extract classes for signRequest, buildRedirectPayload, and verifyResponse, then wrap them in a Laravel ServiceProvider with sandbox contract tests. The catch is that this buys a 2015-era protocol implementation that still needs modernization, putting the port and a rewrite in the same cost bracket. For greenfield work, build against current Worldline documentation instead.
- What are the best alternatives to snowcap/ogone-bundle for Laravel?
- The strongest alternative is to integrate Worldline's current official SDK or HTTP API directly behind your own gateway interface. Define signRequest, buildRedirectPayload, and verifyResponse so you can swap providers later without touching checkout code. Use the old bundle only to understand legacy field names and signature composition, not as a runtime dependency.
- How do I test Ogone or Worldline payments with this bundle?
- Test against the Worldline/Ingenico sandbox with contract tests that verify signature composition, redirect payload fields, and response parsing. The bundle's original test setup is from the PHP 5/Symfony 2 era and should not be trusted for modern PHP or Laravel. Add explicit tests for failure responses and for any 3DS2/SCA flow you implement outside the bundle.
- Can I use snowcap/ogone-bundle in production for card payments?
- It is high risk and not advisable without a compliance and legal review. The code is unmaintained, lacks modern SCA/3DS2 support, and has no CVE response process, all of which are serious concerns in a payment path. If you must reuse it, fork it, name a long-term maintainer with payments experience, and keep the protocol layer behind a tested interface.
Weaver
How can I help you explore Laravel packages today?