Download the PHP package hpwebdeveloper/laravel-pay-pocket without Composer

Laravel Pay Pocket

Laravel Pay Pocket is a package designed for Laravel applications, offering the flexibility to manage multiple wallet types within two dedicated database tables, wallets and wallets_logs.

Demo https://github.com/HPWebdeveloper/demo-pay-pocket

Note: This package does not handle payments from payment platforms, but instead offers the concept of virtual money, deposit, and withdrawal.

• Author: Hamed Panjeh
• Vendor: hpwebdeveloper
• Package: laravel-pay-pocket
• Alias name: Laravel PPP (Laravel Pay Pocket Package)
• Version: 1.x
• PHP Version: 8.1+
• Laravel Version: 10.x
• Composer: composer require hpwebdeveloper/laravel-pay-pocket

Support Policy

Installation:

• Step 1: You can install the package via composer:

• Step 2: Publish and run the migrations with:

You have successfully added two dedicated database tables, wallets and wallets_logs, without making any modifications to the users table.

• Step 3: Publish the wallet types using

This command will automatically publish the pay-pocket.php config file and also WalletEnums.php file into your application's config and app/Enums directories respectively.

Updating

If updating to version ^2.0.0, new migration and config files have been added to support the new Transaction Notes Feature

Follow the Installation Steps 2 and 3 to update your migrations.

Preparation

Prepare User Model

To use this package you need to implement the WalletOperations into User model and utilize the ManagesWallet trait.

Prepare Wallets

In Laravel Pay Pocket, you have the flexibility to define the order in which wallets are prioritized for payments through the use of Enums. The order of wallets in the Enum file determines their priority level. The first wallet listed has the highest priority and will be used first for deducting order values.

For example, consider the following wallet types defined in the Enum class (published in step 3 of installation):

You have complete freedom to name your wallets as per your requirements and even add more wallet types to the Enum list.

In this particular setup, wallet_1 (WALLET1) is given the highest priority. When an order payment is processed, the system will first attempt to use wallet_1 to cover the cost. If wallet_1 does not have sufficient funds, wallet_2 (WALLET2) will be used next.

Example:

If the balance in wallet_1 is 10 and the balance in wallet_2 is 20, and you need to pay an order value of 15, the payment process will first utilize the entire balance of wallet_1. Since wallet_1's balance is insufficient to cover the full amount, the remaining 5 will be deducted from wallet_2. After the payment, wallet_2 will have a remaining balance of 15."

Usage, APIs and Operations:

Deposit

Deposit funds into wallet_1

Deposit funds into wallet_2

Or using provided facade

Note: wallet_1 and wallet_2 must already be defined in the WalletEnums.

Transaction Info (#8)

When you need to add descriptions for a specific transaction, the $notes parameter enables you to provide details explaining the reason behind the transaction.

Pay

Pay the value using the total combined balance available across all allowed wallets

Or using provided facade

Balance

• Wallets

• Particular Wallet

Exceptions

Upon examining the src/Exceptions directory within the source code, you will discover a variety of exceptions tailored to address each scenario of invalid entry. Review the demo that accounts for some of the exceptions.

Log

A typical wallets_logs table.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Hamed Panjeh
• All Contributors
• Icon in the above image: pocket by Creative Mahira from Noun Project (CC BY 3.0)

License

The MIT License (MIT). Please see License File for more information.