- How do I install zoparga/laravel-szamlazzhu in a Laravel application?
- Install it with Composer, publish the package config, and add your Szamlazz.hu agent key through an environment variable or secret store. The package follows native Laravel conventions—service provider, facade, and container binding—so you can resolve it from the container or use the facade. Do not commit credentials to the repository.
- Does zoparga/laravel-szamlazzhu support Laravel 13?
- Yes, release 1.8 is noted as adding Laravel 13 support via issue #19, which is a positive maintenance signal. Before relying on it, confirm whether Laravel 13 is exercised in CI or only declared through Composer constraints. That distinction matters if you are planning an upgrade.
- How do I configure Szamlazz.hu API credentials in Laravel?
- Publish the package configuration and supply the Szamlazz.hu agent key from your environment or secret manager rather than hard-coding it. Run Laravel's config cache after setting the values so production workers see consistent credentials. Keep separate credentials per environment where possible.
- What Laravel versions are compatible with this Szamlazz.hu invoicing package?
- The package is a thin Laravel service-provider and facade wrapper, and version 1.8 widens compatibility to include Laravel 13. Because exact constraints live in Composer and the README, check those before upgrading a major Laravel version. The 1.8 release is described as a semver minor with no announced removals.
- Can I test Szamlazz.hu invoice creation without hitting the live API?
- The provided evaluation does not confirm a documented sandbox or test mode for Szamlazz.hu, so do not assume one exists. Put invoice issuance behind your own interface and use a fake implementation in Laravel tests to avoid live billing calls. Confirm sandbox availability directly with Szamlazz.hu before designing integration tests around it.
- How should I handle Szamlazz.hu API errors after upgrading to 1.8?
- Release 1.8 expands API error messages, including community work in issue #20, which should improve diagnosability. However, errors that were previously unmapped may now surface as new exception messages, so audit catch blocks and tests that assert on exact strings. Prefer structured logging and defensive handling over fragile message matching.
- Does zoparga/laravel-szamlazzhu handle retries and duplicate invoice prevention?
- The evaluation notes no indication of retry or idempotency semantics, so duplicate-invoice protection is the caller's responsibility. Track invoice issuance state in your own domain and avoid blindly retrying failed create calls. Use order-level guards, an outbox or job uniqueness, and reconciliation with Szamlazz.hu where needed.
- Is this package production-ready for Hungarian e-invoicing?
- Architecturally it is a favourable, additive integration at the billing boundary, but it is a thin wrapper around an external statutory provider. Key production risks include a single primary maintainer, dependence on Szamlazz.hu and NAV regulatory stability, and no indicated idempotency support. Mitigate with an abstraction layer, invoice-state tracking, monitoring, and a tested error-handling path.
- How do I map Laravel orders and VAT data to Szamlazz.hu invoices?
- The package handles API wiring; most implementation effort goes into mapping your domain objects—orders, line items, VAT rates, and buyer tax numbers—onto Szamlazz.hu's invoice schema. Build explicit mapper or DTO classes and validate Hungarian tax-number and VAT requirements before sending requests. Cover the mapping with fixtures so regulatory or schema changes are easier to absorb.
- What should I check before migrating from an earlier 1.x release to 1.8?
- Version 1.8 is an in-place Composer update for earlier 1.x users, adding Laravel 13 support and broader error coverage. The main migration risk is observable error output: grep for hard-coded Szamlazz.hu error strings in catch blocks and assertions, then run invoice-related tests in a branch. No deprecations or removals are announced for 1.8.