- Is hugomn/iugu-bundle compatible with Laravel?
- No. hugomn/iugu-bundle is a Symfony bundle: it registers through Symfony's Bundle class and DependencyInjection extension, which Laravel does not load. Laravel boots service providers, so the package cannot be registered in a Laravel application without forking it into a service provider. The only reusable part would be roughly 100 lines of container wiring around the underlying Iugu SDK.
- How do I install hugomn/iugu-bundle in a Laravel project?
- There is no supported way to install it as a Laravel package. Composer may pull it in, but its Symfony FrameworkBundle dependencies and bundle registration will not work in Laravel's bootstrapping model. The practical path is to require the maintained official Iugu PHP SDK (or Guzzle) and bind it in your own service provider with a config/iugu.php file.
- Which Laravel and PHP versions does hugomn/iugu-bundle support?
- Its last release was 2016-09-27, targeting the PHP 5.6/7.0 and Symfony 2.x/3.x era. On PHP 8.x you should expect fatal errors and deprecation issues such as removed functions and dynamic property warnings. It was never built for Laravel, so no Laravel version is officially supported.
- What is the best way to integrate Iugu payments into Laravel?
- Build a thin Laravel-native adapter: a config/iugu.php with IUGU_API_TOKEN, account ID and sandbox flag, a service provider binding a typed client as a singleton, and optionally a facade. Put the Iugu client behind a PaymentGateway interface so domain code never imports Iugu namespaces and the provider can be swapped later. That build is typically one to three engineering days including tests.
- Does hugomn/iugu-bundle support PIX, boleto, subscriptions, and marketplace splits?
- You should not rely on it for current Iugu features. The bundle pins an API client from 2016, while Iugu has since added PIX, revised webhook signing, changed token semantics and expanded marketplace/split behavior. Inheriting that frozen contract is a liability; use the maintained official SDK or direct REST calls so you can target the current API.
- Is hugomn/iugu-bundle safe and maintained for production use?
- No. It has zero stars, zero dependents, no security disclosure channel and a last release in 2016, so it is a single-author artifact rather than a dependency you can rely on. For production Iugu traffic, use a maintained SDK behind your own Laravel service provider. Also keep card tokenization client-side so raw PAN never reaches your servers and PCI DSS scope stays minimal.
- What are the alternatives to hugomn/iugu-bundle for Laravel?
- The main options are the maintained official Iugu PHP SDK, a thin Guzzle client for the specific endpoints you use, or a small custom Laravel package wrapping either. For narrow needs like creating a charge token or an invoice, a Guzzle client is often simpler than any third-party wrapper. Whichever you pick, hide it behind a gateway interface.
- Can I fork hugomn/iugu-bundle into a Laravel package?
- Technically yes, provided the license is permissive; verify it before any fork, since a non-permissive license makes it a dead end. The work is small (roughly one to three days), but you would mainly be reusing about 100 lines of container wiring. In most cases starting fresh with the official SDK and a service provider is cleaner and cheaper than resurrecting the bundle.
- How do I handle Iugu webhooks in a Laravel application?
- Add a Laravel route and controller, excluding CSRF for that path, verify the webhook signature according to current Iugu documentation, and dispatch a queued job for processing. The bundle provides no Laravel routing, middleware or event integration, so this is your own code either way. Store and rotate webhook secrets outside the repository.
- How should I test an Iugu integration in Laravel?
- Use the sandbox flag in config/iugu.php and inject the client via the PaymentGateway interface so tests can swap in a fake. For HTTP-level tests, use Laravel's HTTP fake around Guzzle or the SDK and assert the payloads your code sends. Keep one small contract test against the sandbox for real API behavior, but do not let it run in the default unit suite.