- Can I install sparkling/adyen-bundle in a Laravel application?
- No. sparkling/adyen-bundle is a Symfony2 bundle, not a Laravel package. It ships Symfony dependency-injection configuration, a configuration tree, and service definitions that Laravel has no kernel or service provider to consume. Composer resolution will also likely fail because its Symfony 2.x and PHP constraints conflict with modern Laravel applications.
- What Laravel and PHP versions is sparkling/adyen-bundle compatible with?
- It is not compatible with any Laravel version in practice. The package targets Symfony 2.x components and PHP ^5.3|^7.0, while Laravel 10 and 11 require Symfony 6/7 and PHP 8.1 or newer. Expect PHP 8 breakage such as dynamic properties and removed functions even if you force installation.
- Is sparkling/adyen-bundle still maintained?
- No, the repository is archived and unmaintained. That means no security patches, no PHP 8 support, and no updates for current Adyen APIs. It also has very weak validation signals: around 22 stars, zero dependents, and no production issue history to learn from.
- What Adyen API does sparkling/adyen-bundle use?
- It wraps Adyen's legacy recurring-billing model, including contract creation, recurring payment submission, contract disable, and notification handling. That is based on the older hosted payment page and RECURRING payment type approach. It is not built around Adyen's current Checkout API with shopperReference and stored payment methods.
- How does sparkling/adyen-bundle handle Adyen webhooks and notifications?
- The bundle includes notification handling as part of its Symfony service layer. However, that wiring is Symfony-specific and does not transfer to Laravel. In Laravel you should implement webhook verification, idempotency, and queued processing yourself using Adyen's official SDK guidance.
- What are alternatives to sparkling/adyen-bundle for Laravel Adyen integration?
- Use Adyen's official PHP library or Checkout SDK and wrap it in a Laravel service provider with typed configuration and a gateway interface. Queue webhook handling as Laravel jobs and keep credentials in your normal secrets-management workflow. Treat sparkling/adyen-bundle as a domain reference, not a dependency.
- Is ruudk/AdyenBundle the same package as sparkling/adyen-bundle?
- The repository is ruudk/AdyenBundle while the Composer package is sparkling/adyen-bundle, which suggests a fork or re-publication. Renamed forks are a known supply-chain risk, especially with zero dependents. Diff the actual Packagist distribution against the upstream repository before trusting it.
- Can I copy classes from sparkling/adyen-bundle into my Laravel app?
- You can vendor or copy the small set of Adyen wrapper classes, but that is not the same as Composer installation. You would own PHP 8 patching, security fixes, and API updates indefinitely. A better approach is to lift the contract lifecycle and notification flow concepts and reimplement them natively.
- How do I configure Adyen credentials with sparkling/adyen-bundle?
- It uses Symfony bundle configuration to define Adyen API credentials and client services. Laravel has no publishable config, facade, or service provider from this package, so that configuration model does not carry over. In Laravel, put merchant credentials and HMAC keys in environment-specific secrets and bind them through your own config files.
- How should I test Adyen payments in Laravel if I can't use this bundle?
- Test against Adyen's test environment using the official SDK, and isolate payment calls behind a gateway interface you can fake in unit tests. Use Laravel's queue fakes for webhook jobs and verify HMAC signatures in integration tests. Do not rely on this archived Symfony bundle for test utilities or modern Adyen behavior.