Weave Code
Balance Laravel Package
illuminatech/balance
Laravel package for managing balances tied to Eloquent models. Supports deposits, withdrawals, holds, transfers, and transaction history with atomic, concurrency-safe updates—ideal for wallets, points, credits, and virtual currency.
Balance accounting (bookkeeping) system based on debit and credit principle
Frequently asked questions about Balance
- What is illuminatech/balance used for in Laravel?
- It is a Laravel package for managing balances tied to Eloquent models using a debit and credit bookkeeping approach. It supports deposits, withdrawals, holds, transfers, and transaction history, making it useful for wallets, points, credits, commissions, and promotional funds. It is an accounting primitive, not a complete payments, billing, or regulated financial ledger.
- How do I install illuminatech/balance in a Laravel application?
- Install it with Composer, register the service provider, publish and run its migrations, and add the package models or traits to your application. You then call the package services around balance mutations from your own service layer. Pin the exact Composer version and verify the package documentation against your Laravel and PHP versions before adopting it.
- Which Laravel and PHP versions does illuminatech/balance support?
- The provided evaluation does not list exact Laravel, PHP, or database version constraints, so check the package composer.json and release history before installing. Verify compatibility with your Laravel release, PHP version, and MySQL or PostgreSQL engine. If your application is on a newer Laravel version than the package supports, plan for a fork or choose another package before committing.
- Is illuminatech/balance concurrency-safe for wallet balance updates?
- The package is described as supporting atomic, concurrency-safe balance updates, which typically relies on database transactions and locking. Real safety still depends on enforcing a single write path, keeping transactions short, handling retries, and monitoring hot-account contention. Test lock waits and deadlocks under realistic load before using it for revenue-critical balances.
- Does illuminatech/balance support holds, transfers, and transaction history?
- Yes, the package overview lists deposits, withdrawals, holds, transfers, and transaction history as supported balance operations. That makes it a reasonable fit for wallet-style flows where funds or credits must be reserved before final capture. Confirm in your technical spike how holds are released, how transfers are represented, and whether transaction history is immutable enough for your audit needs.
- What license does illuminatech/balance use, and can I use it commercially?
- The technical assessment flags the license as NOASSERTION, meaning no clear license was detected. Treat legal review as a hard gate before using it in proprietary or commercial software. Do not assume it is MIT or otherwise commercially safe until the repository owner or legal team confirms the actual license.
- Does illuminatech/balance enforce double-entry accounting invariants?
- It is based on debit and credit principles and stores accounting entries, but the provided context does not confirm that true double-entry invariants are enforced. Verify whether balanced postings, account constraints, and audit immutability are guaranteed by the package or must be added at the application layer. If strict accounting correctness is required, add reconciliation and validation controls around it.
- How should I handle idempotency and reversals with illuminatech/balance?
- The context does not confirm built-in idempotency keys or reversal APIs, so implement idempotency in your own LedgerService or repository layer. Use unique business references, controlled reversal postings instead of editing history, and duplicate-submission tests. Map each business event to a debit or credit posting through a single write path.
- Is illuminatech/balance suitable for production financial ledgers?
- It is better suited to internal wallets, credits, points, and similar Laravel application balances than to regulated financial ledgers. Production use requires legal clearance, reconciliation, audit controls, rollback and data-repair runbooks, and a clear owner for maintenance. The low star count and unclear long-term support mean your team should be prepared to fork or maintain it if needed.
- How do I migrate existing balances to illuminatech/balance?
- Create an auditable opening-balance posting for each account rather than updating balance rows directly. Reconcile those opening entries against current business records, run a shadow or dual-calculation period, then freeze writes for a controlled cutover. Keep rollback and repair procedures ready and monitor balance reads after switching.
Weaver
How can I help you explore Laravel packages today?