damms005/laravel-multipay

An opinionated, easily extendable and configurable package for handling payments in Laravel

v5.0.8 2024-10-25 20:05 UTC

Requires

• php: ^8.1
• damms005/laravel-flutterwave: ^2.0
• flutterwavedev/flutterwave-v3: ^1.0
• guzzlehttp/guzzle: ^7.3
• illuminate/support: ^7.0|^8.0|^9.0|^10.0|^11.0
• yabacon/paystack-php: ^2.2

Requires (Dev)

• doctrine/dbal: ^3.6
• larastan/larastan: ^2.9
• orchestra/testbench: ^9.0
• pestphp/pest: ^3.0
• pestphp/pest-plugin-laravel: ^3.0
• pestphp/pest-plugin-watch: ^3.1

MIT

• Damilola Olowookere

• laravel
• laravel payments
• damms005
• configurable laravel payments
• multiple payments providers
• multiple payments
• Damilola Olowookere

README

An opinionated Laravel package to handle payments, complete with blade views, routing, and everything in-between.

Whether you want to quickly bootstrap payment processing for your Laravel applications, or you want a way to test supported payment processors, this package's got you!

Although opinionated, this package allows you to "theme" the views. It achieves this theming by @extend()ing whatever view you specify in config('laravel-multipay.extended_layout') (defaults to layout.app).

Requirements:

This package is tested against:

• PHP ^8.1
• Laravel 10/11

Currently supported payment handlers

Currently, this package supports the following online payment processors/handlers

• Paystack
• Remita
• Flutterwave**
• Interswitch**
• UnifiedPayments**

key: ** implementation not yet complete for specified payment handler. PRs welcomed if you cannot afford to wait 😉

Your preferred payment handler is not yet supported? Please consider opening the appropriate issue type.

Adding a new payment handler is straight-forward. Simply add a class that extends Damms005\LaravelMultipay\Services\PaymentHandlers\BasePaymentHandler and implement Damms005\LaravelMultipay\Contracts\PaymentHandlerInterface

Note
Payment providers that you so register as described above are resolvable from the Laravel Container to improve the flexibility of this package and improve DX.

Installation

1. Install via composer.

composer require damms005/laravel-multipay

1. Publish the config file.

php artisan vendor:publish --tag=laravel-multipay-config

1. Run migrations.

php artisan migrate

Demo Repo

I published an open source app that uses this payment package. It is also an excellent example of a Laravel app that uses Laravel Vite and leverages on Laravel Echo to provide realtime experience via public and private channels using Laravel Websocket, powered by Livewire. The app is called NFT Marketplace. Click here to check it out ✌🏼

Test drive 🚀

Want to take things for a spin? Visit /payment/test-drive (route('payment.test-drive') provided by this package) . For Paystack, ensure to set paystack_secret_key key in the laravel-multipay.php config file that you published previously at installation. You can get your key from your settings page.

Warning
Ensure you have TailwindCSS installed, then add this package's views to the content key of your tailwind.config.js configuration file, like below:

    content: [
        ...,
        './vendor/damms005/laravel-multipay/views/**/*.blade.php',
    ],
    ...

Needed Third-party Integrations:

• Flutterwave: If you want to use Flutterwave, ensure to get your API details from the dashboard, and use it to set the following variables in your .env file:

FLW_PUBLIC_KEY=FLWPUBK-xxxxxxxxxxxxxxxxxxxxx-X
FLW_SECRET_KEY=FLWSECK-xxxxxxxxxxxxxxxxxxxxx-X
FLW_SECRET_HASH='My_lovelysite123'

• Paystack: Paystack requires a secret key. Go to the Paystack dashboard to obtain one, and use it to set the following variable:

PAYSTACK_SECRET_KEY=FLWPUBK-xxxxxxxxxxxxxxxxxxxxx-X

• Remita: Ensure to set the following environment variables:

REMITA_MERCHANT_ID=xxxxxxxxxxxxxxxxxxxxx-X
REMITA_API_KEY=xxxxxxxxxxxxxxxxxxxxx-X

For most of the above environment variables, you should rather use the (published) config file to set the corresponding values.

Usage

Typical process-flow

Step 1

Send a POST request to /payment/details/confirm (route('payment.show_transaction_details_for_user_confirmation') provided by this package).

Check the InitiatePaymentRequest form request class to know the values you are to post to this endpoint. (tip: you can also check test-drive/pay.blade.php).

This POST request will typically be made by submitting a form from your frontend to the route described above.

Note

if you need to store additional/contextual data with this payment, you can include such data in the request, in a field named metadata. The value must be a valid JSON string.

Step 2

Upon user confirmation of transaction, user is redirected to the appropriate payment handler's gateway.

Step 3

When user is done with the transaction on the payment handler's end (either successfully paid, or declined transaction), user is redirected back to /payment/completed (route('payment.finished.callback_url') provided by this package) .

Note

If the Payment has metadata (supplied with the payment initiation request), with a key named completion_url, the user will be redirected to that URL instead on successful payment, with the transaction reference included as transaction_reference in the URL query string.

Note

If the Payment has metadata (supplied with the payment initiation request), and it contains a key named payment_processor, it will be used to dynamically set the payment handler for that particular transaction. Valid value is any of the providers listed above

Note

If the Payment has metadata (supplied with the payment initiation request), with a key named split_code, for Paystack transactions, it will be processed as Paystack Multi-split Transaction.

Note

If there are additional steps you want to take upon successful payment, listen for SuccessfulLaravelMultipayPaymentEvent. It will be fired whenever a successful payment occurs, with its corresponding Payment model.

Payment Conflict Resolution (PCR)

If for any reason, your user/customer claims that the payment they made was successful but that your platform did not reflect such successful payment, this PCR feature enables you to resolve such claims by simply calling:

/**
* @var bool //true if payment was successful, false otherwise
**/
$outcome = LaravelMultipay::reQueryUnsuccessfulPayment( $payment )

The payment will be re-resolved and the payment will be updated in the database. If the payment is successful, the SuccessfulLaravelMultipayPaymentEvent event will be fired, so you can run any domain/application-specific procedures.

Payment Notifications (WebHooks)

Some payment handlers provide a means for sending details of successful notifications. Usually, you will need to provide the payment handler with a URL to which the details of such notification will be sent. Should you need this feature, the notification URL is handled by route('payment.external-webhook-endpoint' provided by this package).

If you use this payment notification URL feature, ensure that in the handler for SuccessfulLaravelMultipayPaymentEvent, you have not previously handled the event for that same payment.

Testing

composer test

Credits

This package is made possible by the nice works done by the following awesome projects:

• yabacon/paystack-php
• kingflamez/laravelrave

License

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