Download the PHP package appslab-ke/paystack-laravel without Composer
On this page you can find all versions of the php package appslab-ke/paystack-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download appslab-ke/paystack-laravel
More information about appslab-ke/paystack-laravel
Files in appslab-ke/paystack-laravel
Package paystack-laravel
Short Description A Laravel Package for Paystack
License MIT
Informations about the package paystack-laravel
laravel-paystack
A Laravel Package for working with Paystack seamlessly
Installation
PHP 5.4+ or HHVM 3.3+, and Composer are required.
To get the latest version of Laravel Paystack, simply require it
Or add the following line to the require block of your composer.json
file.
You'll then need to run composer install
or composer update
to download it and have the autoloader updated.
Once Laravel Paystack is installed, you need to register the service provider. Open up config/app.php
and add the following to the providers
key.
If you use Laravel >= 5.5 you can skip this step and go to
configuration
Unicodeveloper\Paystack\PaystackServiceProvider::class
Also, register the Facade like so:
Configuration
You can publish the configuration file using this command:
A configuration-file named paystack.php
with some sensible defaults will be placed in your config
directory:
General payment flow
Though there are multiple ways to pay an order, most payment gateways expect you to follow the following flow in your checkout process:
1. The customer is redirected to the payment provider
After the customer has gone through the checkout process and is ready to pay, the customer must be redirected to the site of the payment provider.
The redirection is accomplished by submitting a form with some hidden fields. The form must send a POST request to the site of the payment provider. The hidden fields minimally specify the amount that must be paid, the order id and a hash.
The hash is calculated using the hidden form fields and a non-public secret. The hash used by the payment provider to verify if the request is valid.
2. The customer pays on the site of the payment provider
The customer arrives on the site of the payment provider and gets to choose a payment method. All steps necessary to pay the order are taken care of by the payment provider.
3. The customer gets redirected back to your site
After having paid the order the customer is redirected back. In the redirection request to the shop-site some values are returned. The values are usually the order id, a payment result and a hash.
The hash is calculated out of some of the fields returned and a secret non-public value. This hash is used to verify if the request is valid and comes from the payment provider. It is paramount that this hash is thoroughly checked.
Usage
Open your .env file and add your public key, secret key, merchant email and payment url like so:
If you are using a hosting service like heroku, ensure to add the above details to your configuration variables.
Set up routes and controller methods like so:
Note: Make sure you have /payment/callback
registered in Paystack Dashboard https://dashboard.paystack.co/#/settings/developer like so:
OR
OR
OR
OR
Let me explain the fluent methods this package provides a bit here.
A sample form will look like so:
When clicking the submit button the customer gets redirected to the Paystack site.
So now we've redirected the customer to Paystack. The customer did some actions there (hopefully he or she paid the order) and now gets redirected back to our shop site.
Paystack will redirect the customer to the url of the route that is specified in the Callback URL of the Web Hooks section on Paystack dashboard.
We must validate if the redirect to our site is a valid request (we don't want imposters to wrongfully place non-paid order).
In the controller that handles the request coming from the payment provider, we have
Paystack::getPaymentData()
- This function calls the verification methods and ensure it is a valid transaction else it throws an exception.
You can test with these details
Todo
- Charge Returning Customers
- Add Comprehensive Tests
- Implement Transaction Dashboard to see all of the transactions in your laravel app
Contributing
Please feel free to fork this package and contribute by submitting a pull request to enhance the functionalities.
How can I thank you?
Why not star the github repo? I'd love the attention! Why not share the link for this repository on Twitter or HackerNews? Spread the word!
Don't forget to follow me on twitter!
Thanks! Prosper Otemuyiwa.
License
The MIT License (MIT). Please see License File for more information.
All versions of paystack-laravel with dependencies
illuminate/support Version ~6|~7|~8
guzzlehttp/guzzle Version ~6|~7|~8