Weave Code
Laravel Pay Pocket Laravel Package
toneflix/laravel-pay-pocket
A Laravel package for adding payment wallets and transactions to your app, with simple APIs for funding pockets, tracking balances, recording transactions, and supporting multiple payment providers. It simplifies wallet-based payment workflows in Laravel.
A multi-wallet Laravel package with comprehensive logging and payments capabilities.
Frequently asked questions about Laravel Pay Pocket
- How do I install toneflix/laravel-pay-pocket in a Laravel app?
- Install v4 with composer require toneflix/laravel-pay-pocket:^4.0. Your application must run PHP ^8.3|^8.4 and Illuminate ^12.0|^13.0. After installation, review or re-publish the package config and replace any old namespace imports if you are migrating from v3.
- Does toneflix/laravel-pay-pocket support Laravel 11 or PHP 8.2?
- No. Version 4 restricts runtime support to PHP 8.3 through 8.4 and Laravel 12 through 13. Applications on older Laravel or PHP versions need a platform upgrade first, or they should remain on v3 while confirming its support and security-fix posture.
- How do I upgrade from toneflix-code/laravel-pay-pocket v3 to v4?
- Use the documented sequence: composer remove toneflix-code/laravel-pay-pocket, then composer require toneflix/laravel-pay-pocket:^4.0. Replace ToneflixCode\LaravelPayPocket with Toneflix\LaravelPayPocket in imports, published config, tests, seeders, custom wrappers, class-string references, container bindings, and cached config. Clear config, route, and class caches, then run the full test suite. Keep the old lockfile available for rollback until production verification completes.
- What namespace changed in laravel-pay-pocket v4?
- The PHP namespace changed from ToneflixCode\LaravelPayPocket to Toneflix\LaravelPayPocket. The Composer package also moved from toneflix-code/laravel-pay-pocket to toneflix/laravel-pay-pocket. Treat this as a new integration identity in dependency inventories and security monitoring.
- Can I use multiple wallets for a single user with laravel-pay-pocket?
- Yes. The package is described as a multi-wallet Laravel package. It provides simple APIs for funding pockets, tracking balances, and recording transactions, so wallet-based payment workflows can be modeled per user or pocket.
- How are payments and transaction logging handled by laravel-pay-pocket?
- The package includes payments capabilities and comprehensive logging alongside wallet management. It supports multiple payment providers and records transactions while tracking balances. Review the package config and APIs for the specific provider integrations and logging behavior your application needs.
- Do I need to publish config or run migrations after upgrading to v4?
- The v4 release notes do not describe database schema changes, but the published config must be reviewed after the namespace replacement. Re-publish or diff the config if it references the package namespace. Clear cached config before testing and confirm whether any migrations apply in your installation.
- What should I check before deploying laravel-pay-pocket v4 to production?
- Inventory all old package and namespace references first, then upgrade the runtime platform if needed. Perform the Composer swap on a branch, run a global namespace replacement, clear config and route caches, and run the full test suite. Do not assume old and new package versions or namespaces can coexist cleanly, and keep a rollback path until production verification completes.
- How should I test a Laravel app using laravel-pay-pocket v4?
- After the Composer swap and namespace replacement, clear config, route, and class caches and run your full application test suite. Cover wallet funding, balance tracking, transaction recording, and any configured payment-provider flows. Package contributors use Testbench ^10.11|^11.1 and Pest ^4, but that mainly affects package development and CI rather than production runtime.
- How do I keep maintenance and security monitoring working after the package rename?
- Update Renovate, Dependabot, SBOM tooling, vulnerability scanners, and internal allowlists to watch toneflix/laravel-pay-pocket instead of the old package name. Otherwise the package may become invisible to maintenance monitoring. Also confirm whether v3 still receives security fixes during your transition period.
Weaver
How can I help you explore Laravel packages today?