Weave Code
Tomato Wallet Module Laravel Package
tomatophp/tomato-wallet-module
A Laravel wallet module for the TomatoPHP ecosystem, adding account balances, credits and debits, and transaction tracking to your app. Integrates with TomatoPHP admin panels for managing wallets and payment records.
Account Wallet Manager & Payment Integrations For TomatoPHP and TomatoCRM
Frequently asked questions about Tomato Wallet Module
- How do I install tomatophp/tomato-wallet-module in a Laravel app?
- Install it with Composer at a pinned version, then publish any config, assets, and migrations the module ships and run the migrations in a disposable environment first. Because first-time adoption depends on TomatoPHP packages and version constraints, verify Laravel and PHP compatibility before enabling it in an existing application. Smoke test routes, permissions, localization, and the admin UI before promoting the changes to staging.
- Which Laravel and PHP versions does tomato-wallet-module support?
- The package is a TomatoPHP module, so its constraints are tied to the TomatoPHP ecosystem rather than documented standalone Laravel ranges. Confirm the Composer requirements against your application's Laravel and PHP versions and your existing TomatoPHP packages before installing. Do this check up front, since first-time adoption hinges on resolving that dependency graph cleanly.
- Does this package work without TomatoPHP or Filament?
- It is built for the TomatoPHP and Filament admin stack, so it fits best in applications already using those modules. Fit is uncertain for a standalone Laravel app until its dependencies, persistence model, and extension points are confirmed. For non-TomatoPHP apps, treat it as a candidate module that needs a dependency and architecture review rather than a drop-in package.
- What does the wallet module actually provide: balances, transactions, or only admin UI?
- The module is described as an account wallet manager with balances, credit and debit transactions, plus ready-made Filament resources and helpers for tracking funds and payment history. Whether it fully owns refunds, payment methods, and ledger integrity versus providing admin scaffolding is not confirmed in the available documentation. Review the schema and service layer before mapping it onto an existing wallet domain.
- Are the package migrations safe to run in production and reversible?
- Migration reversibility and production safety are not documented in the available information, so verify both in a disposable environment before adopting. Run the migrations, test rollback behavior, and confirm rollback does not destroy wallet data you need to keep. If you already have wallet tables, map your current schema and service boundaries before enabling package-owned migrations.
- How do wallet permissions and authorization work in this module?
- The authorization model is one of the open questions for this package, and the permissions and policies governing wallet access are not documented in the details available. Inspect the module's policies, gates, and Filament resource permissions after installation. Establish internal ownership for permission configuration so that access to wallet data stays auditable in production.
- Can I publish and override the translation files?
- Translation files are part of the package surface, and v1.0.2 was a translation-only patch, so locale publishing and overrides matter. Check whether the translation files are publishable and confirm that updates will not overwrite product-specific terminology. Test config and route caching after adjusting locale files to make sure nothing breaks.
- How should I test wallet credit and debit transactions?
- There is no published test suite detail in the available information, so plan your own coverage around credit and debit behavior, balance consistency, and concurrency. Write feature tests that exercise transactions through the module's public API or Filament actions rather than only through the UI. Add CI checks for migrations, routes, and config caching as part of adoption.
- Is tomato-wallet-module actively maintained, and what changed in v1.0.2?
- v1.0.2 is a translation-only patch from a new contributor, with no evidence of breaking API, schema, dependency, or configuration changes, which keeps release-specific risk low. Ongoing maintenance still requires tracking Laravel and TomatoPHP compatibility, translation drift, and dependency updates. Pin versions and review patch releases before rolling them into production.
- What are alternatives to tomato-wallet-module for Laravel wallet and balance management?
- Alternatives depend on whether you need a full ledger with integrity guarantees or admin tooling on top of an existing balance model. If you are committed to TomatoPHP and Filament, this module fits the stack; otherwise evaluate packages with a documented data model, test coverage, and an authorization story. Run a short spike comparison against your schema and reporting needs before committing.
Weaver
How can I help you explore Laravel packages today?