- What is cashier-provider/cash and what does it do?
- It is a Laravel Cashier provider that plugs a cash payment backend into Cashier's subscription billing API. It lets you work with plans, invoices, and payments through Cashier's familiar fluent interface with minimal setup. The repository is a subtree split of the Cashbox component, so cashbox/foundation is the authoritative source for full documentation.
- How do I install cashier-provider/cash in a Laravel app?
- Install it with Composer using composer require cashier-provider/cash. Then configure it like any other Cashier provider, following the setup steps for config files, migrations, or service provider registration where applicable. Because this repo is a subtree split, check cashbox/foundation for the most complete installation instructions.
- Which Laravel and PHP versions does cashier-provider/cash support?
- Check the package's composer.json for the exact illuminate/support and PHP version constraints. Support tracks the Cashbox foundation release you install, so constraints can change between versions. Use a Laravel and PHP combination that satisfies those declared requirements.
- How is cashier-provider/cash different from Laravel Cashier Stripe or Paddle?
- Laravel Cashier is provider-based, and this package supplies a cash payment backend instead of Stripe or Paddle. It keeps the same subscription billing concepts, including plans, invoices, and payments, behind a familiar fluent interface. Use it when you want Cashier-style billing flows backed by cash payments rather than a card gateway.
- Do I need API keys or webhooks to use this cash provider?
- Because it targets a cash payment backend rather than a third-party card gateway, it does not depend on Stripe- or Paddle-style API keys and webhook endpoints. Configuration is handled like any other Cashier provider, typically through package config and provider setup. Check cashbox/foundation for the exact configuration keys and required steps.
- Is cashier-provider/cash production-ready and maintained?
- Production readiness follows the release and maintenance status of cashbox/foundation, since this repository is a subtree split of that component. Review the foundation repository's release tags, tests, and issue tracker before relying on it for billing. Test your plan, invoice, and payment flows in staging before going live.
- How do I test subscription billing with cashier-provider/cash?
- Use your normal Laravel test suite and refer to the tests in cashbox/foundation for examples. Cashier-style providers generally let you configure a test setup so you can assert plans, invoices, and payments without a real backend. Check the foundation docs for any fakes or helpers provided for testing.
- Where should I report bugs or contribute changes to cashier-provider/cash?
- This repository is a read-only subtree split, so changes should be made in cashbox/foundation and then split into this package. Open issues or pull requests against the foundation repository rather than the split. That keeps the Cashbox component and this Cashier provider in sync.
- How do I manage plans, invoices, and payments with this provider?
- Use Cashier's fluent subscription billing API as you would with other Cashier providers, with the cash backend handling the payment side. You define plans and let Cashier create invoices and record payments through the provider. Exact method calls follow Cashier's API and the Cashbox foundation documentation.
- What alternatives exist if I need a real payment gateway?
- If you need card or wallet processing, use Laravel Cashier's Stripe or Paddle integrations, or another Cashier-compatible provider. This package is specifically for a cash payment backend. If your code is written against Cashier's API shape, you can often swap providers with limited changes.