Download the PHP package bhekor/laravel-monnify without Composer

Laravel Monnify

A laravel package to seamlessly integrate monnify api within your laravel application

What is Monnify

Monnify is a leading payment technology that powers seamless transactions for businesses through omnichannel platforms

Create a Monnify Account Sign Up.

Look up Monnify API Documentation API Documentation.

Installation

You can install the package via composer:

Publish Monnify configuration file, migrations as well as set default details in .env file:

Laravel Monnify Webhook Event (RESERVED ACCOUNT SHOULD USE THIS)

To handle Monnify Webhook event-based notifications, the Laravel Monnify already include all required webhook endpoints Log on to your Monnify Dashboard Setting, under Developer menu, select Webhook URLs and set the respective webhook URL as follows:

• Transaction completion https://your_domain/laravel-monnify/webhook/transaction-completion
• Refund completion https://your_domain/laravel-monnify/webhook/refund-completion
• Disbursement https://your_domain/laravel-monnify/webhook/disbursement
• Settlement https://your_domain/laravel-monnify/webhook/settlement

NOTE: Make sure you replace your_domain with your server url e.g. example.com

LEGACY Webhook

To handle Monnify LEGACY Webhook notification the Laravel Monnify already include the webhook endpoint https://your_domain/laravel-monnify/webhook, replace your_domain with your server url e.g. example.com

• Log on to your Monnify Dashboard Setting, select API Keys & Webhooks and set your webhook to https://your_domain/laravel-monnify/webhook

Setup Listener

Next, create an Event Listener by running the command below within your project directory;

The NewWebHookCallReceived has two properties:

• WebHookCall webHookCall => This is an unguarded Model with property dump from the webhook call $event->webHookCall->transactionReference gives you the transactionReference from the webhook call, learn more about Transaction Completion Webhook properties on Monnify API Docs Here
• bool isValidTransactionHash => This does the transaction hash calculation for you ahead of time, if you prefer doing it yourself; Monnify::Transactions()->calculateHash($event->webHookCall->paymentReference, $event->webHookCall->amountPaid, $event->webHookCall->paidOn, $event->webHookCall->transactionReference); Laravel Monnify Webhook Event

Please see MonnifyLegacyNotificationListener.example.txt for LEGACY sample implementation of the MonnifyNotificationListener. Please see MonnifyNotificationListener.example.txt for LEGACY sample implementation of the MonnifyNotificationListener.

Note

To ensure your listener works correctly, you have to register the event within in your App\Providers\EventServiceProvider manually if auto discovery isn't turned on

Manually Registering Events

Typically, events should be registered via the EventServiceProvider $listen array; however, you may also register class or closure based event listeners manually in the boot method of your EventServiceProvider: Learn More about manually registering events

or

Turn On Event Discovery

Event discovery is disabled by default, but you can enable it by overriding the shouldDiscoverEvents method of your application's EventServiceProvider: Learn More about Event Discovery

Usage

To use the monnify package you must import the Monnify Facades with the import statement below; Other Classes import is based on your specific usage and would be highlighted in their corresponding sections. You'll also need to import the MonnifyFailedRequestException and handle the exception as all failed request will throw this exception the with the corresponding monnify message and code Learn More

Important Notice!!!

Migrating from Previous Version of Laravel Monnify

This new changes reflect my concern for modular code base, I'm certain you should not have any issues migrating and refactoring your codebase, but if you do, kindly contact me or use the issues tab, and I will make sure your concerns are all attended to. The Monnify class has been broken down grouping all actions into five(5) classes, Banks, CustomerReservedAccounts, Disbursements, SubAccounts, and Transactions see example usage below:

Before

Now

Similar implementation applies to other sections (i.e. Banks, CustomerReservedAccounts, Disbursements, and SubAccounts)

Testing

Changelog

Please see CHANGELOG for more information what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Bugs & Issues

If you notice any bug or issues with this package kindly create and issues here ISSUES

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

• Ibidapo Adeolu
• All Contributors

License

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