Filament Wallet Laravel Package

Product Decisions This Supports

• Monetization & Subscription Models: Enables rapid implementation of user balance systems for SaaS platforms, marketplaces, or gaming apps (e.g., credits, virtual currency, or tiered access). Directly supports recurring revenue or freemium-to-paid conversion flows.
• Admin Efficiency: Cuts development time for wallet management UIs by 60–80% (vs. custom Filament tables/actions), freeing resources for core product features. Aligns with productivity-driven roadmaps (e.g., "Reduce backend dev time by 20%").
• Compliance & Auditing: Built-in transaction history and admin controls simplify financial audits or regulatory reporting (e.g., GDPR, PCI, or internal accounting). Critical for high-trust products (e.g., fintech, healthcare, or legal SaaS).
• Build vs. Buy: Justifies buying over custom development for teams without Filament expertise or when wallet features are non-differentiating (e.g., "We need balances, not a competitive edge").
• Roadmap Prioritization: Accelerates MVP launches for balance-dependent features (e.g., "Launch beta with wallets in 2 weeks" vs. 2 months). Example use cases:
  • Marketplaces: Seller payouts or buyer credits.
  • Gaming: In-game currency or loot boxes.
  • SaaS: Usage-based billing or API credits.
  • E-commerce: Store credits or loyalty programs.

When to Consider This Package

• Adopt if:

  • Your primary admin panel is FilamentPHP v4 (or you’re migrating to it), and you need wallet/transaction management without custom UI work.
  • You require real-time balance updates (e.g., live deposits/withdrawals) with minimal frontend complexity (the lazy() action handles this elegantly).
  • Your team lacks dedicated QA but needs testable wallet logic (the included PestPHP suite covers core actions).
  • You’re building a B2B, B2C, or SaaS product with:
    • Subscription models (e.g., credits, tiers).
    • Microtransactions (e.g., tips, donations).
    • Internal accounting (e.g., payouts, refunds).
  • You prioritize speed over customization (e.g., "Ship wallets in 1 sprint" vs. 3).

• Look elsewhere if:

  • You’re using FilamentPHP v3 or earlier (v4.0.0 drops v3 support; migration effort may outweigh benefits).
  • Your wallet needs multi-currency, fractional reserves, or advanced accounting (this package is designed for simple balance/wallet actions).
  • You require deep integrations with payment gateways (e.g., Stripe, PayPal) beyond basic top-ups (though the underlying bavix/laravel-wallet may support extensions).
  • Your team prefers React/Vue over Filament’s Blade/Livewire stack for wallet UIs (this package is tightly coupled to Filament’s ecosystem).
  • You need offline-capable or mobile-first wallet experiences (this is admin-panel focused).

How to Pitch It (Stakeholders)

For Executives: *"This package lets us launch wallet features in 2 weeks instead of 2 months, saving $50K in dev costs while reducing user friction. For [Product X], it directly enables:

• Recurring revenue (e.g., credits for premium features).
• Higher retention (e.g., gamified balances for [Y]).
• Compliance-ready audits (transaction logs for [Z]). The Filament v4 integration ensures we’re future-proof, and the built-in tests cut QA time by 50%. *Recommend adopting for [Q1 roadmap] to hit [revenue goal]."

For Engineering: *"Filament Wallet v4.0.0 is a zero-custom-code solution for wallet management in Filament v4. Key wins:

• Drop-in setup: Install, run php artisan filament-wallet:install, and add a trait to your model. Done.
• Livewire 3.x ready: The lazy() action improves UX for real-time updates (e.g., no more accidental double-submits).
• Test coverage: Covers deposits/withdrawals, so we can CI/CD wallet features confidently. Tradeoffs:
• Filament v4 only: If we’re stuck on v3, we’ll need to backport or migrate.
• Limited extensibility: No multi-currency or complex accounting, but we can build on top of bavix/laravel-wallet if needed. Recommend adopting if we’re using Filament v4 for [Feature Y]—it’s a 1-day integration for a 3-month custom dev effort."*

For Design/Product: *"This gives us pre-built UI components for:

• User balances (e.g., dashboard cards).
• Transaction history (e.g., activity feeds).
• Top-up flows (e.g., 'Add credits' buttons). No design work needed—just plug it into Filament. Perfect for [Product Z]’s monetization phase."*