- Is padam87/billingo-bundle compatible with Laravel?
- No. padam87/billingo-bundle is a Symfony bundle, not a Laravel package. It ships a Bundle class, a DI extension, and a config tree that Laravel's service container does not understand. You can reuse transport and domain classes only after removing the Symfony wiring, or use the repo as a specification for a Laravel-native client.
- How do I install and configure padam87/billingo-bundle?
- Install it with Composer and enable the bundle in your Symfony application's bundles.php, then configure the Billingo API key and environment options under config/packages. The package is designed for Symfony's service container and autowiring. There is no Laravel service provider or config publish step, so installation steps do not transfer to Laravel.
- Can I use this package in a Laravel 10, 11, or 12 application?
- Not as a drop-in dependency. One path is to install the bundle, exclude bundle registration, and manually bind the underlying Billingo client in a Laravel service provider, but that is fragile across bundle releases. A more controlled path is to vendor or fork the client classes into app/ or a private package, which is roughly one day of work. No Laravel artifacts exist: no service provider, facade, config publish, or Laravel-style error mapping.
- What Billingo features does the bundle expose?
- The bundle exposes Billingo API access for invoices, partners, and products. The broader package blurb also covers PDF documents, Hungarian and international invoices, tax rates, and electronic invoicing workflows. Confirm the exact endpoint coverage in the source before relying on any specific feature.
- Which Billingo API version does it target?
- The repository overview does not state a Billingo API version. Billingo has iterated API versions and deprecated older ones, so inspect the client code and pin to a known version. Track the vendor changelog rather than the bundle's release notes for breaking changes.
- Does it handle NAV online invoice reporting status?
- The overview mentions electronic invoicing workflows, but it does not document NAV submission status tracking such as pending, accepted, or rejected. That is a critical gap for Hungarian invoicing because NAV online invoice reporting is legally load-bearing. Verify whether the client tracks submission state or is fire-and-forget before considering production use.
- Is there a test suite or sandbox support for this package?
- There is no evidence of CI, a test suite, or downstream validation in the vetting notes. The package has 1 star and 0 dependents, so production signal is effectively zero. Ask the maintainer whether tests run against a Billingo sandbox or recorded fixtures, and demand coverage for idempotency and retry behavior.
- How does it handle idempotency and retries on network timeouts?
- Idempotency, duplicate-invoice prevention, and timeout retry behavior are not documented in the overview. A serialization bug or silent retry can produce a legally invalid invoice or a numbering gap, so this needs a spike. Own the integration seam in your application and test duplicate prevention explicitly.
- Is padam87/billingo-bundle maintained and safe for production?
- Treat it as reference code rather than a supported product. It has a single maintainer, 1 star, and 0 dependents, which is a high bus-factor risk in a regulated domain. A recent release suggests it is not abandoned, but it may be a personal-use library; vet it accordingly.
- What are Laravel-native alternatives to this Symfony bundle?
- For Laravel, implement a BillingoGateway interface in app/Contracts, back it with a Saloon-based HTTP client, and bind it in a single service provider. Use this repo as a spec for endpoints, payload shapes, and edge cases; the relevant surface is likely 15 to 25 endpoints. Also check whether the bundle is a thin shell over a standalone Billingo SDK, in which case depend on that SDK and skip the bundle.