- What is shivella/ideal-bundle used for?
- It is a Symfony bundle that integrates iDEAL online banking payments into PHP applications. It wraps issuer list retrieval, payment requests, and return handling in Symfony services and configuration. It uses an Omnipay-based gateway abstraction and includes test mode support. It is not a Laravel package.
- Is shivella/ideal-bundle deprecated?
- Yes. The 1.0.6 release is marked as Deprecated, which is the key fact for any evaluation. The exact enforcement level is unconfirmed from the provided notes, so check whether Composer marks it abandoned, whether there is a README notice, or whether a runtime deprecation is triggered. Treat it as unmaintained unless you verify otherwise.
- Can I use shivella/ideal-bundle in a new Symfony project?
- It is not recommended for greenfield work because the release is deprecated and receives no forward-compatibility or security updates. Integration feasibility is low for new services and would create an orphaned dependency. It is only reasonable as a short-lived bridge if a funded replacement is already identified.
- Does shivella/ideal-bundle work with Laravel?
- No, it is a Symfony bundle, not a Laravel Composer package. Its service container and configuration integration target Symfony, so Laravel applications would not use it directly. Laravel teams should look at maintained Laravel payment packages instead.
- How do I install shivella/ideal-bundle?
- It is installed with Composer as shivella/ideal-bundle and registered as a Symfony bundle. You then configure the gateway provider settings and enable the bundle in your Symfony application. Because 1.0.6 is deprecated, pin an exact version and lock dependencies if you must install it for an existing project. Confirm it resolves against your current PHP and Symfony constraints first.
- How do I retrieve iDEAL issuers with shivella/ideal-bundle?
- The bundle provides issuer list retrieval so your checkout can present Dutch banks for selection. You call the Symfony service exposed by the bundle and pass the selected issuer into the payment request flow. Exact service IDs and method names depend on your bundle configuration, so audit the installed version's services and README before wiring it.
- How does shivella/ideal-bundle handle payment returns and callbacks?
- It wraps payment request and callback return handling in Symfony services, so your controller can process the gateway response after the user returns from their bank. You should verify the status through the gateway abstraction rather than trusting request parameters alone. Since the package is deprecated, review and harden this flow yourself because no upstream fixes are expected.
- Does shivella/ideal-bundle support test mode?
- Yes, the overview states it includes test mode support for development. That lets you exercise issuer selection and payment flows without real bank transactions. Confirm the test configuration against your gateway credentials and your installed version, because documentation may be incomplete for a deprecated package.
- What are the alternatives to shivella/ideal-bundle?
- Evaluate maintained Omnipay-based gateways, a first-party Symfony payment integration, a supported iDEAL provider SDK, or an in-house adapter around your payment provider. The right choice depends on your provider and whether you need Symfony or Laravel support. Do not adopt another unmaintained fork without checking its release and security history.
- How do I migrate away from shivella/ideal-bundle?
- Inventory every consumer and pinned version, confirm the deprecation mechanism, and identify a successor. Build a thin abstraction around current call sites, migrate behind it, then remove the dependency. Treat it as a trigger event, especially because it handles payments: audit, security triage, abstraction, replacement, and removal.