- What is eugenefvdm/billing used for in Laravel applications?
- It is a Laravel billing package for managing subscriptions, plans, invoices, and payments. It provides configurable billing logic, Eloquent models, and a clean API for integrating payment gateways and tracking customer charges. The overview emphasizes straightforward setup in existing Laravel applications.
- Which Laravel and PHP versions does eugenefvdm/billing support?
- The provided materials do not list exact Laravel or PHP version constraints. Check the package composer.json and README before scheduling an upgrade. Because this is a v0.x release, confirm compatibility in staging and pin the version you validate.
- How do I install eugenefvdm/billing with Composer?
- Use Composer to require eugenefvdm/billing, then follow the package documentation for service provider registration, config publication, and database migrations. The overview confirms Eloquent models and configurable billing logic but does not include exact install commands. Verify the repository README before running installation steps in production.
- What changed in eugenefvdm/billing v0.4 for EFT subscriptions?
- The v0.4 release changes a core lifecycle rule: EFT subscriptions should not become active until money is actually received. This moves activation from intent-to-pay time to settlement-confirmed time. The release note is terse, so confirm implementation details before relying on the behavior.
- Does v0.4 make delayed EFT activation the default or an opt-in setting?
- The release note states that EFT subscriptions should not become active until money is received, but it does not say whether that is the default or controlled by a config flag. Check the package configuration and tests for the exact behavior. Treat this as a workflow integration change, not just a Composer update.
- What happens to pending EFT subscriptions created before upgrading to v0.4?
- The provided release information does not specify how existing pending subscriptions are handled. Inventory every EFT subscription creation path and decide whether to backfill, grandfather, or manually reconcile existing records according to finance policy. Validate the outcome in staging before rollout.
- How should I represent "EFT money received" when activating a subscription?
- Map money received to an explicit, auditable receipt event, and only then transition the subscription to active. Avoid coupling customer provisioning directly to raw bank notifications; use a reconciliation service or queued job that records receipt and calls the package activation API. Every receipt event should be traceable and safely replayable.
- Is subscription activation idempotent in eugenefvdm/billing?
- The release note does not confirm whether activation transitions are idempotent. If the package does not provide an idempotent activation command or event, the host application must enforce idempotency. Add tests for duplicate receipt, delayed receipt, and repeated reconciliation events.
- How can I test the EFT activation workflow before production?
- Upgrade in a branch, run the existing test suite, and add tests for pending EFT, received EFT, duplicate receipt, delayed receipt, and manual override. Integrate the receipt source in staging and run a pilot cohort before full rollout. Use a feature flag if one is available.
- Is eugenefvdm/billing production-ready given its v0.x versioning?
- A v0.x release means semver stability should not be assumed. Pin v0.4 after validating behavior in staging, especially because the package now sits on a finance-critical activation path. Require explicit acceptance criteria such as no active subscription without a traceable receipt event.