- Is ruudk/payment-adyen-bundle a Laravel package?
- No. It is a Symfony2 bundle built around JMSPaymentCoreBundle, not a Laravel package. It assumes Symfony's service container, bundle registration, configuration tree, event dispatcher, and JMS payment abstractions. A Laravel application cannot consume it through a service provider without substantial adaptation.
- Can I install ruudk/payment-adyen-bundle in Laravel with Composer?
- It is unlikely to install cleanly. There is no Laravel service provider, facade, or publishable configuration contract. Composer dependency conflicts are probable on modern PHP 8.x and current Laravel because the bundle targets Symfony2-era PHP and an abandoned payment core.
- What Laravel and PHP versions does ruudk/payment-adyen-bundle support?
- The package does not provide modern Laravel or PHP support. It is archived, last released in 2015, and predates modern PHP, Symfony, Laravel, and Adyen API conventions. Treat current Laravel and PHP compatibility as unresolved and likely broken.
- What is ruudk/payment-adyen-bundle used for?
- It integrates Adyen payments with the ruudk PaymentBundle in Symfony applications. It provides Symfony configuration and services to add Adyen as a payment provider. Its value is coupled to Symfony2 and JMSPaymentCoreBundle rather than Laravel.
- Does ruudk/payment-adyen-bundle use Adyen's official PHP SDK or current API?
- No. The provided context says it predates modern Adyen API conventions and does not establish use of the official Adyen PHP SDK. For Laravel, the practical path is to implement required Adyen operations with the official SDK.
- Is ruudk/payment-adyen-bundle maintained and safe for production?
- No, it is not acceptable for production. The bundle is archived, has no active maintainers, six stars, zero dependents, and was last released in 2015. Bugs, API changes, security issues, and Symfony2 or JMS compatibility become internal fork obligations.
- How should I handle Adyen payments in Laravel if this bundle is not suitable?
- Build a Laravel-native Adyen integration using the official Adyen PHP SDK. Add a Laravel service provider, configuration surface, webhook handling, idempotency, retry policies, observability, and secrets management. Validate the integration against Adyen's test environment before any production use.
- Which Adyen payment flows need to be rebuilt for a Laravel integration?
- Inventory authorization, capture, refund, webhook handling, idempotency, and reconciliation. Map each required operation to the official Adyen SDK rather than adopting the Symfony bundle. Build contract tests if legacy behavior must be matched.
- Are there maintained alternatives to ruudk/payment-adyen-bundle for Laravel?
- There is no credible install-and-migrate path from this bundle to Laravel. Use the official Adyen PHP SDK or a maintained Laravel package that wraps it. If evaluating a third-party Laravel package, check release cadence, PHP and Laravel support, and Adyen API coverage.
- What should I check before forking or migrating legacy Adyen behavior from this bundle?
- Confirm whether the legacy Adyen workflow is a hard business requirement. Identify the Adyen API version and payment methods, run a time-boxed spike to prove installation or adaptation is not viable, and estimate fork versus rebuild cost. Assign ownership for security and PCI-related review before accepting any archived payment dependency.