Weave Code
Laravel Fatture In Cloud Laravel Package
offline-agency/laravel-fatture-in-cloud
Laravel integration for the Fatture in Cloud API, making it easy to manage invoices, clients, products, and other billing data from your PHP applications. It provides a configurable API client, fluent resource methods, and Laravel-friendly configuration for streamlined Italian e-invoicing workflows.
A wrapper plugin with Fatture in Cloud Api written in Laravel PHP
Frequently asked questions about Laravel Fatture In Cloud
- Does offline-agency/laravel-fatture-in-cloud support Laravel 10 and PHP 8.1?
- Version 2.2.8 adds PHP 8.1 support, which is the practical floor for Laravel 10 and modern Laravel 9 deployments. That makes 2.2.8 the first release you should consider for Laravel 9/10 applications on PHP 8.1. The assessment does not confirm Laravel version coverage in CI, so verify Composer constraints against your exact laravel/framework pin before adopting.
- How do I install and configure offline-agency/laravel-fatture-in-cloud?
- Install it with Composer and publish the package configuration, then add your Fatture in Cloud API credentials to the config or environment. The package follows the standard Laravel shape: a service provider, facade, publishable config, and Guzzle-backed HTTP client. It is a bounded integration layer, so it should not force patterns on the rest of your app.
- Is there a sandbox or test credentials option for Fatture in Cloud?
- The assessment does not document a sandbox or test-credentials path for pre-production validation. You should confirm with the maintainer or package docs whether Fatture in Cloud sandbox credentials are supported. If not, wrap all API calls behind an internal adapter so you can stub responses in staging.
- Does this package support webhooks for SDI status updates or do I need to poll?
- The assessment identifies webhooks and async SDI status callbacks as open questions, not confirmed features. Treat polling for invoice status as the safe default until the package documents webhook support. Check the README and source for any event or callback handling before designing your workflow.
- Which version of the Fatture in Cloud API does this package use?
- The assessment notes that the package is a thin shim over the Fatture in Cloud REST API and asks which API version is pinned, but does not state a version. Upstream API changes propagate directly through the wrapper, so review the package source or changelog for the pinned API version. Pin the package version and monitor upstream releases.
- Is offline-agency/laravel-fatture-in-cloud safe for production invoicing?
- It is a thin wrapper around a third-party SaaS, so production safety depends on Fatture in Cloud availability, API versioning, and auth token lifecycle. The package is maintained by a small agency, which creates bus-factor and release-cadence risk. Use an internal adapter, queue outbound calls, and add dependency monitoring before relying on it for invoicing.
- How do I create and send an invoice using this package?
- The package exposes fluent resource methods for invoices, clients, products, and other billing data. A typical flow is to configure credentials, resolve the invoice resource through the facade, create the invoice payload, and call the send method. Review the README for the exact method names and payload shape, and test against sandbox credentials first.
- Does the package support PHP 8.2 and 8.3?
- The 2.2.8 release note claims PHP 8.1 support; it does not provide evidence of PHP 8.2 or 8.3 CI coverage. Treat 8.2+ as unverified until the maintainer demonstrates testing. Run your own test suite on your target PHP minor rather than assuming 8.1 support implies 8.3 support.
- How actively maintained is offline-agency/laravel-fatture-in-cloud?
- It is maintained by offline-agency, a small shop, and the assessment flags maintainer concentration as the dominant long-term risk rather than code quality. Expect a steady trickle of patch releases driven by upstream API and PHP compatibility work. Add Dependabot or Renovate monitoring and re-evaluate on each upstream release.
- How do I test offline-agency/laravel-fatture-in-cloud in my Laravel tests?
- The assessment does not state the package's test suite coverage, so plan to test your own integration layer. Wrap the package behind an internal service or adapter interface so you can stub API responses in Laravel tests. Use Fatture in Cloud sandbox credentials if available, and never call the live API synchronously in a user request path.
Weaver
How can I help you explore Laravel packages today?