Weave Code
Subscription Bundle Laravel Package
softspring/subscription-bundle
Softspring Subscription Bundle adds subscription management to PHP applications: define plans, manage subscriber lifecycles, track recurring billing periods, and attach subscriptions to your existing entities through a clean, configurable bundle architecture.
At a glance
Frequently asked questions about Subscription Bundle
- What is softspring/subscription-bundle used for?
- It is a Composer package that adds subscription management to PHP applications: you define plans, manage subscriber lifecycles, track recurring billing periods, and attach subscriptions to entities you already have. It is packaged as a configurable bundle, so the intent is to plug subscription state into an existing domain model rather than build a standalone SaaS billing platform. Typical use cases are membership sites, SaaS tiers, and any app where access is tied to an active period.
- How do I install softspring/subscription-bundle with Composer?
- Install it with Composer using the package name softspring/subscription-bundle, then register the bundle in your application kernel or bundle configuration. Because the package is distributed as a bundle, setup normally means enabling it in the bundle list and importing its configuration. Check the repository README for the exact registration snippet and any required migration or schema steps before running it in an existing project.
- Does softspring/subscription-bundle work with Laravel?
- The package is built as a Symfony-style bundle, which means it targets Symfony's bundle and kernel architecture rather than Laravel's package discovery and service provider model. There is no documented Laravel service provider or facade, so dropping it into a Laravel app is not a supported out-of-the-box path. Laravel teams should either budget for an integration layer or evaluate a Laravel-native billing option such as Cashier.
- Which PHP and Symfony versions does softspring/subscription-bundle support?
- Version requirements are declared in the package's composer.json, so check that file or the Packagist page for the exact PHP and Symfony constraints before installing. Confirm the Symfony major version matches your application, since bundle configuration and service definitions can change between majors. If you are on an older Symfony release, verify compatibility rather than assuming the latest tag will install.
- How do I define subscription plans in this bundle?
- Plans are modelled as first-class objects so a subscription can reference the plan that defines its duration and billing period. You create or seed plans in your application and then start subscriptions against them, which keeps pricing and period rules out of your controllers. Review the bundle documentation for the exact plan fields and configuration options available in your installed version.
- How do I attach a subscription to an existing entity such as a User or Team?
- The bundle is designed for exactly this: subscriptions attach to your existing entities, so a User, Team, or Organisation becomes a subscriber without changing its core model. You typically implement or map the subscriber relationship through the bundle's configuration and then query the active subscription for that entity when checking access. Keeping access checks behind a single service or method makes it much easier to swap or extend later.
- How does the bundle track recurring billing periods and renewals?
- Each subscription carries its billing period state, so the bundle can record when the current period starts and ends and when a renewal is due. Your application is still responsible for the scheduling layer that triggers renewals, for example a console command or queued job that advances periods. Store period changes transactionally so a failed renewal does not leave a subscription in an ambiguous state.
- Does softspring/subscription-bundle process payments or integrate with Stripe or Paddle?
- The scope described is subscription lifecycle and billing-period management, not payment gateway processing. You should expect to pair it with a payment provider such as Stripe or Paddle, or with your own invoicing flow, and let the bundle own the subscription state. That separation is useful, but it does mean card handling, refunds, and webhooks remain your responsibility.
- How should I test subscription lifecycle logic built on this bundle?
- Write integration tests that create a plan, start a subscription, advance the billing period, and expire it, asserting the state after each transition. Run those tests against a disposable test database and freeze or inject the clock so period boundaries are deterministic rather than dependent on the real date. Cover edge cases such as renewing an already expired subscription and double-starting a subscription for the same entity.
- Is softspring/subscription-bundle actively maintained and safe for production use?
- Before committing, review the repository's recent commit history, tagged releases, open issues, and whether the composer.json constraints match your stack. Since no formal technical assessment is included here, verify test coverage and how the bundle handles schema migrations in your environment. If activity looks sparse, plan to pin a version and be prepared to fork or patch it yourself.
Weaver
How can I help you explore Laravel packages today?