If you want to start your online business using one of the Paytabs' ready and easy-to-install backend packages, which shortens the development cycle for your engineering team, but you can't choose between the languages/platforms. Then stay tuned as this article is for you.
In this article, you will be introduced to a comparison between all of the available packages we provide through our seven steps integration processes. This will make it easier for you to choose the suitable plugin to run on the ground with your business as seamlessly as possible.
In this article we are going to walk through the following:
- Step 1 - Setup And Activate The Integration Method
- Step 2 - Configure The Integration Method
- Step 3 - Initiating The Payment
- Step 4 - Accepting The Payment
- Step 5 - Handle The Payment Response
- Step 6 - Handle The Post-Payment Response
- Step 7 - Manage Transactions
Click on each (✔) to be redirected to know how to learn more about this feature under the selected plugin.
Step 1 - Setup And Activate The Integration Method
Packages | System Requirements | How To Install | System Supported Versions | Supported Payment Methods |
|---|---|---|---|---|
It has specific requirements, as mentioned here. | [5.8 , 8.x] | Based on Region, | ||
It has specific requirements, as mentioned here. | Any | Based on Region, click here to learn more. |
Step 2 - Configure The Integration Method
| Allow configurations in One file | ✔ Laravel config file click here to learn more. | ✔ |
Step 3 - Initiating The Payment
Please note that this step requires you to follow the instructions on the documentation to implement your payment system workflow. | Manage the Payment methods | ✔ | ✔ |
| Manage Transaction Type | ✔ | ✔ |
| Manage Transaction Class | ❌ | ✔ |
| Manage the Cart Details | ✔ | ✔ |
| Manage Shipping and Billing Details | ✔ | ✔ |
| Hide the Shipping Details | ✔ | ❌ |
| Manage the Return and Callback URLs | ✔ | ✔ |
| Manage the Payment Page Display Language | ✔ | ✔ |
| Initiate an iFramed/Embedded Payment Page | ✔ | ✔ |
Step 4 - Accepting The Payment
Please note that this step is handled automatically in Packages. However, If you need to know which package is supported for transaction type, class or integration type, see the below table.| Supported Transactions Types | Auth | ✔ | ✔ |
| Sale | ✔ | ✔ | |
| Supported Transaction Class | ecom | ✔ | ✔ |
| recuring | ❌ | ❌ | |
| moto | ❌ | ❌ | |
| Supported Integration Type | Hosted Payment Page | ✔ | ✔ |
| Managed-Form | ❌ | ❌ | |
| Own Form | ❌ | ❌ | |
| Invoice | ❌ | ❌ | |
Step 5 - Handle The Payment Response
Since the main reason of having a response on the return page is to handle the look and feel of the return page for a better experience for your customers, the documentation is giving you the needed instructions you need to follow to verify the received response, cusomizing the look and feel of the return page based on the received response is something left to your call.| Return Page handler | ❌ | ❌ |
| Verify the response on the return page method | ❌ | ❌ |
Step 6 - Handle The Post-Payment Response
Since the main reason of having a IPN/Callback (server-to-server call) is to continue the order workflow and update the payment and order/invoice status, the documentation is giving you the needed instructions you need to follow to verify the received response, handling the backend order releated workflow based on the received response is something left to your call.| IPN/Callback (server-to-server call) handler | ❌ | ❌ |
| Verify the response on the return page method | ❌ | ❌ |
Step 7 - Manage Transactions
| Capture Transaction | ✔ | |
| Void Transaction | ✔ | ✔ |
| Refund Transaction | ✔ | ✔ |
| Query Transaction | ✔ | ✔ |