- Can I install gordalina/easypay-bundle in Laravel?
- Not directly. gordalina/easypay-bundle is a Symfony bundle and depends on Symfony's Bundle base class, DI container compiler passes, Extension configuration trees, and HTTP kernel bundle registration, none of which Laravel provides. A Laravel integration requires porting the separable API client into an application-owned service provider, or using Easypay's official SDK or REST API instead.
- Is gordalina/easypay-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The repository name and package type target Symfony Framework integration, and the code is organized around Symfony bundle conventions such as DependencyInjection, Resources/config, and a Bundle class. Laravel service providers and facades are not part of its architecture.
- What Laravel version does gordalina/easypay-bundle support?
- It does not declare Laravel support because it is built for Symfony. There is no Laravel service provider, facade, config publish command, or Illuminate dependency to bind it into a Laravel application. You should check composer.json for its Symfony and PHP constraints, which are likely to conflict with a modern Laravel stack.
- How do I integrate Easypay payments into a Laravel application?
- Do not treat this bundle as a drop-in Laravel integration. The practical path is to use Easypay's official SDK or REST API directly, or extract only the underlying API client classes from the bundle and bind them through a Laravel service provider. Keep the payment flow in application-owned code so you control idempotency, callbacks, refunds, and reconciliation.
- Does gordalina/easypay-bundle handle Easypay webhooks and callback verification?
- There is no visible evidence that it implements callback or webhook signature verification. A thin bundle wrapper typically covers outbound request and response handling rather than the full payment lifecycle. You must audit and likely implement callback validation, idempotency, retry safety, and reconciliation yourself.
- Is gordalina/easypay-bundle maintained and production ready?
- Treat it as unproven: the repository shows 3 stars and 0 dependents, which is effectively no production evidence for a money-handling path. A bundle of this vintage is likely dormant and may pin Symfony 2.x or 3.x and older PHP versions. Check the last commit date, tagged releases, changelog, and test suite before relying on it.
- How do I install and configure EasypayBundle in Symfony?
- In Symfony, the bundle is installed with Composer and registered in the kernel bundle list, with configuration provided under its extension key. You then inject the bundle's services where needed for payment requests. This Symfony setup does not translate to Laravel, where you would need a custom service provider and configuration file.
- What PHP and Symfony versions does gordalina/easypay-bundle require?
- You must read the package composer.json for the exact constraints, because the metadata does not state them. Symfony bundles from this era commonly require Symfony 2.x or 3.x and PHP 5.x or 7.x. Composer resolution failure against a modern Laravel lockfile is the most likely first blocker.
- Are there better alternatives to gordalina/easypay-bundle for Laravel?
- Prefer Easypay's official PHP SDK or its REST API if either is maintained, because payment integrations should not depend on an unmaintained Symfony bundle. If no maintained Laravel package exists, build a thin application-owned client and wrap it in a Laravel service provider. That gives you control over PCI scope, logging hygiene, idempotency, and callback verification.
- Can I reuse the Easypay API client from gordalina/easypay-bundle in a Laravel service provider?
- Possibly, but only if the bundle contains a cleanly separable client, typically classes outside DependencyInjection, Resources/config, and the Bundle class. Extract those service classes and discard the Symfony scaffolding rather than bootstrapping a Symfony container inside Laravel. Review the extracted code for credential handling, logging, and callback validation before using it in production.