- Is mkurc1/wallet-bundle a Laravel package?
- No. Despite being catalogued among PHP packages, it is explicitly a Symfony bundle and ships no Laravel service provider, no publishable config file, no Laravel migrations and no Eloquent models. It assumes Symfony's dependency injection container, registration in config/bundles.php and Doctrine entity mapping. Any plan that starts with composer require in a Laravel app is built on a false premise.
- Can I use mkurc1/wallet-bundle in a Laravel application?
- Only by porting it. There is no integration layer bridging Symfony's container and Doctrine mapping to Laravel's Eloquent, migrations and events, so you would own every piece of glue code and its support burden. Most teams evaluate it as a design reference instead, then rebuild the small surface area — a wallet model, ledger entries and a credit/debit service — natively in Laravel. If you do want a drop-in dependency, look at Laravel-oriented wallet packages rather than a Symfony bundle.
- What does mkurc1/wallet-bundle actually do?
- It adds a lightweight wallet and balance layer so a user or entity can hold funds, with each credit and debit stored as a transaction rather than only recalculating a running total. That gives the current balance an auditable history plus a straightforward service API for deposits and withdrawals. It targets simple in-app accounting such as credits, refunds, payouts or virtual currency, not a full billing platform.
- Does mkurc1/wallet-bundle store balances as a ledger or a mutable balance column?
- The package markets itself as ledger-based, but you must confirm in src/Entity whether the balance is derived from append-only transaction rows or written to a mutable column. A mutable balance column with no reconciliation back to the ledger is a hard stop beyond demo use. Read the entities and Doctrine migrations before trusting the description.
- Does mkurc1/wallet-bundle handle concurrency, row locking and idempotency?
- This is not documented in the overview and has to be verified in source. Check whether credit and debit writes are wrapped in database transactions with pessimistic locking or a version column, and what isolation level is assumed. Also look for an idempotency key on each credit and debit plus an audit trail of who moved funds and why. Without those, concurrent withdrawals can overdraw a wallet silently.
- How does mkurc1/wallet-bundle represent money — integer minor units or floats?
- Unverified from the package description; inspect the entity column types and the service code that performs the arithmetic. Float or plain decimal storage is an immediate disqualifier for money-adjacent code — integer minor units is the only acceptable answer. Confirm this before anything else, because it determines whether the design is even reusable as a reference.
- Does mkurc1/wallet-bundle support multiple currencies?
- There is no mention of multi-currency support in the overview, so assume a single implicit currency until you read the schema. If you need a currency per wallet, conversion or formatting, treat that as net-new work rather than configuration. That gap alone often pushes teams toward a clean-room Laravel implementation.
- Is mkurc1/wallet-bundle safe to use in production?
- Treat it as unproven: roughly seven stars, zero dependents, a single maintainer and no visible support model or evidence of production use anywhere. This is money-adjacent code, where failures are silent and financially material rather than loud and cosmetic. A short source read focused on atomicity, locking, ledger shape and money representation is the minimum bar before any adoption decision.
- Is mkurc1/wallet-bundle maintained, and which PHP and Symfony versions does it support?
- Check the composer.json PHP and Symfony constraints against your runtime and look at the last commit date first. If it targets end-of-life PHP or Symfony versions, stop the evaluation immediately — that kills the option outright. There is no published support policy or release cadence, so maintenance is effectively whatever the single maintainer has time for.
- What license is mkurc1/wallet-bundle, and how hard is it to port to Laravel?
- It is MIT licensed, so forking or vendoring fragments is legally clean as long as license and attribution headers stay intact. Time-box a one to two day spike reading src/Entity, src/Resources/config, the DependencyInjection directory and the Doctrine migrations, then decide build versus port. Because the surface area is small, a native Laravel rebuild — wallets and wallet_entries tables, a HasWallet trait, and a WalletService owning atomic debit and credit with row locking and idempotency keys — is measured in days, not weeks. Port the invariants, not the code, and you keep something idiomatic, reviewable and yours.